Version 1.6.0 · Last updated 2026-06-05 · Last reviewed by counsel: NOT YET REVIEWED BY COUNSEL ⚠ This is a first draft published in good faith while attorney review is being arranged.
This Privacy Policy describes how [ENTITY NAME]
([ENTITY ADDRESS]) ("we," "us," "our"), the operator of
temporalBLOCK (the "Service"), collects, uses, and shares personal
information about you when you visit temporalblock.com, sign up for
the waitlist, use the customer dashboard, or call the API.
For European Economic Area, United Kingdom, and Swiss data subjects:
we act as the data controller with respect to information we
collect from you directly (waitlist intake, dashboard accounts), and
as a data processor with respect to content you submit through
the API (the prompts and metadata you send when calling the
Service). The Data Processing Addendum at /dpa governs that
processor relationship.
1. Information we collect
1.1 Information you give us
- Waitlist signup. Your email address, and an optional one-line description of what you're building.
- Account. When you create a dashboard account (via Clerk, our authentication provider), Clerk collects your email, your chosen authentication method (password, OAuth provider such as Google or GitHub), and a hashed password if you chose that method.
- Billing. When you upgrade to a paid plan, our payment processor Stripe collects your billing name, billing address, tax ID where applicable, and the card or bank-account information needed to charge you. We do not see or store your full card number.
- Support. Anything you send us by email or via the support form.
1.2 Information we collect automatically
- API usage logs. For every API call: the API key prefix (we do
not log the full key), the route called, the response status, the
request size, the response time, the source IP, and the
User-Agentheader. We retain these logs for 90 days for abuse-detection, debugging, and security-incident response. - Usage meter. A monthly aggregate of your API calls by tier
(snippet / briefing / deep). The aggregate row in
usage_monthlyis retained indefinitely as billing history; we cannot delete it without losing the audit trail of what you were invoiced for. - Audit log. Significant administrative events (key issuance, key revocation, sub-processor changes, security-relevant config changes) are recorded for 90 days in our Azure Monitor workspace.
- Marketing site analytics. None. We do not run analytics,
ad pixels, or any third-party tracking on
temporalblock.comtoday. If that ever changes, this Privacy Policy will be re-versioned and the new collection will be disclosed before it begins.
1.3 Bring-Your-Own-Key (BYOK) metadata
When you supply an API key for an upstream AI model provider (OpenAI, Anthropic, Google, Perplexity, Brave, SerpAPI), we collect:
- The provider name (so we know whose API to call).
- A metadata fingerprint of the key (for caching and rate-limit attribution within a single request lifecycle).
We do not store the key value itself. We do not write it to
durable storage. It is held in memory for the lifetime of the
single request that supplied it, then discarded. The redaction
behavior is enforced by artifacts/api-server/src/lib/logger.ts and
locked-in by automated test (tests/loggerRedaction.test.ts).
2. How we use information
We use the information we collect to:
- Provide the Service — execute your API calls, surface your usage in the dashboard, send you transactional emails.
- Meter and bill — compute your monthly invoice and produce statements you can download.
- Secure the Service — detect and respond to abuse, fraud, credential leakage, and security incidents.
- Communicate with you — respond to support requests, send service updates, send you a key when your waitlist signup is ready (we do not send marketing email; if we ever do, we will send it from a separate list with proper double-opt-in and an unsubscribe header).
- Comply with legal obligations — respond to lawful requests from regulators and law enforcement, meet tax and accounting requirements.
We do not use the content you submit through the API (your prompts, your data, your BYOK metadata) to train AI models. We do not sell personal information. We do not share personal information for cross-context behavioral advertising.
3. Who we share information with
We share personal information only with the categories of recipients below, and only as needed to operate the Service.
3.1 Sub-processors
We use these third-party providers to operate the Service. Each one has its own published privacy notice and Data Processing Addendum; follow the links to read theirs.
| Provider | Purpose | DPA / privacy link |
|---|---|---|
| Microsoft Azure (Azure App Service, Azure Static Web Apps, Azure Monitor, Azure Database for PostgreSQL) | Cloud hosting, TLS termination, logging, database. | Microsoft Online Services DPA |
| Clerk | Customer authentication for the dashboard. | Clerk DPA |
| Mailgun | Outbound transactional email (waitlist admin notifications today; customer-facing email in the future). | Mailgun (Sinch) DPA |
| Stripe | Payment processing for paid plans and PAYG invoicing. | Stripe DPA |
| OpenAI / Anthropic / Google / Perplexity / Brave / SerpAPI | Only when you opt in by supplying a BYOK key for that provider — your prompt is forwarded to them on your behalf. Each has its own privacy and data-processing terms governing your relationship with them. | See each provider's terms. |
We will give 30 days' notice (via email and via this Privacy Policy's version history) before adding a new sub-processor. If you have a Data Processing Addendum signed with us, you have the right to object to a new sub-processor per the DPA's terms.
3.2 Other sharing
- Legal. We may disclose information if required by law, subpoena, or other valid legal process, or to protect the rights, property, or safety of ourselves, our users, or the public.
- Business transfers. If we are acquired, merged, or sell substantially all of our assets, personal information may transfer to the acquirer subject to the protections in this Policy.
4. Data subject rights
If you are in the European Economic Area, the United Kingdom, Switzerland, California, or another jurisdiction with similar laws, you have rights with respect to your personal information, including:
- Access — request a copy of the personal information we hold about you.
- Rectification — ask us to correct inaccurate or incomplete information.
- Erasure — ask us to delete personal information ("right to be forgotten"), subject to legal and contractual retention obligations (e.g. we cannot delete billing-history rows we are required to retain for tax). If your only data with us is a waitlist signup, you can delete it yourself at https://temporalblock.com/request-deletion — enter your address and confirm via the link we email you, no message to us required.
- Restriction / objection — ask us to limit how we process your information.
- Portability — receive a machine-readable copy of your information.
- Withdraw consent — where processing is based on consent, withdraw it at any time (this does not affect prior lawful processing).
- Complain to a regulator — your local data-protection authority. For EU/EEA residents, that is your country's DPA; for UK residents, the Information Commissioner's Office; for California residents, the California Privacy Protection Agency.
To exercise any of these rights, email support@temporalblock.com with the subject line "Data subject request." We will respond within 30 days. We may need to verify your identity before acting on a request.
California "Do Not Sell or Share My Personal Information": we do not sell personal information and we do not share it for cross-context behavioral advertising, so there is no opt-out mechanism to surface. If that ever changes, we will provide the required disclosure and opt-out.
5. Cookies and similar technologies
The marketing site at temporalblock.com uses only functional
storage — specifically, localStorage keys set by
useVisitorState to remember whether you've already signed up for
the waitlist (so we can collapse the form on return visits). We do
not use cookies for analytics, advertising, or third-party tracking
on the marketing site today.
The customer dashboard at temporalblock.com/dashboard uses
Clerk's session cookies for authentication. These are strictly
necessary for the dashboard to function and cannot be disabled
without logging out.
If we ever add analytics, ad pixels, or any non-functional cookies, this Privacy Policy will be re-versioned and a cookie banner with a granular opt-in will be added before the new collection begins.
6. International data transfers
The Service is operated from Microsoft Azure regions in the United
States. If you access the Service from outside the United States,
your information will be transferred to, processed, and stored in
the United States. Where we transfer personal information out of the
EEA, UK, or Switzerland, we rely on the European Commission's
Standard Contractual Clauses (Decision 2021/914, Module 2:
controller-to-processor) and, for UK transfers, the UK
International Data Transfer Addendum. These mechanisms are
incorporated by reference in the Data Processing Addendum at /dpa.
7. Security
We protect your information with administrative, technical, and
physical safeguards appropriate to the sensitivity of the data and
the risk of harm. Specific measures (TLS posture, key rotation,
PostgreSQL encryption-at-rest, audit logging, access controls,
incident response) are described on the Security page at
/security. No system is perfectly secure; we cannot guarantee
that unauthorized access will never occur.
In the event of a personal-data breach affecting your information, we will notify you and, where required, the relevant supervisory authority within 72 hours of becoming aware of the breach, consistent with GDPR Article 33.
8. Children
The Service is not directed to children under 16, and we do not knowingly collect personal information from children. If you believe a child has provided personal information to us, please email support@temporalblock.com and we will delete it.
9. Retention summary
| Data category | Retention |
|---|---|
| Waitlist email + use-case | Stored as a row in our waitlist_signups database table and forwarded to an admin notification mailbox (kept until manually deleted). We do not write your email address to our server request logs — the signup log line records only a non-reversible hash of your address. Retained until you ask us to remove you, you unsubscribe, or you are converted to a paid account. Delete it yourself at https://temporalblock.com/request-deletion (enter your address, confirm via the emailed link): this removes the database row immediately and the admin mailbox copy is deleted by an operator. (For signups made before this logging change, any residual log copy self-purges within 90 days.) |
| Dashboard account profile | For the life of the account, plus 30 days after closure (export window), then deleted. |
| API request logs (route, status, IP, UA, key prefix) | 90 days. |
usage_monthly aggregate (billing history) | Indefinite — required for tax and audit. |
| Audit log (admin actions, key events) | 90 days. |
| Support email correspondence | 2 years from last message. |
| Billing records (invoices, tax) | 7 years (tax law). |
10. Changes to this Policy
We may update this Policy from time to time. Material changes will be communicated by email and by a version bump visible at the top of this page. The version history is the authoritative record of what version was in effect on a given date.
11. Contact
Privacy / data-subject requests and general inquiries go to support@temporalblock.com. Postal: [ENTITY NAME], [ENTITY ADDRESS].