What Raabta collects, why, and how it is protected.

Who this covers

This policy covers visitors to the Raabta website, people who join the waitlist, business users who sign in to a Raabta workspace, and customers who message a business that uses Raabta. For customer conversations, the business that owns the workspace decides what is collected and is responsible for it; Raabta processes that information on the business's behalf.

Information we collect

Waitlist and demo requests: name, business name, email, phone number, industry, optional preferences and message, consent timestamp, and limited source information such as campaign tags and the page where the form was submitted.

Workspace accounts: the name, email and role of each person who signs in, and a securely hashed password. We never store passwords in readable form.

Customer conversations: messages received through the channels a business connects (for example WhatsApp or the website chat), the sender's phone number or identifier, and the replies sent, so the business can review them and the assistant can answer in context.

Business content: knowledge-base documents, message templates and instructions that a business adds so the assistant can answer accurately.

Google account data

A workspace administrator can choose to connect a Google account so Raabta can offer and book meeting times. When they do, Raabta asks for these permissions:

• Your email address and basic sign-in identity, to show which account is connected.
• View and edit events on your calendars (calendar.events), to create, move and cancel meetings the assistant books.
• View your calendars (calendar.readonly), to check when you are free before offering a time.

We use this data only to check availability and to create, change or cancel meetings for that business. We do not use it for advertising, we do not sell it, we do not share it with data brokers, and we do not use it to train AI models. Access tokens are stored encrypted. Only people in the connected workspace can use the connection, and it can be disconnected at any time from the workspace's connection settings.

Raabta's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can also remove Raabta's access at any time at myaccount.google.com/permissions.

How we use information

To run the service (receive and answer messages, book meetings, show the business its conversations and reports), to review and respond to waitlist requests, to keep accounts secure, and to fix problems. To write replies, the text of a conversation and the business's own content are sent to an AI model provider acting as our service provider. We do not allow that provider to use the content to train its models for other customers.

Who we share it with

Only with service providers needed to run Raabta (hosting and database, the messaging channels a business connects such as Meta's WhatsApp platform, Google when a calendar is connected, and the AI model provider), and where the law requires it. Waitlist and demo details are not shown publicly. No third-party advertising or analytics tracker is loaded on the website.

Security and retention

Connections use HTTPS, passwords are hashed, and channel and Google credentials are encrypted at rest. Each workspace's data is kept separate from every other workspace's. We keep information while a workspace is active and for as long as needed to provide the service. When a workspace is closed we delete its data on request, unless the law requires us to keep something.

Your choices

You can ask to see, correct or delete your information, withdraw consent for follow-up, or disconnect Google at any time. If you are a customer of a business that uses Raabta, please contact that business first; we will help them respond. To reach Raabta directly, use the contact form.

Changes

If we change this policy in a meaningful way we will update the date at the top of this page. See also our Terms of Service.