Privacy Policy

Effective 20 September 2026

Who controls your data

Unitpace is not a shared online service. Each insurance agency unit runs its own separate copy of the software, on hosting accounts and a database belonging to that unit's manager.

This matters for your privacy, so it is worth stating plainly: the unit manager who invited you is the owner and controller of the personal data in their deployment, and is responsible for it under the Data Privacy Act of 2012 (RA 10173). Justin Salas, operating as Unitpace, publishes and maintains the software and acts on that manager's instruction. Unitpace does not run a central copy of any unit's data.

If you want your data corrected or removed, your unit manager is the right person to ask first. Contact details for Unitpace are at the end of this page.

What is collected

About your seat

• Your name, as your unit manager entered it on your invite.
• Your email address, used to sign you in and to send you invites.
• Your mobile number, if you choose to add one. It is optional and you can remove it.
• Your agent code and your role in the unit.
• Which sign-in methods you have connected, and technical records of your sign-in sessions.

About your work

• The activity counts you record, by day, and the points they earn under your unit's settings.
• Corrections your unit manager makes to a past day, and who made them.
• Monthly persistency rates typed in by your unit's admin, and a record of who last edited them and when.

From your carrier's reports

Your unit's admin imports reports exported from the carrier's own system. What is kept from them is the production record: agent codes and names, policy numbers, product codes and names, transaction dates, premium and credit figures, and — from the agent list — appointment and termination dates.

These files are opened and read in the admin's own browser. Only the fields listed above are sent to your unit's database. Every other column is dropped where the file was opened and never leaves that computer — policyholder names first, along with contact details and birthdays. This is not a matter of policy alone: no imported table has a column that could hold a policyholder's name, and a test in the software fails the build if one is ever added.

What is not collected

• No analytics, advertising or tracking of any kind. There are no third party scripts in the app.
• No passwords. There is no password sign-in, so there is none to store.
• Nothing is sold, rented, or shared for anyone else's marketing. There is no mechanism in the software to do so.

Signing in with Google or Facebook

If you sign in with Google or Facebook, Unitpace receives only your basic profile information and your email address from them. It asks for nothing else — no contacts, no files, no posting, no friends list, no ongoing access to your account.

Unitpace never sees or stores your Google or Facebook password. You can disconnect a sign-in method from your Profile screen at any time, provided you keep at least one way to sign in — the app refuses to remove your last one.

The Google and Facebook sign-in apps belong to Unitpace, not to your unit. Each deployment's address is registered on them at setup, so what Google or Facebook shows you when you sign in names Unitpace rather than your unit.

You may also sign in with a code emailed to you instead, and use no social account at all. The same email carries a link that fills the code in for you; opening it does not by itself sign you in.

Where your data lives

Your unit's data is stored in a Cloudflare D1 database inside your unit manager's own Cloudflare account, and the app runs on Cloudflare's network.

Sign-in emails are the one exception to that separation. They are sent over SMTP through Resend, from a domain belonging to Unitpace rather than to your unit, because the sign-in setup is maintained centrally. Resend therefore handles your email address and the sign-in code sent to it.

Cloudflare keeps short-lived operational logs of requests, as any web host does. Cloudflare's backup feature retains recoverable copies of the database for seven days.

Who can see it

• You see your own activity, points and record.
• Your unit manager sees the whole unit: everyone's activity, production, rankings and records. That is the purpose of the system, and your manager can already see this information at work.
• Your unit's admin handles imports and the roster, and sees what those tasks require.
• Unitpace holds maintenance access to your unit's deployment in order to keep it running, apply updates and fix faults. That access is governed by a written agreement with your unit manager, which includes confidentiality and a duty to notify them of any breach within 24 hours.
• No other unit can see your data. Separate deployments do not share a database, and nothing connects them.

How long it is kept

Your data is kept for as long as your unit's deployment runs. If you leave the unit, your past records stay with the unit, because they are part of the unit's own history — but your seat is closed and you can no longer sign in.

When a unit stops using Unitpace, the deployment is shut down and its data is deleted within 30 days. Before that, an export of the unit's own activity counts is offered to the unit manager; the carrier's production figures are not part of it.

Moving to a different unit does not carry anything over. That unit's deployment is a separate system, and you would start there with a new invite and an empty record.

Your rights

Under RA 10173 you have the right to be informed about how your data is used, to access it, to correct it, to object to its processing, to have it erased or blocked where the law allows, to obtain a copy in a portable form, and to be indemnified for damage caused by its mishandling.

Ask your unit manager first, since they control the deployment. These are requests made to a person, not buttons in the app: there is no self-service download or delete screen, and a closed seat can no longer sign in to reach one. If your request concerns the software itself, or you cannot reach your manager, write to hi@justinsalas.dev. You may also complain to the National Privacy Commission at privacy.gov.ph.

Changes to this policy

If this policy changes, the effective date at the top of the page changes with it. This page is the current version; the app itself shows no notice when it changes, so check here.

Contact

Justin Salas, Quezon City, Philippines — hi@justinsalas.dev