Paritum Privacy Policy

Last updated: [FILL IN — date of legal review].

Paritum is operated by [FILL IN — Corporate Entity, Inc.]. This policy describes what data Paritum stores when you use the service, what we do with it, who we share it with, and your rights.

What this document covers: the data Paritum reads from Stripe, the account data we store for you, the subprocessors that handle it, how long it’s retained, and how to export or delete it.

Data Paritum reads from Stripe

When you connect Stripe, Paritum subscribes to your account’s webhook events. The free Leak Detector uses read-only OAuth scope and reads these event types:

invoice.payment_failed — failed charge attempts
customer.source.expiring — cards about to expire
customer.subscription.trial_will_end — trial ending soon
customer.subscription.deleted — canceled subscriptions

Paritum reads the event payload, stores the event ID for idempotency (so each event is processed exactly once across retries and redeploys), and stores the fields needed to render your dashboard and power enabled modules. Paritum does not read data unrelated to these event types.

Paid modules that send email on your behalf also read customer email addresses and names on the specific subscriptions they operate against.

Account data Paritum stores for you

Your Paritum account is authenticated via Clerk. Paritum stores your email address, name (if provided), and the Stripe-account relationship linking your Paritum workspace to your connected Stripe account. Authentication tokens and OAuth tokens are stored encrypted.

Subprocessors

Paritum uses the following third parties to run the service:

Stripe — billing and the webhook source itself
Clerk — account authentication
Vercel — application hosting
Railway — PostgreSQL database hosting
Sentry — error tracking (PII is redacted from error context)
[FILL IN — Resend or Postmark] — transactional email delivery for paid modules
BetterUptime — uptime monitoring

Each subprocessor has its own privacy posture; links to their policies are maintained at [FILL IN — subprocessor index URL once published].

How long data is retained

[FILL IN — specific retention windows per data class. Must name: (a) event records, (b) aggregated counts, (c) email send logs, (d) account records after deletion, (e) backups. Per brand-voice §3.7, don’t state a retention period the database doesn’t actually enforce.]

Your rights

You can, at any time:

Revoke Stripe access. From your Stripe dashboard under Connected apps. This stops event ingestion immediately.
Export your data. Contact privacy@paritum.dev — we return your stored event records and account data in machine-readable form within [FILL IN — response window, e.g. 30 days].
Delete your account. Deleting your Paritum account removes your account record and revokes stored OAuth tokens immediately; event records are purged within [FILL IN — deletion window].

If you’re in a jurisdiction with additional rights (GDPR, CCPA), those rights are listed at [FILL IN — link to rights-by-jurisdiction appendix once drafted with counsel].

Security

Paritum’s security posture is documented internally in docs/security.md. Summary: Stripe OAuth tokens are encrypted at rest; webhook signatures are verified via stripe.webhooks.constructEvent; database access is row-level-security enforced per tenant; no tenant-scoped data is logged as error context.

Security reports go to security@paritum.dev. Our public security contact is in security.txt.

Cookies and analytics

[FILL IN — list the cookies the app sets (Clerk session, CSRF) and whether analytics is enabled. Per brand-visual §1 restraint, we don’t run tracking scripts on the marketing site beyond first-party uptime and error monitoring.]

Changes to this policy

We may update this policy. Material changes will be announced via email to the address on file and via an in-product notice at least 30 days before they take effect.

Contact

Privacy questions: privacy@paritum.dev. General operational contact: hello@paritum.dev.