asm
Start free trial

Privacy Policy

Placeholder. DCCO legal counsel to supply the final Privacy Policy before v1.0.0 RC. The structure below reflects what the final document will cover; it already names the specific processors + retention windows the Service uses today so operational review is accurate.

Last updated: TBD · Data controller: Digital Center Company (DCCO), Riyadh, Saudi Arabia.

1. What we collect

  • Account data: name, email, password hash, workspace slug, locale, timezone.
  • Workspace data: posts, drafts, scheduled content, media, approval state, audit trail.
  • Integration data: OAuth tokens for connected social platforms (encrypted at rest), scoped to the minimum permissions each integration requires.
  • Billing data: MyFatoorah recurring tokens (never raw card numbers), AlOstaz invoice references, workspace billing address.
  • Usage data: page views, feature usage, AI token consumption — for product improvement and plan enforcement.
  • Error telemetry: stack traces and request metadata, sent to Flare (Spatie). Personally identifying fields, OAuth tokens, and BYOK API keys are scrubbed before transmission per the application's config/flare.php censor rules.

2. How we use it

  • Provide and operate the Service.
  • Process billing and issue ZATCA-compliant invoices.
  • Communicate about your account, trial, renewal, and Service incidents.
  • Improve the product via aggregate usage analytics (PostHog, anonymized where the user opts out).
  • Comply with legal obligations.

3. Where we store it

  • Primary: Saudi Arabia (KSA).
  • Backups: secondary region in accordance with Saudi Personal Data Protection Law (PDPL).
  • Transactional email: smtp2go account owned by DCCO.
  • Payments: MyFatoorah. Raw card data is handled by MyFatoorah and never stored by DCCO.
  • Invoicing: AlOstaz. Invoices are ZATCA-compliant and stored for the retention period required by Saudi tax law (currently 6 years).
  • Error telemetry: Flare (Spatie). Retention 90 days.
  • Analytics: PostHog project. Retention per project configuration.

4. Third-party processors

| Processor | Purpose | Data passed | |---|---|---| | MyFatoorah | Payment processing | Billing address, amount, recurring token reference | | AlOstaz | Invoicing + ZATCA compliance | Customer name, address, VAT, amount | | smtp2go | Transactional email | Email address, message body | | Flare (Spatie) | Error telemetry | Stack traces, request metadata (scrubbed) | | PostHog | Product analytics | Anonymized usage events | | Anthropic (Claude) | AI features — caption generation, hashtag suggestions, sentiment | Prompts you choose to send to AI features. Bring-Your-Own-Key (BYOK): requests are billed against your own Anthropic API key, not DCCO's account; DCCO never proxies billable AI on your behalf. | | Google (Gemini) | AI features — alternate provider per workspace | Same as Anthropic. BYOK model. | | Social platforms (X, Meta, LinkedIn, TikTok, Snapchat, WhatsApp) | Publishing + read-back | Content you choose to publish; read scopes as authorized |

5. Retention

  • Active workspaces: retained for the life of the subscription.
  • After cancellation or trial expiry: 30 days full retention (grace) · 30 days soft-deleted archive · then permanent deletion. Timing matches PDPL expectations for lawful deletion.
  • Billing invoices: retained 6 years per Saudi tax law, regardless of workspace state.
  • Error telemetry: 90 days.

6. Your rights under PDPL

You may:

  • Access the personal data we hold about you.
  • Correct inaccuracies.
  • Request deletion (subject to the §5 legal-retention windows).
  • Export your workspace data at any time via /settings/billing / account export.
  • Withdraw consent for optional processing (e.g. opt out of PostHog).

To exercise any of these rights, email privacy@dcco.sa. We respond within 30 days.

7. Security

  • All traffic is HTTPS with a wildcard TLS certificate.
  • OAuth tokens, API keys, and passwords are encrypted at rest.
  • 2FA is mandatory for admin and owner roles.
  • Incident response follows DCCO's internal runbook; we notify affected customers within 72 hours of a confirmed breach, per PDPL.

8. Changes

Material changes to this policy are announced via email 30 days in advance where reasonably practicable.

9. Contact