Security and data
Plain answers for the person who has to ask.
The practices below are the ones we run today, written so procurement can read them without a call. When something here changes, this page changes first.
Where your data lives
Review data, drafts, and play history live in a managed Postgres database, encrypted in transit and at rest.
How platform access works
Google Business Profile connects through per-operator OAuth. Each operator grants access to their own locations and can revoke it at any time from their Google account. Replio never asks for platform passwords.
Nothing posts without approval
Nothing is posted without a person on your team tapping to approve it. There is no automation mode to switch on.
What owners see
Owners see every location on their account.
Payments
Billing runs through Stripe. Replio never stores card numbers or bank details on its own systems.
Deletion and exit
Leaving is boring by design. Ask, and your account data is deleted. Replies you published stay where they were published, on your platform profiles, under your name, because they were always yours.
Enterprise deployments
Larger groups are set up with us directly, including onboarding. We complete security questionnaires on request, and we would rather answer a hard question in writing than talk around it.
Questions we have not answered here deserve a direct reply: reach us through the contact page and the founder answers.