Privacy policy

Who is responsible for what

We decide how account data about Abe’s users is handled (for example the people who sign in to a workspace). Businesses that use Abe decide how the data of their own customers is handled: when someone messages a business through Abe, that business is the controller of the conversation and Solarai processes it on the business’s behalf and on its instructions. If you messaged a business, contact that business first about your data.

Data we process

• Account data: name, email address, profile photo, password (stored only as a hash by our authentication provider), language and appearance preferences, notification settings, organization and workspace memberships, roles and invitations.
• Workspace content: contacts and their details (such as name, phone number, email, country, language, tags, lifecycle stage and custom fields), conversations, messages, media and files, internal comments, closing notes, snippets, workflows, broadcasts, AI agent settings and knowledge sources that a workspace adds.
• Channel data: when a business connects WhatsApp, Instagram, Messenger, Telegram, LINE, Viber, SMS, email, a custom channel or website chat, we receive and send messages through that provider (or, for a custom channel, the business’s own server), including account and phone-number identifiers, customer identifiers and profile names, message content and media, and delivery and read updates. Access tokens for connected accounts are stored encrypted.
• Website chat visitors: a random visitor identifier kept in the visitor’s browser, any name or email the visitor chooses to share, and their messages.
• Technical and usage data: IP addresses, browser and device information and request logs kept by our hosting providers; session cookies that keep you signed in; audit records of important account actions; and records of AI feature usage used for limits and billing.
• Billing data: when paid plans are enabled, payments are processed by Stripe. We store customer and subscription references, not full card numbers.

Why we use it

• To provide Abe: sign-in, workspaces, the shared inbox, sending and receiving messages through connected channels, automations, broadcasts, reports and exports.
• To run features a workspace turns on, such as workflows, AI Assist and AI agents, on that workspace’s instructions.
• To keep Abe secure and reliable: preventing abuse, investigating incidents, enforcing limits and fixing problems.
• To support customers, send service notices and, when billing is enabled, process payments.
• To meet legal obligations.

We don’t sell personal data and we don’t use workspace content for advertising.

AI features

When a workspace uses AI Assist, AI agents, conversation summaries, AI closing notes or image knowledge sources, the relevant conversation messages, contact details and knowledge are sent to our AI provider, Anthropic, to produce the result. The provider processes this data to return the answer and, under its commercial terms, does not use it to train its models. Workspaces choose whether to use these features and can turn them off.

Service providers

We use these providers to run Abe. They process data only as needed to provide their service to us.

• Supabase: database, authentication and file storage, hosted in Singapore.
• Vercel: application hosting and content delivery.
• Meta Platforms: WhatsApp Business Platform, Messenger and Instagram messaging, for workspaces that connect them.
• Telegram: messaging for workspaces that connect a Telegram bot.
• LY Corporation (LINE): messaging for workspaces that connect a LINE Official Account.
• Rakuten Viber: messaging for workspaces that connect a Viber bot.
• Twilio: SMS for workspaces that connect their own Twilio account. Messages go through the business’s Twilio account.
• Anthropic: AI features.
• Expo: push notifications to the Abe mobile apps (message previews are sent to the recipient’s device through Apple or Google).
• Stripe: payments, once paid plans are enabled.
• Resend: email delivery for account and notification emails, and for workspaces that connect an email channel.

International transfers

Abe’s primary data store is in Singapore. Some providers above process data in other countries, including the United States. Where required, we rely on appropriate safeguards such as contractual commitments from those providers.

How long we keep data

We keep account and workspace data while the account or workspace is active. Data a workspace deletes (for example a contact and their messages) is removed from the active database. When an account or workspace is closed, we delete or anonymize its data, normally within 30 days, unless we must keep some of it longer by law. Backups are overwritten on a rolling schedule.

Security

Data is encrypted in transit. Channel access tokens are additionally encrypted at rest. Access is limited by workspace roles and database access rules, and important administrative actions are logged. No system is perfectly secure; tell us promptly at mail@solarai.asia if you notice a problem.

Your rights

Depending on where you live, including under Singapore’s Personal Data Protection Act and, where it applies, the EU and UK GDPR, you may ask to access, correct, export or delete your personal data, or object to or restrict some processing. Workspace owners can export and delete contacts in Abe. See data deletion for step-by-step instructions, or email us. We respond within 30 days.

Children

Abe is a business service and isn’t directed at children. Accounts are for people aged 18 or over.

Changes

We’ll update this page and its effective date when this policy changes, and tell workspace owners about significant changes before they take effect.