Privacy policy.

Publisher and privacy contact

Contact us with privacy questions or deletion requests. Include your SayAlloo account email and workspace name when relevant, but never send passwords, verification codes or provider keys.

Account and workspace information

SayAlloo stores account names and email addresses, password hashes, verification and sign-in challenge information, workspace membership and permissions, session records and security settings. If you enable authenticator two-factor authentication, its secret is encrypted and recovery codes are stored as hashes. This information provides sign-in, account recovery, access control and account security.

Your workspace may also contain connected Twilio account configuration, assigned phone numbers, personal contacts you enter, SMS content and delivery status, call history, read state, preferences, presence and workspace activity. These records provide your team's calling, messaging, number management and administration. A deletion request adds your account email, optional details, request status and processing notes to a private operator queue so the request can be verified and handled.

Microphone, notifications and device access

Calling uses the microphone after you enable calling or choose a call or answer action and grant the applicable Android, Windows or browser permission. Audio is transmitted to Twilio to connect the call. SayAlloo's Android app does not request access to your device address book, system SMS inbox, SIM identifiers, system call log or device location. Contacts and communication history shown in SayAlloo are SayAlloo workspace records.

Android notification permission supports call and message notifications. The optional background listener is off by default and starts only through your explicit action; it uses a visible ongoing notification with a Stop action to poll your authenticated SayAlloo workspace. It does not start at device boot or automatically restart after it is stopped. Active calling uses an Android microphone foreground service. The Windows app uses a dedicated WebView2 workspace profile, native microphone consent and optional notification permission. Keeping Windows running in the tray is a separate user choice. Internet interruptions, device sleep, expired sessions and stopped apps affect availability.

Twilio and call diagnostics

The Twilio account connected by your workspace processes call audio, phone numbers, routing, SMS text, delivery information and call records to provide communication. Twilio Voice SDKs also send connection events and call-quality measurements. Depending on the connection, Twilio's diagnostics may include public IP addresses, caller and recipient identifiers, operating system and SDK versions, device model or browser details, network timing, packet loss and audio levels. Network information can be used by Twilio to derive an approximate location; SayAlloo does not request a device location permission.

Your workspace administrator manages the connected Twilio account and its settings. Twilio's processing and retention also depend on its service terms and account configuration. See Twilio's privacy notice and Voice Insights information.

Optional account email and AI

If Brevo is configured on the SayAlloo server, it receives recipient email addresses and account-email content to send verification, sign-in and password-recovery messages. See Brevo's privacy policy.

If Amazon Bedrock is configured and you use an AI feature, prompts and relevant message or speech context are sent to that provider to generate a response. Manual AI drafts are reviewed before sending. SMS and voice automations are separate choices controlled by your workspace administrator and start disabled. Voice automation may use Twilio speech recognition and send the resulting text to Bedrock. Avoid including information that you do not want these providers to process. Generated content can be inaccurate. See AWS's privacy notice.

Provider credentials stay on the SayAlloo server. SayAlloo does not use Firebase for authentication, its database or notification delivery. The use of optional services depends on the server configuration and the features your workspace enables.

Workspace billing

Customer workspace services require a verified seven-day trial with saved billing or an active paid subscription. Stripe secure checkout saves your payment method for the initial trial and obtains your authorization for automatic renewal. Your selected monthly or annual subscription is charged automatically when the seven-day trial ends unless you cancel renewal before that time. Twilio usage is billed separately, including during the trial. After a workspace has used its one-time trial, configured Stripe or PayPal checkout can collect payment for a paid subscription. SayAlloo sends a workspace reference, selected recurring plan and trial eligibility to the chosen provider. The provider collects billing contact and payment information directly. SayAlloo stores provider customer and subscription references, recurring-billing consent, saved-payment verification, trial eligibility and dates, subscription status, billing periods and payment amounts to manage access and payment history. SayAlloo does not collect or store your card number. Payment providers apply their own privacy and retention policies. See Stripe's privacy policy and PayPal's privacy statement.

Workspace administrators manage subscriptions through Billing. Canceling renewal and requesting account deletion are separate actions. Trial-use records prevent repeated trial activation. Provider billing records and records needed to resolve disputes or meet accounting requirements may need to be retained; deletion-request processing identifies any retained data and applicable period.

Access, storage and security

Workspace access is scoped to team membership, administrator roles and number grants. Administrators manage their own workspace's people and provider accounts. Platform administration exposes customer profiles, roles, workspace status, resource counts, plans and billing history; it does not expose other workspaces' message content or provider credentials. Authorized platform operators can review deletion-request contact information and processing notes.

The live service uses HTTPS. Provider credentials, authenticator secrets and deletion-request details are encrypted on the server. Browser and Windows sign-in uses a secure session cookie. Android stores its bearer session using Android Keystore encryption, with that storage excluded from Android backup and transfer. Local drafts and preferences may remain on your device until you clear them or sign out as applicable. Notification history remains in the current page's memory and clears when you sign out or change workspace. Windows keeps cookies and browser storage in the current user's dedicated SayAlloo WebView2 profile; removing a portable executable may leave that profile behind. Sign out before sharing a device.

Private API responses and conversations are not cached by SayAlloo's service worker. Server and hosting infrastructure process network requests and operational information to deliver and protect the service. Public deletion forms are rate-limited, and unverified requests do not reveal whether an account exists.

Data retention

SayAlloo keeps active account and workspace records while they provide the service, until removed through an authorized action or a verified deletion request. Password-recovery links, sign-in challenges and sessions expire according to their purpose. Expired challenges and sessions are cleaned up during normal authentication and maintenance activity.

The server stores private database snapshots for recovery. SayAlloo's default maintenance setting creates daily snapshots and keeps the seven most recent valid snapshots; the installation's retention setting can differ. Snapshots may temporarily contain information deleted from the active database until they expire or are removed. During deletion review, we identify the applicable backup expiry or removal plan and any specific information that must be retained for security, fraud prevention or a legal requirement, including the reason and retention period. Records are not retained merely because a deletion request concerns a shared workspace.

Delete your account and associated data

Request account deletion

You can use the public deletion form or email [email protected] without signing in or installing the app. Settings in the apps provide a deletion pathway; signed-in web and Windows users can submit a request and view processing status. We verify account ownership before deleting account information. Submission records a request and does not immediately erase your account.

The request covers your SayAlloo account profile, authentication information and sessions, personal contacts, number preferences and read state, and associated personal information in communication and activity records. If your account administers a team or owns connected resources, we may coordinate a handover with you and the workspace administrator. You can submit a request before that handover. Shared communication records are reviewed for other users' interests, and your personal information is deleted or retained only for a specific disclosed legitimate reason and period.

When providers hold data processed for the service, deletion handling includes the necessary provider request or documented follow-up. Deleting SayAlloo does not itself close a separately managed Twilio, Brevo or AWS account, cancel a subscription, release phone numbers or reverse charges. We explain required steps and any retained data during processing. Completed-request notes identify the outcome and any retained data, including the applicable retention period. Deactivation, signing out or uninstalling an app is not account deletion.

Your controls

You can update your account name and email, change your password, manage two-factor authentication and remove personal contacts through the workspace. Administrators control team permissions and optional automations. You can stop the Android listener, sign out, and change microphone or notification permissions in device settings. Contact us if you cannot access the account or need help exercising a privacy choice.