Privacy Policy

Anything you enter about a client stays on your device. It is never sent to or stored on our servers. The only personal information we hold is your own advisor account.

To give you an account and a profile for your documents, we store, through our authentication provider, your email address, phone number, name, MGA / company, and province, along with whether you have completed your profile. This is used solely to operate your account and to populate the letterhead on documents you generate.

We also keep daily counts of a few things you did in the app (for example, “3 client copies downloaded this week”) to improve the product — never their content and never anything about your clients.

Calculations, financial-needs intake, uploaded PDFs, and the documents you fill are processed entirely in your browser, on your device. They are not transmitted to us and we have no copy of them. Client details stay in this browser only until you end the meeting or sign out (and never longer than 48 hours). They are never sent to our servers.

When you choose to save a client file, it is written directly to your own device as a file you control — optionally encrypted with a password only you hold. We never receive it.

We use a third-party authentication and database provider to store the advisor-account information described above, and a hosting provider to serve the application. These providers process only your advisor-account data, never client data — because client data never leaves your device.

Because client information lives on your device and in files you save, you are the custodian of that data under PIPEDA and applicable provincial privacy law. You are responsible for safeguarding your device, your saved client files, and the passwords that protect them.

You can update your advisor profile at any time in Settings. You may request deletion of your advisor account, which removes the advisor-account information we store.

We may update this policy as the product evolves. If we ever introduce a feature that would change how client data is handled, that change will be disclosed clearly before it takes effect — the on-device promise will not be broken silently.