Plain answers for the person who has to ask.
Where does your data live?
Review data, drafts and play history live in a managed Postgres database with row-level security, encrypted in transit and at rest. Your locations are isolated at the database layer: an account can only ever read its own stores.
How does platform access work?
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.
Can anything post without approval?
No. No reply reaches a guest without a human tap from someone in your organization. There is no silent automation mode and no way to switch one on. Every published reply is attributable to the person who approved it.
Who can see what?
Store-level users see their own store. Multi-unit and corporate roles see the roll-up across the stores they are responsible for, and nothing else. Access follows your org chart, not ours.
How are payments handled?
Billing runs through Stripe. Replio never stores card numbers or bank details on its own systems.
What happens if you leave?
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.
What about enterprise deployments?
Network plans include SSO, a master service agreement and custom onboarding. We complete security questionnaires as part of every Network evaluation, and we would rather answer a hard question in writing than around it.