Last updated: draft, not yet published.
Account data: your email address, and your Organization's name.
Customer data you enter: names, phone numbers, payment amounts, currencies, payment history, and follow-up notes for the customers you track. This is entered by you or your team, not collected from your customers directly.
To run the Service: showing your follow-up schedule, tracking balances, letting your team collaborate on shared customers. We don't use your data for advertising, and we don't sell it.
Most AI features — call scripts, call plans, call notes, the chat assistant, risk scoring, payment-plan suggestions, objection responses, reminder drafts, and message translation — send a summary of your customer data (including full payment and contact history, not just recent activity) to Google's Gemini API to generate suggestions. Before anything is sent, customer names and phone numbers are replaced with placeholder labels ("Customer A", "Customer B", ...) — only amounts, currency, contact/reminder history, and follow-up timing reach the AI provider. Real names are restored only in your browser, after the response comes back.
Two features are narrow, deliberate exceptions to that pseudonymization, because the task itself requires the real content:
Name transliteration sends only the customer's or team member's actual name (nothing else — no balance, phone, or notes) to render it in the other script.
Receipt/check photo scanning (Business plan) sends the photo you choose to scan directly to Gemini to read the amount, date, and reference number off it — a photo can show a signature, account number, or payer name that can't be pseudonymized. The photo itself is never stored by Rasid; it's read once and discarded.
While Rasid is in private testing and not yet publicly launched, our Gemini API usage is on Google's free tier, under which Google's terms permit prompts to be used to improve their models. We will move to a paid tier — where Google does not train on prompts — before any public launch.
Supabase hosts our database, authentication, and backend functions — your data is stored with them as our infrastructure provider, isolated from every other Organization's data at the database level (Postgres Row-Level Security), not just in application code.
Google (Gemini API) processes the pseudonymized summaries (and the two narrow exceptions) described above, if you use the AI features.
Our payment provider (once billing is live) will process payment information for paid plans; we don't store your card details ourselves.
Sentry receives error/crash reports so we can fix bugs — diagnostic data (what went wrong, where), not your customer records.
PostHog receives basic product-usage data (which screens are used, how often) to help us improve the Service, identified only by an internal account ID, not your email. Session recording and screen capture are turned off, specifically because your customers' data appears on those screens.
Resend delivers transactional emails on our behalf (team invites, daily digests, auto-send reminders, and messages sent through our website's contact form) — it sees the recipient's email address and the email's content.
Running the Service means your data may be processed outside your own country:
Supabase (database, auth, backend functions) — hosted in Mumbai, India.
Google (Gemini API) — processed on Google's infrastructure, primarily in the United States.
Resend (transactional email) — US-based delivery infrastructure.
Sentry (error monitoring) — hosted in the EU (Germany).
PostHog (product analytics) — hosted in the United States.
Each provider publishes its own safeguards for cross-border transfers (such as Standard Contractual Clauses) as part of their own compliance programs; we rely on those rather than running our own regional infrastructure at this stage.
You can export your Organization's data at any time. An account manager can permanently delete an individual customer's personal data (name, phone, notes) directly in the software — their payment history is kept, fully anonymized, for the Organization's own accounting records. Closing your account removes your access; contact support if you want your whole Organization's data deleted rather than retained for legal/accounting reasons.
Data is isolated per Organization at the database level. Access requires authentication, and team member permissions are role-based (manager, admin, agent) — an agent only sees the customers assigned to them.
We may update this policy as the Service evolves. Material changes will be communicated in advance.
Questions about this policy, or a data request — see our Contact page.