Preview notice. The service operator’s legal details and privacy contact will be provided for live use.
Who this notice covers
This notice describes SavaraFlow’s handling of information used to run the website, administer accounts, and handle billing and support.
When a business uses SavaraFlow to contact you, that business generally decides why it contacts you, which channel it uses, and what it sends. SavaraFlow handles recipient and message data to provide the service on the business’s instructions. Direct questions about why you received a message, requests about its contact list, and opt-out requests to that business first.
The hosted demo simulates sending and billing. Use sample information in the demo. Your browser may keep changes to the demo workspace on this device.
Information we handle
- Website and device information. Requests to the site, basic device and network information available to the host, and your cookie choice. See the Cookie policy for browser storage.
- Accounts and workspaces. Sign-in email, account and workspace identifiers, team roles and invitations, sender identities, and configuration and access records. If you sign in with Google or GitHub, we receive the account identifier, email address, and basic profile information the provider shares.
- Messaging and delivery. Contact and recipient details, message content and templates, CSV rows you submit, routing and delivery status, message and provider identifiers, and consent or suppression records. This information can come from your workspace, its API integration, a message reply, or a delivery provider.
- Billing and support. Top-up amounts, transaction references, payment status, mobile money number where requested, usage records, and what you send us in a support request. Payment details entered in provider checkout are handled by that provider.
How we use information
We use this information to authenticate users, set up workspaces and senders, send and route messages, display delivery outcomes, apply suppression, reconcile payments and usage, and respond to support requests. Access and operational records help prevent abuse, diagnose failures and investigate security events.
Where the law requires a legal basis, we use information as needed to provide requested services or perform our contract, for legitimate operational and security interests where appropriate, and to meet applicable legal obligations. We rely on your permission for optional browser storage. Your business remains responsible for its permission or other basis to message recipients.
If a team member uses Smart assist to draft, translate or classify a reply, the configured language-model provider may process recent conversation context and selected support examples to produce the suggestion. A team member reviews and sends every reply.
Retention and security
Account, workspace and message records are retained as needed to operate the service and manage the workspace. In the standard deployment, a scheduled cleanup removes sandbox message records after seven days and completed webhook jobs after 30 days. Billing and access records may be needed longer for accounting, security, or disputes. Provider and backup retention depends on the deployment and applicable obligations. You can ask for the retention details that apply to your workspace.
SavaraFlow uses workspace access controls, scoped API keys, and encrypted provider credentials where configured. Keep your access links and API keys private. Contact your workspace administrator if a credential is exposed or access needs to be withdrawn.
Your choices and rights
Depending on applicable law, you may have rights to access or correct your information, request deletion or restriction, object to some processing, withdraw consent, or complain to your data protection authority. We may need information to verify your identity and locate the relevant records. Avoid sending passwords, API keys, or full payment credentials with a request.
Request account or Meta integration data deletion
Send a deletion request from your account email with the workspace name and say whether it concerns your SavaraFlow account or the data associated with a Meta integration. We will verify your authority over the account or workspace and explain any records we need to retain.
If you are a member of a live workspace, contact its administrator about workspace information. For communications you receive, contact the business that sent the message.
If Uganda’s data protection law applies, you can contact the Personal Data Protection Office.
Manage optional browser storage with .
Changes to this notice
We update this notice as our services and data practices change. The date above identifies this version.