This Privacy Policy explains how we collect, use, store, share, and protect personal data when you use CyberTemp (https://cybertemp.xyz), our API (https://api.cybertemp.xyz), and our mobile app (together, the "Service"). CyberTemp is a disposable/temporary email service that also offers optional registered accounts, private mailboxes, custom domains, and a developer API. We have written this policy to comply with the EU General Data Protection Regulation (GDPR), the ePrivacy Directive ("cookie law"), the UK GDPR, and applicable U.S. state privacy laws including the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA).
A core principle of our Service is data minimization through ephemerality: contents of anonymous, public inboxes are short-lived and automatically deleted, as described in detail below.
Who We Are (Data Controller)
The data controller responsible for your personal data is:
N.R. Digital LLC, a limited liability company formed in the State of New Mexico, USA.
- Registered address: 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, USA
- Contact for privacy matters, data-subject requests, and legal notices: [email protected]
If you are in the EU/EEA or the UK and wish to contact us about how we handle your personal data, please use the email address above.
What Data We Collect and Where It Comes From
We collect data you provide directly (for example, when you register an account, send or receive email through an inbox, set up a custom domain, or make a payment), data generated automatically as you use the Service (for example, IP addresses, browser signals, and antibot data), and data we receive from third parties (for example, OAuth providers and payment processors). The categories below reflect exactly what our systems store.
- Temporary/disposable inbox addresses and email contents — the inbox address and the contents of messages received (subject, body, HTML, sender address, recipient addresses, size, timestamp, and flags). Registered users may enable at-rest AES-256-GCM encryption for their stored mail.
- Registered account data — email and authentication — your account email, hashed password, email-verification status, email prefix, and related authentication records (sessions and verification tokens). For private mailboxes we store the mailbox email and a password hash.
- OAuth provider IDs and third-party account data — if you sign in with Google or GitHub, we store the provider name, your provider account ID, and OAuth tokens (access, refresh, and ID tokens), scope, and session state used to maintain your login.
- API keys — the key value plus creation and last-used timestamps, tied to your user account.
- IP addresses and antibot signals — IP addresses derived from request headers (X-Forwarded-For, CF-Connecting-IP) and stored in fields such as anonymous session records, CLI token records, user logs, and audit logs; transient ban/fail counters are held in Redis.
- Browser fingerprints and anti-bot signals — a composite fingerprint hash, selected browser/header data (user-agent, accept-language, client-hint and fetch headers), WebGL renderer, and user-agent string, used to detect bots and abuse.
- Private email mailbox credentials — bcrypt password hashes for private mailboxes, plus IMAP tokens and CLI tokens (with device name, client version, user-agent, and the IPs at creation and last use).
- Custom domains and domain ownership — domains you register with us, ownership and status flags, and the associated payment reference and amount paid.
- Payment identifiers and transaction records — processor identifiers and transaction records from Stripe (customer ID, subscription ID, session/intent/refund/dispute IDs), cryptocurrency payment records, order records, and a credit-transaction ledger. We do not store card numbers or cryptocurrency wallet credentials; payment-card and crypto-payment data is handled by our PCI-compliant payment processors.
- Support and user-action messages — user-action logs and administrative audit logs (action, metadata, IP address, and user-agent).
- Consent and analytics opt-out flags — your cookie-consent choices (stored in your browser's localStorage) and analytics opt-out state.
- Server logs and access logs — application console logs, process logs, and reverse-proxy/CDN access logs, which may include IP address, user-agent, request path, and response code.
- Session and authentication state — authentication cookies and session records used to keep you signed in and to verify paid status.
- Webhooks and Elite-tier integrations — for users who configure webhooks, the destination URL, signing secret, subscribed events, status, and (on failed deliveries) the delivery payload and error details.
- Team and collaboration data — team names and ownership, member roles, invitations (invitee email, token, acceptance/expiry), and team activity events.
- Add-ons, plans, and billing — add-on subscriptions and their status, plan and billing metadata, API credits, and coupon usage.
- Audit and compliance logs — administrative audit logs and abuse-ban records (scope, value, reason, evidence, status, and timestamps).
- Passkey credentials (WebAuthn) — credential ID, public key, signature counter, device type, and related metadata for passwordless sign-in.
Because messages received in any inbox can contain whatever a sender chooses to include, email subjects, bodies, HTML, and addresses may contain personal data (names, addresses, phone numbers, links, codes, and so on). We do not control what senders include.
Purposes and Lawful Bases for Processing
We process personal data only where we have a lawful basis under the GDPR / UK GDPR. The table below maps the main processing activities to their lawful bases, consistent with our data inventory.
| Processing activity | Purpose | Lawful basis |
|---|---|---|
| Receiving and displaying anonymous/public inbox email | Deliver the core disposable-email service | Legitimate interest in providing the requested service; consent through service usage |
| Storing private registered mailbox email | Deliver the paid mailbox service | Performance of a contract; legitimate interest; consent |
| Account credentials, sessions, verification, passkeys | Create and secure your account; authenticate you | Performance of a contract; legitimate interest in security |
| OAuth sign-in (Google/GitHub) | Provide optional social login | Performance of a contract; consent |
| API keys, CLI tokens, IMAP tokens | Provide and secure API/programmatic access | Performance of a contract; legitimate interest in security auditing |
| IP addresses, fingerprints, antibot signals, rate-limit/event logs | Prevent fraud, bots, and abuse; enforce rate limits; platform safety | Legitimate interest in fraud and abuse prevention; contract |
| Custom domains | Provide custom-domain inboxes | Performance of a contract; legitimate interest in address allocation |
| Payments and transaction records | Process payments; prevent payment fraud; meet tax/accounting duties | Legal obligation (tax/accounting); performance of a contract; legitimate interest in fraud prevention |
| User logs and admin audit logs | Security, compliance, and accountability | Legitimate interest; legal obligation (audit trail) |
| Webhooks and delivery logs | Deliver event notifications you configure | Performance of a contract; legitimate interest in delivery logging |
| Team and collaboration data | Provide team features and collaboration audit trail | Performance of a contract; legitimate interest |
| Add-ons, plans, coupons, credits | Manage subscriptions and billing | Performance of a contract; legitimate interest in billing |
| Analytics and session replay (PostHog) | Product analytics, performance monitoring, UX improvement | Consent (EU/EEA/UK and where required); legitimate interest elsewhere |
| Geolocation (country) for regional pricing | Apply regional pricing and detect pricing abuse | Performance of a contract; legitimate interest in abuse prevention |
Where we rely on consent (for example, analytics and session replay in the EU/EEA and UK), you may withdraw it at any time without affecting the lawfulness of processing carried out before withdrawal. Where we rely on legitimate interests, you have the right to object (see "Your Rights").
How Long We Keep Data (Retention)
We keep personal data only as long as needed for the purposes above, then delete or anonymize it. Our automated cleanup jobs apply the following retention periods:
- Anonymous/public inbox email contents — automatically deleted 10 minutes after receipt.
- Private registered mailbox email contents — automatically deleted after 7 days. Users with the long-retention add-on can extend this to up to 90 days via their expiry preference.
- Anonymous session records (fingerprints, IP, browser data) — automatically deleted after 10 minutes; session-history rows are deleted together with their parent session.
- Private email account credentials — accounts inactive for 30 days are automatically deleted (purged where the last update is older than 30 days).
- API keys — kept while active; orphaned keys with no balance that have not been used for 30 days are automatically deleted. You can delete keys manually at any time.
- User action logs — kept for 7 days.
- Rate-limit and antibot event logs — kept for 3 days; transient Redis ban/fail flags expire on their own (temporary bans last 1 hour). Permanent bans have no automatic expiry and are removed only by an administrator.
- CLI tokens, IMAP tokens, sessions — kept while active; CLI and IMAP tokens are retained until revoked or until the account is deleted; expired sessions are cleaned up at query time.
- Payment and transaction records — retained on a long-term basis (typically 7 years or longer) to meet tax, accounting, and audit obligations; raw webhook payloads are preserved for audit.
- Account records and preferences — kept while your account exists. Deleting your account cascades deletion to related records (inboxes, API keys, webhooks, team memberships, sessions, passkeys, and similar). Password fields are never independently deleted and are cleared on account deletion.
- Custom domains, teams and team data, add-on subscriptions, webhook configurations, audit logs, and ban records — retained while active or for accountability/audit purposes; these are not subject to automatic time-based deletion, and team/domain data is deleted via cascade when the parent account or team is deleted.
- Analytics data (PostHog) — retained per our configured PostHog retention (a 30-day default for session replay), subject to PostHog's data policy.
- Server, CDN, and reverse-proxy logs — application/process logs typically rotate on roughly a 14-day cycle; Cloudflare access logs are retained per Cloudflare's plan defaults (typically a few days on the free tier).
Who We Share Data With (Recipients and Processors)
We do not sell your personal data. We share it with a limited set of service providers ("sub-processors") who process it on our behalf under contractual data-processing terms that require them to protect it and use it only for the purposes we specify. Our sub-processors are:
- Stripe — payment processing for subscriptions and credit packs. Receives tokenized payment method, billing address, subscription ID, user email, plan type, transaction amounts, and country for geo-pricing abuse detection.
- Cryptocurrency payment processor(s) — where you choose to pay with cryptocurrency, a third-party crypto-payment processor handles the transaction. Receives the data needed to process and confirm the payment (such as the transaction/order identifiers, amount, and currency); we store the resulting transaction records but do not store wallet credentials.
- Supabase — authentication, session management, and database storage for accounts, teams, emails, and transactions. Receives email addresses, hashed passwords, user profiles, authentication tokens, subscription status, plan metadata, billing intervals, and session data.
- PostHog (hosted in the European Union) — product analytics, event tracking, session replay (10% sampled, with form inputs masked), and performance/crash monitoring. Receives user IDs, event properties, session recordings, browser/device information, and performance metrics.
- Google (Google Analytics) — web analytics and event tracking via analytics cookies. Receives analytics event and usage data associated with the analytics cookie. This runs only where analytics is enabled (see "Cookies and Analytics").
- Crisp Chat — real-time customer support chat. Receives session ID, support chat messages, and the IP address implicit in the session.
- Resend — transactional email delivery (verification, invoices, team invitations, payment confirmations). Receives recipient email addresses and email content such as verification links and invoice details.
- Cloudflare Turnstile — CAPTCHA/bot prevention on login and registration. Receives IP address, browser headers, the CAPTCHA token, and the verification result.
- hCaptcha — alternative CAPTCHA/bot prevention. Receives IP address, browser headers, response token, and challenge result.
- Google OAuth — optional social login. Receives/returns email address, name, profile picture, and a transient OAuth token.
- GitHub OAuth — optional social login. Receives/returns GitHub username, email address, public profile information, and a transient OAuth token.
- IP-API — IP geolocation for regional-pricing detection (results cached for 24 hours). Receives your IP address solely to determine a country code.
- Cloudflare CDN/WAF — content delivery, DDoS protection, web application firewall, and geolocation header injection. Processes all HTTP request/response traffic, including IP addresses, headers, request bodies, and access logs.
We may also disclose personal data where required by law, to enforce our terms, or to protect the rights, safety, and security of our users, the Service, or others.
International Data Transfers
We are based in the United States, and our sub-processors may process data in the United States and other countries. When we transfer personal data of individuals in the EU/EEA or the UK to a country that has not been deemed to provide an adequate level of data protection, we rely on appropriate safeguards, including the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum where applicable), together with supplementary measures as needed. You can request more information about these safeguards using the contact details in this policy.
Cookies and Analytics
We use cookies and similar technologies in three categories: Essential (required for the Service to function, such as authentication, CSRF protection, paid-status verification, and antibot handshake tokens), Functional (such as language preference and UI state), and Analytics (PostHog and Google Analytics). Our cookie banner lets you control these categories, and analytics is off by default until you accept it.
For analytics and session replay (PostHog), we operate a region-aware consent model:
- If you are in the EU/EEA or the UK, analytics and session replay run only after you opt in (prior consent).
- Elsewhere, they run on an opt-out basis, and you can disable them at any time through the cookie banner.
Session replay is sampled (a 10% rate) and is disabled on sensitive paths such as admin, settings, authentication, checkout, and API routes; recorded form inputs are masked. For a full list of cookies, their categories, and durations, please see our Cookie Policy.
Your Rights
Depending on where you live, you have rights over your personal data. For individuals in the EU/EEA and the UK, these include the right to:
- Access the personal data we hold about you;
- Rectify inaccurate or incomplete data;
- Erase your data ("right to be forgotten");
- Restrict processing in certain circumstances;
- Data portability — receive your data in a structured, commonly used, machine-readable format;
- Object to processing based on legitimate interests, and to object to direct marketing;
- Withdraw consent at any time where processing is based on consent (for example, analytics).
You also have the right to lodge a complaint with a supervisory authority — in the EU, your local Data Protection Authority, and in the UK, the Information Commissioner's Office (ICO) — although we encourage you to contact us first so we can try to resolve your concern.
Note that for anonymous, public inboxes, message contents are automatically deleted within 10 minutes and anonymous session records within 10 minutes, so in many cases the data may no longer exist by the time a request is made; you can also delete inbox contents yourself within the Service.
How to Exercise Your Rights and Response Times
To exercise any of these rights, email us at [email protected]. We may need to verify your identity before acting on a request, particularly for account or mailbox data. We will respond without undue delay and within one month of receiving your request, as required by the GDPR/UK GDPR; this period may be extended by up to two further months for complex or numerous requests, in which case we will let you know.
Automated Decision-Making and Profiling
We do not make decisions that produce legal or similarly significant effects about you based solely on automated processing. We do use automated systems for anti-abuse, anti-bot, fraud prevention, and rate limiting (using IP addresses, browser fingerprints, and related signals). These measures are intended to protect the Service and its users; if you believe an automated anti-abuse measure has affected you in error, you can contact us at the address above.
Children's Privacy
The Service is not directed to children. You must be at least 16 years old to use the Service (or at least 13 where permitted by local law with appropriate consent). We do not knowingly collect personal data from children below the applicable age. If you believe a child has provided us personal data, please contact us and we will delete it.
Security
We use technical and organizational measures to protect personal data. These include hashing of account and mailbox passwords (using bcrypt/scrypt), optional at-rest AES-256-GCM encryption for registered users' stored email, HMAC-signed and short-lived authentication and paid-status tokens, CSRF protection, antibot and rate-limiting controls, and delivery of the Service over Cloudflare's CDN/WAF with DDoS protection. We also keep audit logs of administrative actions. No method of transmission or storage is completely secure, but we work to protect your data and to limit retention as described above.
Your California Privacy Rights (CCPA/CPRA)
If you are a California resident, you have the right to:
- Know the categories and specific pieces of personal information we have collected, the sources, the purposes, and the categories of third parties with whom we share it;
- Delete personal information we have collected, subject to legal exceptions (for example, transaction records we must keep for tax and accounting purposes);
- Correct inaccurate personal information;
- Opt out of the "sale" or "sharing" of personal information; and
- Not be discriminated against for exercising your rights.
We do not sell personal information for money. Our use of analytics cookies may be considered "sharing" for cross-context behavioral advertising purposes under the CPRA; you can control analytics through our cookie banner (and analytics is off by default until accepted). The categories of personal information we collect, our purposes, and the recipients are described in the sections above. To submit a California rights request, email us at [email protected]; you may use an authorized agent, and we will verify requests as required by law.
Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make material changes, we will update the "Last updated" date shown with this policy and, where appropriate, provide additional notice. Please review this policy periodically.
Governing Law
This Privacy Policy and any disputes relating to it are governed by the laws of the State of New Mexico, USA, without prejudice to any mandatory data-protection rights you may have under the laws of your country of residence.
Contact Us
For any questions, requests, or complaints about this Privacy Policy or our handling of your personal data, contact the data controller:
N.R. Digital LLC 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, USA Email: [email protected]