Privacy Policy
Last updated: 23 September 2026
This policy explains what Goalfinder collects when you use the API and the dashboard, what we do with it, and — importantly — what happens to your prompts once they leave us. Plain language, no surprises.
1. What we collect
We keep this deliberately minimal. We collect:
- Account data — the email address you sign up with, and an authentication record. We do not ask for your name, phone number or date of birth.
- Billing data — which pack you bought, the amount, and the timestamp. Your card details are handled entirely by our payment processor; they never reach our servers and we cannot see them.
- API keys — stored only as a SHA-256 hash, plus the key's display prefix. We never store the full key after you create it, which means we cannot recover it for you if you lose it.
- Usage metadata — for each request: the model ID, token counts (prompt, completion and cache), the cost deducted, the API key used, and the time of the request.
2. What we do not store
We do not store the content of your prompts or the model's responses.
Your messages are streamed through our gateway to the upstream provider and are not written to our database, our logs or our backups. The usage_logs table records counts and costs — never text.
The one practical exception is the standard web-server logging that any internet service performs (request paths, status codes, IP addresses) for security and abuse prevention. We do not mine that data, and we do not tie it to your prompt content.
3. Your data reaches our upstream model providers
Please read this section before sending confidential material through the API.
Goalfinder is a gateway. To answer your request, we must forward your prompt — in full — to the provider that serves the model you called. Whatever that provider does with your content is governed by its policies, not ours, and we cannot override them.
We currently route to three model families. Their published data practices differ significantly, so treat them as different products:
| Provider | Retention | Training on your data |
|---|---|---|
| DeepSeek | No fixed retention window published; data may be processed and stored in China. | May be used for training by default. |
| Z.ai (GLM) | No fixed retention window published; content may be retained for service operation, security and abuse prevention. | May be used for training under its consumer terms. |
| Alibaba Qwen | Inputs and outputs are processed in memory for the duration of the request and not retained in persistent storage. | Not used for training — an explicit published commitment. |
In short: DeepSeek and Z.ai may retain your inputs and may use them to train their models. Qwen has committed that it will not. Choose your model accordingly.
4. Choosing the right model for the data
- Do not send secrets, credentials, personal data about other people, regulated data, or material under a confidentiality obligation to DeepSeek or Z.ai.
- If your use case requires inputs that are not retained and are never trained on, route those requests to the Qwen models.
- Provider policies change without notice. We summarise them here in good faith, but the provider's own current policy is the authoritative text — please verify it before relying on this table for a compliance decision.
5. How we use what we collect
Account and usage metadata is used to authenticate your requests, meter and bill usage correctly, run the dashboard that shows your balance and request history, prevent abuse, and provide support when you contact us. We do not sell your data, and we do not use your prompts or responses to train any model of our own.
We share data only with the parties required to run the service: the upstream model providers (your prompt content, as described above), our payment processor (billing details), and our database and hosting infrastructure providers (account and usage records).
6. Retention and deletion
Account, billing and usage-metadata records are kept while your account is open and for as long as we need them for accounting, tax and dispute-resolution purposes. Because we do not store prompt or response content, there is no conversation history to delete — but you may request deletion of your account, API keys and associated metadata at any time by emailing us. We will action the request within 30 days, except where we are required to retain specific records by law.
7. Security
Traffic between you, our gateway and our upstream providers is encrypted in transit with TLS. API keys are stored as one-way hashes. Access to production data is restricted to the operator of the service. No system is perfect, but we do not hold the one thing that would make a breach of this service catastrophic for you: your prompt content.
8. Age requirement
Goalfinder is a developer tool and is not directed at children. You must be at least 18 years old, or the age of majority where you live, to create an account.
9. Changes to this policy
If we change how we handle your data — for example, by adding a model provider with different terms — we will update this page and revise the "last updated" date above. Continuing to use the service after a change means you accept the revised policy.
10. Contact
Questions about this policy, or want your account and data deleted? Email contact@goalfinder.space. Please write from the email address on your account so we can verify the request.