Privacy policy

Last updated: OPERATOR — set this date before deploying to production.

Replace this template with your own privacy policy before going live. The structure below is a starting point — it must be reviewed by counsel for your jurisdiction (GDPR, CCPA, LGPD, PIPEDA, etc.) before publication. The skeleton mirrors what Fulcrum API already implements technically; fill in operator-specific addresses, retention windows, sub-processor lists, and contact details.

1. What we collect

Email address (used as your sign-in identity), the IP address and User-Agent of each request you make, an audit trail of API key lifecycle events, request logs (endpoint, status code, latency), credit-ledger transactions if billing is enabled, and any data you register for outbound webhooks.

2. What we do with it

Authenticate sign-in (magic-link or OAuth), enforce per-user rate limits and quotas, render your dashboard, and operate the API+MCP surface. Aggregate analytics (counts, latency percentiles) are computed daily over request logs.

3. Where it lives

OPERATOR — list your hosting region(s) + sub-processors. Examples: primary database (Postgres on <provider>), Redis cache, Stripe (billing), Sentry (error monitoring, opt-in), email provider (SMTP / Postmark / Resend).

4. How long we keep it

Audit events: 180 days for non-compliance rows; compliance rows (account creation, billing lifecycle, account deletion) retained indefinitely. API request logs: rolling window per operator policy. After you delete your account, all personally identifying data is anonymized or removed after a 30-day grace period.

5. Your rights

  • Download your data. Visit Account settings and click "Request data export". We email you a signed download link valid for 24 hours.
  • Delete your account. Same page. Account deletion is immediate (API keys revoked, webhooks deactivated); after a 30-day grace period your data is permanently anonymized.

6. Cookies + tracking

Session cookie for sign-in, CSRF cookie for form submissions, and a theme-preference cookie for light/dark mode.

We don't use third-party tracking or advertising cookies.

7. Security

Sensitive fields are encrypted at rest with Fernet; staff access to the operator console requires TOTP 2FA; brute-force lockouts and rate-limits guard authentication surfaces. Full security details: /.well-known/security.txt.

8. Contact

OPERATOR — replace with a real address. Privacy questions / requests / complaints: privacy@example.com.