Privacy policy — Singularity API

01Who we are and what this covers

Singularity API operates the reserved-lane service available at singularityapi.tech and app.singularityapi.tech (the “Service”). This policy covers the website, the dashboard and the API endpoint. Inference content is covered separately, and more strictly, by our zero-data-retention policy.

02What we collect

Information	Where it comes from and why
Email address and password hash	Your sign-up. Used to authenticate you, send account emails (confirmation, password reset, approval) and identify your account in support.
Beta application answers: time zone, daily coding hours, use case, estimated cache-hit rate; optionally monthly spend, providers and tools you use	Provided by you when applying. Used to review applications, plan capacity and understand how the lane is used. Never sold or shared.
Bookings, credit balance and ledger entries	Generated by your use of the dashboard. Needed to reserve capacity and account for credits.
Purchases, refunds and disputes	Generated when you buy credits. We store the amount, the pack, timestamps and our payment processor's transaction identifiers. We never receive or store card numbers.
API usage metadata: timestamps, model id, token counts, latency, status	Generated by API requests. Used for usage reporting, reliability and automatic service credits. Contains no request content.
Technical data: IP address, browser type, session cookies	Generated when you use the website or dashboard. Used to keep you signed in, secure accounts and prevent abuse.
Messages you send us	Discord, email or in-app problem reports. Used to respond and improve the Service.

We do not use tracking pixels or advertising cookies on this site. The dashboard uses only the cookies required for your session.

03How we use it

To provide the Service: authenticate you, reserve capacity, admit your API key during booked hours, meter usage and maintain your credit balance.
To bill you: process purchases and refunds through our payment processor and keep the records that tax and accounting rules require.
To keep the Service reliable and safe: detect abuse, investigate incidents and issue service credits when a booked hour is disrupted.
To communicate: transactional emails about your account, and replies to your questions. We do not send marketing email without your consent.
To improve the product: aggregate, de-identified usage statistics such as those in our beta report.

We do not sell personal information and we do not use your data, or anything you send to the model, to train machine-learning models.

04Who we share it with

We use a small number of service providers to run the Service. Each receives only what its function requires and is bound by its own contractual confidentiality and security obligations:

A payment processor (Stripe) for purchases, receipts, refunds and fraud prevention. It receives your email, the amount and your payment details, which we never see.
An authentication and database provider that stores account records and sends account emails on our behalf.
Cloud and accelerator capacity providers that run the website, the gateway and the model. Request content passes through their machines in memory only, under the zero-data-retention policy, and is never stored by them on our behalf.

Beyond these providers we disclose information only if the law requires it, to protect the rights and safety of users or the Service, or with your direction. If the business is transferred, this policy continues to apply to the information transferred.

05How long we keep it

Data	Retention
Model inputs and outputs	Not retained. See the zero-data-retention policy.
Account and application data	For the life of the account, then deleted within 30 days of a deletion request or account closure.
Bookings, ledger and usage metadata	For the life of the account; financial records for as long as tax and accounting law require (typically up to 7 years) in de-identified or minimised form after closure.
Purchase and refund records	As long as tax, accounting and payment-dispute rules require.
Security logs (IP addresses, sign-in events)	Up to 90 days.
Support conversations	Until resolved plus a reasonable period, or on request.

06Your choices and rights

Access and export: ask us for a copy of the personal information we hold about you.
Correction: change your email or details through the dashboard, or ask us.
Deletion: ask us to close your account and delete your information, subject to the financial records we must keep.
Objection and restriction: tell us if you object to a particular use; we will explain what the Service still needs in order to function.
Complaint: you may complain to the data-protection authority in your country. We would appreciate the chance to resolve it first.

To exercise any of these, message us on Discord from an account linked to your email, or reply to any email we have sent you. We respond within 30 days.

07Security

All traffic uses TLS. Account passwords are stored only as salted hashes. Secrets that protect the Service are held outside the code base with restricted access, and administrative access to account data is limited to the people who operate the Service and is logged. No system is perfectly secure; if we learn of a breach affecting your data we will notify you without undue delay.

08International transfers and children

The Service is operated with providers in more than one country, so your account information may be processed outside the country you live in, always under this policy. The Service is intended for adults and businesses; we do not knowingly collect information from anyone under 16.

09Changes to this policy

We will post any changes on this page and update the effective date. Material changes will be announced to account holders by email or in the dashboard before they take effect.