Legal
Privacy Policy
What we collect, why we collect it, how long we keep it and who else sees it. Written to match what the code actually does.
Last updated 20 September 2026
1. Who we are
Truscan Inc. ("we", "us") operates the Truscan web search API at truscan.co and its subdomains. Our registered address is 111B S Governors Ave # 82225, Dover, DE 19904, United States. For anything in this policy, write to support@truscan.co.
We are the data controller for account and billing information. Where you use the API to process personal data of your own users, you are the controller and we act as your processor. The Data Processing Addendum covers that relationship.
2. What we collect
Information you give us when you create an account:
- Your email address and name.
- A password, which we store only as a bcrypt hash. We cannot read it or recover it.
- A profile picture, if you upload one.
- Billing details, handled by our payment processor. We store a customer reference and payment records, never full card numbers.
Information generated as you use the service:
- Request metadata for each API call: the method, path, response status, duration, the source that made the call, your IP address and user agent. We do not store request bodies.
- Nothing else about the call itself. The query you searched, the URLs you extracted, the question you asked and the results we returned are not written to any database. They pass through a cache so a repeated request is free, and that cache expires on its own within seven days.
- API key metadata: a name, a SHA-256 fingerprint and the last four characters. The key itself is shown once at creation and never stored in a form we can reverse.
- Webhook endpoints you configure and a record of each delivery attempt, including the response code and any error.
- Your credit balance and a ledger entry for every charge.
We do not sell personal data, and we do not use your queries or results to train models.
3. Why we are allowed to use it
| What we use | Why | Lawful basis (GDPR) |
|---|---|---|
| Email, name, password hash | To create and secure your account | Performance of a contract |
| Billing details and payment records | To take payment and meet tax obligations | Contract and legal obligation |
| Request logs | To show you your usage, bill accurately and debug faults you report | Contract and legitimate interests |
| IP address and user agent | To apply rate limits and detect abuse | Legitimate interests |
| Contact form submissions | To answer you | Legitimate interests |
Where we rely on legitimate interests, we have considered whether that interest is overridden by your rights, and you can object at any time using the contact details below.
4. How long we keep it
Retention is enforced automatically by a scheduled delete, not by anyone remembering to run a clean-up. The shortest retention period is the one that applies to what you actually send us, which is none: queries, URLs, questions and results are never written to a database at all.
| Data | Kept for | Where |
|---|---|---|
| Account record (email, name, password hash) | Until you delete the account | Primary database |
| Profile picture | Until you delete it or the account | Primary database |
| API key fingerprints and last four characters | Until the key is revoked or the account is deleted | Primary database |
| Request logs (method, path, status, duration, IP, user agent) | 30 days, then removed automatically | Primary database |
| Queries, URLs and questions you send, and the results we return | Not stored. Cached up to 7 days, then expires on its own | Cache only, never a database |
| Webhook endpoints and delivery records | Endpoints until deleted; deliveries 30 days | Primary database |
| Credit ledger and payment records | Retained while required for tax and accounting | Primary database |
| Password reset tokens | 1 hour, or until used | Primary database |
5. Deleting your account
You can delete your account from the dashboard. It requires your password, and it is not reversible.
When you delete an account, the following happens immediately:
- Your account record, profile picture, API keys and any pending password reset tokens are deleted.
- Your webhook endpoints and their delivery history are deleted.
- Your billing records are purged, except where we are required to keep invoice data for tax and accounting.
- Every API key you held stops working at once.
Request logs are not deleted at that moment. They hold no query text and no request bodies, and are removed automatically within 30 days of their creation whether or not the account still exists. If you need them removed sooner, write to us and we will do it by hand. There is no search history to delete, because none is kept.
7. International transfers
We are a United States company and our infrastructure and sub-processors may be located outside your country. Where personal data of individuals in the European Economic Area or the United Kingdom is transferred, we rely on the European Commission's Standard Contractual Clauses and equivalent UK provisions.
8. Your rights
Depending on where you live, you have some or all of the following rights. We do not charge for exercising them and we will respond within 30 days.
- Access: ask for a copy of the personal data we hold about you.
- Correction: have inaccurate data fixed. Your name, email and picture are editable in the dashboard.
- Deletion: delete your account, or ask us to remove data ahead of its automatic expiry.
- Portability: receive your data in a machine readable form.
- Objection and restriction: object to processing we base on legitimate interests.
- Withdraw consent: where we rely on consent, withdraw it at any time.
If you are in the European Economic Area or the United Kingdom, you may complain to your local supervisory authority. If you are in India, the Digital Personal Data Protection Act gives you comparable rights, including the right to nominate someone to exercise them on your behalf, and you may raise a grievance with us first at the address above. If you are a California resident, you have the rights to know, delete, correct and opt out of sale or sharing. We do not sell or share personal information as those terms are defined by the CCPA.
9. How we protect it
- Passwords are hashed with bcrypt at cost 12. They are never stored or logged in plain text.
- API keys and password reset tokens are stored as SHA-256 fingerprints. A stolen database does not yield a usable key.
- All traffic is served over TLS with HSTS enabled.
- Sessions expire after 24 hours. Password reset links expire after one hour or on first use.
- Internal service endpoints are unreachable from the internet and require a separate internal credential.
- Rate limits apply at the edge to slow credential stuffing and abuse.
- Request bodies are never written to logs.
No system is perfectly secure. If you find a vulnerability, report it to us using the contact page and please give us a chance to fix it before disclosing it publicly.
11. Children
The service is not directed at children and is not intended for anyone under 16. We do not knowingly collect data from children. If you believe a child has created an account, tell us and we will remove it.
12. Changes to this policy
We will update the date at the top when this policy changes. If a change materially affects how we handle your data, we will email account holders before it takes effect.
13. Contact
Write to support@truscan.co, or to Truscan Inc., 111B S Governors Ave # 82225, Dover, DE 19904, United States. A person reads it.