Privacy policy
Sphere Consulting Group LLC, a Wyoming limited liability company at 30 N Gould St Ste R, Sheridan, WY 82801, United States, operates Modelworks. This page says what is collected when you use the API or this site, why, and for how long.
Last updated 29 October 2026.
The short version
Text you send for synthesis is not stored. It is processed to produce the audio and discarded when the request completes, and the audio is not stored either. The service keeps request metadata for 30 days, and no request content at all. The site sets no cookies and runs no analytics, no error tracking and no advertising.
This policy covers the services that are live, which today means text-to-speech. Modelworks is built to carry other model families on the same gateway; when one is offered, this page is updated and dated before it goes on sale, and it will say what that service collects.
What is collected
Text you submit. Processed in memory to generate audio and discarded when the request completes. Never written to a database, never used to train anything, never read by a person.
Audio generated for you. Returned in the response and not retained.
Request metadata. Timestamp, endpoint, byte count, HTTP status, the API key used, and the referring page for a visit to this site. Kept for 30 days, then deleted.
What request metadata does not contain. The text or audio, the client's IP address, the port, and the browser's User-Agent. The web server deletes the address and the User-Agent before a log line is written, so the log cannot be used to identify a visitor, including by us.
Account data. If you get a key, we hold the email address you wrote from, the key itself (stored hashed by the gateway, never in plaintext), the allowance attached to it, and the spend records the gateway produces.
Billing data. Payments go through Paddle.com, which is the merchant of record. Paddle collects and handles the payment details, the invoice and the tax. We never see your card details. We see the billing contact details and the amounts of invoices and refunds.
Email you send us. Kept for as long as it takes to answer and to keep a record of the answer.
No cookies and no third-party scripts. This site is static HTML with no JavaScript, so there is nothing to set a cookie or run a tracker, and no consent banner because there is nothing to consent to. The server does keep a request log, and what it does and does not contain is set out below.
Why it is collected, and on what basis
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the service you asked for | Submitted text, key, allowance | Performance of a contract, GDPR Article 6(1)(b) |
| Running and securing the service - metering, abuse prevention, debugging | Request metadata, key, spend records | Legitimate interests, Article 6(1)(f) |
| Taking payment and meeting tax and accounting obligations | Billing contact details, invoice and refund amounts | Legal obligation, Article 6(1)(c) |
| Answering your email | Your address and the message | Legitimate interests, Article 6(1)(f) |
Nothing is profiled, and no decision about you is automated.
Who it is shared with
Paddle.com Market Limited is the merchant of record for purchases. For the payment it acts as an independent controller, and its own privacy notice applies to that processing.
Service providers that run the system are listed, with what each one can see, on the sub-processor page. There are two: the compute host in the EU, and a DNS provider that never sees request content. There is no analytics vendor, no error-tracking service, and no third-party AI provider anywhere in the path.
Directories and demos, when they exist. If the API is listed in a third-party directory or offered through a hosted demo, the text sent through that route passes through the platform running it before it reaches us, and that platform's own notice applies to its part. Nothing of that kind is live today. If one goes live, this page names the platform and what it sees before the integration is opened.
Nobody else. Data is not sold, rented or shared for advertising, and there is no third party in the path to sell it to. Advisers and authorities receive data only where the law compels it, and a successor entity only if the business is sold, under the same terms as this page.
Where it goes
The company is in the United States and the compute is in the European Union. Administration happens from India. Those transfers are covered by the EU Standard Contractual Clauses in the Data Processing Agreement, which is published on this site and takes effect with the terms. A Transfer Impact Assessment records the channels and the safeguards, and is available on request too.
How long it is kept
| Data | Kept |
|---|---|
| Submitted text and generated audio | Not at all - discarded when the request completes |
| Request metadata | 30 days |
| Account and key records | While the key exists, and for as long as needed to keep the service secure |
| Invoices and tax records | As long as tax law requires |
| Email correspondence | As long as needed to answer it and keep the record |
Your rights
Under the GDPR, and under India's Digital Personal Data Protection Act 2023 where it applies, you can ask to see the personal data held about you, have it corrected or erased, restrict or object to its processing, and receive it in a portable form.
Email support@modelworks.dev. Ask from the address on your account where you can, because that is how the request is verified. A request is answered within 30 days.
If you are in the EU or the UK you also have the right to complain to a supervisory authority in the country where you live or work.
One limit worth stating plainly: because submitted text is not retained, there is nothing to retrieve or delete on request. That is the point of the design, and it also means an access request can only ever return account and metadata records.
Children
The service is not directed at children, and it is not to be used by anyone under 16.
Security
How the system is built and what it does not claim is on the security page. Security reports, privacy questions and data requests all go to support@modelworks.dev.
Changes
Material changes to this policy are published here with a new date. The previous text is not kept online; if you need it, ask.