Trust

Where your data lives,and how you leave with it.

Written for the person who has to sign off before their company buys software. What is true today, and what Rillo does not claim. Anything not answered here, ask hello@rilloapp.com and a person will answer it.

Where the data lives

• One managed database. Your workspace lives in Supabase's managed Postgres, which is where sign-in lives too. The app and this site are served by Vercel, which handles the request and holds none of your records.
• Encrypted in transit and at rest. Every connection is HTTPS and the site is served under a strict transport policy, so a browser will not fall back to an unencrypted one. The database is encrypted where it sits.
• Separated by workspace, in the database itself. Rillo does not rely on the app remembering to filter by company. The database refuses a read that belongs to another workspace, so a mistake in a screen cannot turn into one company seeing another's book.

Who can see it

• Your people, at the level of their role. Owner, manager, administrator and rep each see a different amount, and money figures in particular are held to the roles that are meant to have them.
• Changes are written down. The workspace keeps an audit trail of administrative actions, including who exported it and when.
• Rillo's own people. Rillo is a small company in Phoenix. A person here can reach a workspace to fix a fault or answer a support request, and does so only for that. Rillo does not read your book for any other reason, and nobody at Rillo sells or shares what is in it.
• Nothing leaves without a person's yes. Rillo drafts, and a person sends. There is no setting that lets it message your customers on its own.

Backups, and getting out

• Backups are the platform's. The database is backed up by Supabase's managed backups rather than by a script Rillo wrote, which is the honest answer and the safer one.
• Your own copy, on demand. One control in Settings writes the whole workspace to a file you can open and read. No request, no waiting, no reason needed, and you can take it while you are still a customer.
• Leaving is the export plus a sentence. Take the export, then email hello@rilloapp.com from the address that owns the workspace and ask for it to be deleted. Nothing is held hostage and there is nothing to negotiate.
• Pausing is not leaving. A workspace that pauses because a trial ended or a plan lapsed is not deleted, and everything is there when you come back.

If something goes wrong

• You will be told. If customer data is exposed, Rillo tells the affected account owners what happened, what was involved and what to do, without waiting to have a complete picture first.
• Report one and it is read. A security problem found in good faith goes to hello@rilloapp.com and reaches a person the same day. Sending one is welcome and nobody is going to be threatened for it.
• An outage is a different thing. If the service is down, status says how to reach a person.

What Rillo does not claim

• No certification or audit. Rillo holds no SOC 2, no ISO 27001, no HIPAA attestation and no PCI certification of its own, and has not been audited by anyone. If a badge appears on a page about this product, it is not Rillo's. Card details never touch Rillo: Stripe takes them.
• No claim to be a regulated system of record. Rillo is not your LOS, your carrier system, your ATS of record or your accounting system. It sits alongside them and holds what you put into it.
• If you need more than this. A buyer who needs an agreement, a questionnaire answered or a review before purchase should write to hello@rilloapp.com and say so. The answer will be whatever is true, including no.

What Rillo holds, by trade

One line each, for the nine industries the CRM ships presets for.

Last updated 20 September 2026. Rillo LLC, Phoenix, Arizona. Questions to hello@rilloapp.com. See also privacy and the terms.