Privacy Policy

This policy explains what Hereling collects, why, and how long we keep it. We designed Hereling to see as little as possible.

1. Data about you (the account holder)

• GitHub account id, username, and email address, used to sign you in and to send account and alert emails.
• Billing status from Paddle (plan, subscription state). Card details are handled by Paddle and never reach us.
• Waitlist email addresses, used only to tell you when Hereling opens.

2. Data about your application's usage

For each AI request that passes through our proxy or that you report to us, we store:

• your project id, the user id you send us, and the feature name you send us;
• model name, input and output token counts, cost in USD, duration, and HTTP status;
• a timestamp.

We do not store the request body (prompts, messages, system instructions) or the response body (generated text). We do not store your AI provider API key; it is forwarded in memory and discarded.

3. Data from your payment providers

From Stripe, Paddle, or RevenueCat webhooks we store: the user id you attached to the event, plan name, amount, currency, event type (purchase, renewal, cancellation), and timestamp. A webhook notification can carry more than that: for example, a Stripe checkout event may include your customer's name, email, or billing address. We hold the notification in memory only to verify its signature and pick out the fields above; the rest is not written to our database or logs and is gone once the request ends. We never receive card numbers.

4. Your customers' identifiers

The user id you send us is chosen by you. We recommend using an opaque id rather than an email address. Hereling treats it as a label and never contacts your users.

5. Where data lives and who processes it

• Hosting and proxy: Vercel.
• Database and authentication: Supabase.
• Email: Resend.
• Payments: Paddle.

These providers process data on our behalf under their own data processing terms.

6. Retention

On Free, individual AI request details become eligible for deletion after 7 days; a daily cleanup removes them in batches. On Pro, we keep those details while Pro access is active. When the project returns to Free, a 30-day grace period starts; after that, cleanup removes details older than 7 days. An upgrade cannot restore details already deleted. Failed or backlogged cleanup jobs require a retry.

Separate accounting records remain until you delete the project: per-user lifetime and monthly totals, monthly request counters, revenue events and payment references used to reconcile refunds and prevent duplicate counting, subscription status, and project settings (including rules and alerts). Spending reservations and request details with an unresolved settlement also remain so deleting history cannot release an unknown charge or reset a spending limit. These records include the user identifiers you supplied; they are not anonymous.

Usage delivery receipts and event identifiers remain until project deletion to prevent duplicate recording and explain missing data. Pending retry records retain the numeric usage and labels needed to finish recording; that retry payload is removed after recording or a quota rejection. API keys and conversation content are never part of that payload.

Project deletion removes its data from the active database, including accounting records, keys and webhook settings. It does not cancel a Paddle subscription: cancel it in Manage billing and wait until it has ended before deleting the project. Unresolved checkouts also block deletion until their billing status is confirmed; contact support if a checkout was abandoned. Your Hereling account and other projects are separate. Account and waitlist deletion requests are handled through support; there is no automatic account-deletion timer or waitlist-close cleanup.

Database backups have a separate retention period controlled by the hosting configuration. Deleting a project does not immediately erase it from existing backups. We keep a minimal deletion receipt (project id and deletion date) for recovery checks. Our recovery procedure requires reapplying deletions and expired usage cleanup before restored data is served. Contact support for the applicable backup retention period; we do not promise a fixed backup-erasure deadline here.

7. Your rights

In your project's Settings → Project data, you can download retained data as JSON or permanently delete the project. Exports exclude credentials and read live data; pause ingestion and edits for a stable copy. For account deletion, a specific customer's records, or help with an export, ask us at support@hereling.com. If you are in the EU or UK you have the rights described in the GDPR, including access, correction, deletion, and portability.

8. Cookies

We use only the cookies needed to keep you signed in. No advertising or cross-site tracking cookies.

9. Changes

If we change this policy in a meaningful way we will email account holders before the change takes effect.