RichbeeQuickstart

Attorney review pending. This document is a draft and is not in effect.

Privacy Policy — Richbee Business Services ([service].richbee.ai)

Effective: {{EFFECTIVE_DATE}} · Operator: {{LEGAL_ENTITY}} ("Richbee", "we") · Contact: {{PRIVACY_EMAIL}}, {{POSTAL_ADDRESS}}

1. Scope and roles

Richbee provides agent-only business services (API and MCP endpoints, no user interface): CRM first, then KMS, BPM, DMS and ATS (each a "Service" at [service].richbee.ai).

  • Customer Data (records your agents create, such as CRM contacts or ATS candidates): Richbee is a processor / service provider; the customer is the controller / business. The Data Processing Terms (Terms of Service §9) govern it. End users (for example your contacts or candidates) should send privacy requests to the customer; we forward any we receive without responding ourselves unless instructed.
  • Account Data (account owner name, email, billing details, API key and OAuth client metadata, usage and audit records): Richbee is the controller. This policy covers it.

2. What we collect (Account Data)

  • Account and contact: name, business email, company.
  • Billing: handled by Stripe; we receive the customer ID, plan, invoices and the card's last 4 digits and brand, never full card numbers.
  • Credentials (planned): scoped API keys sent as Bearer tokens, of which we store only hashes; OAuth 2.1 client and grant records for MCP clients.
  • Logs (planned): request ID, endpoint, status, timing, IP address and key ID, in Cloudflare Workers Logs kept about 3 days. Secrets and record bodies are excluded.
  • Audit trail (planned): every write is logged with tenant ID, key, action, record ID and timestamp, with no record contents.
  • Communications: support and service-notice emails. No email provider has been chosen yet; one will be listed in subprocessors.md before use.
  • Analytics: no marketing analytics or advertising trackers. We may use Cloudflare's built-in aggregate traffic analytics and an error-tracking tool (not yet chosen; it will be listed before use and configured to exclude record contents).

3. How we use it

To provide and secure the Services, authenticate agents, bill, prevent abuse, give service and legal notices, and comply with law. We do not sell or share personal information (as CCPA defines those terms), do no targeted advertising, and do not use Customer Data to train AI models. No AI provider processes Customer Data; our internal evaluations use synthetic data only. If that changes, we will list the provider in subprocessors.md and give notice first.

4. Where data is stored

Planned: Neon Postgres in AWS US East (N. Virginia), region aws-us-east-1, and Cloudflare (Workers compute, KV, and R2 for exports and attachments; no D1). Wording: "stored in US data centers, processed primarily in the US" (Cloudflare serves requests at its global edge). [ATTORNEY: confirm wording given edge processing; OPEN: R2 US location setting.]

5. Retention and deletion (planned design)

  • Customers can export all data (a JSON + CSV bundle with checksums, through a short-lived signed link) and delete single records or the whole account at any time through the API/MCP.
  • Account deletion requires confirmation, then a 7-day grace period by default, which the customer can skip. When the grace period ends, the database, R2 storage, search indexes and caches are purged within 24 hours, and we issue a deletion receipt (identifiers and timestamps only, no content). Single-record deletions are purged on the same 24-hour basis.
  • Backups: deleted data stays in Neon's point-in-time restore history until it expires, within {{BACKUP_RETENTION}} after purge. That is currently 6 hours on Neon's Free plan; it rises if we change plans (Launch allows up to 7 days), and we will update this policy before it does. If we ever restore, we re-apply deletions before data is used again.
  • Retained after deletion: (a) billing records held by Stripe under Stripe's terms and tax law; (b) a minimal audit trail (tenant ID, action, timestamps, no record contents) and the deletion receipt, kept for {{RETAINED_RECORDS_PERIOD}} [draft default: 3 years, pending Israel, CPA and attorney].

6. Your rights

Depending on where you live (for example under the Texas TDPSA, California CCPA or GDPR/UK GDPR), you can ask to access, correct, delete or port your data, and opt out of sale, targeted advertising or profiling (we do none). Email {{PRIVACY_EMAIL}}. We respond within 45 days (TDPSA §541.052; CCPA), and you can appeal a refusal by replying "Appeal" (TDPSA §541.053). We will not discriminate against you for exercising your rights. [ATTORNEY: confirm whether the TDPSA small-business exemption (§541.002) applies; we keep these commitments anyway.]

7. Security (planned)

Encryption in transit and at rest; tenant isolation through tenant ID plus Postgres row-level security; scoped, hashed API keys; OAuth 2.1 for MCP; audit logging of every write. No SOC 2/ISO certification held.

8. Children

Not directed at children under 13; we do not knowingly collect their data.

9. Changes

We post updates here and email account owners about material changes at least {{NOTICE_DAYS}} days in advance.