Legal
Privacy Policy
1. Who this policy covers
Signet ("we", "us") provides a fraud-scoring API at puresignet.com. This policy covers three groups:
- Customers: businesses and developers who hold a Signet account and API key.
- End users: the people whose email address, phone number or IP address a customer sends to us to be checked. They are our customers' users, not ours.
- Visitors: anyone browsing this website.
For end-user data, the customer decides why and how it is checked and is the data controller (in Indian law, the data fiduciary). We act on the customer's instructions as a processor. For customer account data and for the shared fraud signals described in section 4, we are the controller.
2. What we collect
From customers
- Name, work email, company name, intended use, expected monthly volume and any note you add, given when joining the waitlist.
- API keys and the names you give them, with when each was created and last used. Keys are stored only as one-way hashes; we cannot read them back.
- Sign-in links and dashboard sessions, stored only as one-way hashes. A link works once and expires; a session lasts up to 7 days or until you sign out.
- Credit balance and usage history.
- Emails you send us.
About end users, when a customer calls the API
| Data | What happens to it |
|---|---|
| The email address, phone number or IP address sent for checking | Processed in memory to produce a verdict. The full value is not written to our database. |
A masked copy, such as j***@company.com, +919***78 or 203.0.*.* | Stored in the customer's usage history. Deleted after 90 days. |
| A keyed one-way fingerprint (hash) of the value | Stored so the service can recognise the same value later. It cannot be turned back into the email, number or IP. |
| The verdict, risk score and signals for that check | Stored with the masked copy. Deleted after 90 days. |
| Details that describe the line or network, not the person: a phone number's country, line type and carrier; an IP address's network owner, network number, registration country and whether it is a VPN, proxy or Tor; how long ago an email's domain was registered; for live checks, whether a mailbox exists or a number is in service | Stored with the masked copy so the customer can see why a check was flagged. Deleted after 90 days. |
| A "fraud" or "legitimate" report a customer chooses to send | Stored against the fingerprint, linked to the reporting account. |
From visitors to this website
- Standard server logs kept by our hosting providers (IP address, browser type, pages requested).
- The site sets no advertising or analytics cookies. The playground keeps your API key in your browser's session storage, which is cleared when you close the tab. The customer dashboard keeps a sign-in session in your browser's local storage for up to 7 days, or until you sign out.
- The live demo on the home page and the bulk list tool run in your browser. Values you type there are checked on your own device. To see whether an email's domain can receive mail, your browser asks a public DNS service (Google or Cloudflare) about the domain name only.
3. How we use it
- To return a fraud verdict to the customer who asked for it.
- To bill credits and show usage history.
- To prevent abuse of the service (rate limiting, key security).
- To operate the shared fraud signals in section 4.
- To answer support requests and send service emails such as your API key.
We do not sell personal data, build advertising profiles, or send marketing to end users.
4. Shared fraud signals
Fraudsters reuse the same addresses, numbers and connections across many businesses. To catch that, Signet keeps, for each fingerprint, a count of how many customer accounts have checked it, how many of those checks looked risky, and how many accounts reported it as fraud or as legitimate.
- When any customer checks a value, the response includes those counts. That is the only thing shared.
- No customer can see another customer's identity, lists, or usage. Only counts are returned.
- The fingerprint is computed with a secret key held only in our database, so it cannot be matched against a list of known emails or numbers by anyone else.
- One account counts once per value. A single report moves a value towards "review"; it takes reports from several independent accounts to "block" it.
Our legal basis for this is the legitimate interest of our customers and of the people they serve in preventing fraud. If you believe a value belonging to you is being wrongly flagged, write to us (section 9) and we will review and remove the reports.
5. Who else processes data for us
| Provider | Purpose | What it receives |
|---|---|---|
| Supabase | Database and API hosting (Sydney, Australia region) | Everything in section 2 that we store |
| Vercel or Cloudflare | Website hosting and delivery | Website requests, including API requests passing through puresignet.com |
| Resend | Sending account emails | Customer name, email address and the message |
| Google Public DNS, Cloudflare DNS | Checking that an email domain can receive mail; looking up which network an IP belongs to | The domain name of an email; the IP address being checked |
| proxycheck.io | VPN, proxy and Tor detection | The IP address being checked |
| MillionVerifier | Confirming a mailbox exists. Only when the customer requests a live check. | The email address being checked |
| HLR Lookups | Confirming a phone number is in service. Only when the customer requests a live check. | The phone number being checked |
| Google Fonts | Typefaces on this website | Your browser's request for the font files |
These providers may process data outside your country, including in Australia, the United States and the European Union. We send them only what the stated purpose needs.
6. How long we keep it
- Masked usage history and verdicts: 90 days, then deleted automatically.
- Fingerprints and report counts: while they remain useful for fraud prevention, and removed on a valid request.
- Customer account details: for the life of the account, then deleted on request unless law requires us to keep records.
- Waitlist entries: until you have an account, or until you ask us to remove you.
- Sign-in links: deleted a day after they expire. Sessions: deleted when they end.
7. Security
- All traffic uses HTTPS. Data is encrypted at rest by our database provider.
- API keys are stored as hashes and shown once.
- The database cannot be read from a browser. Every table is closed to public access; only our server-side functions can reach it.
- Requests are rate limited, and administrative access is locked out after repeated wrong attempts.
No system is perfectly secure. If we learn of a breach affecting your data we will tell affected customers without undue delay.
8. Your rights
Depending on where you live (for example under India's Digital Personal Data Protection Act, the EU or UK GDPR, or California law), you may have the right to access, correct or delete your personal data, to object to or restrict its use, and to complain to a data protection authority.
- Customers and visitors: email us and we will act on your request.
- End users: the business that checked your details is the right first contact, because it decides how your data is used. You can also write to us directly. Because we hold only masked copies and fingerprints, we will ask you for the exact email address, phone number or IP so we can compute its fingerprint and find any record.
9. Contact
Email hello@puresignet.com with "Privacy" in the subject line. We aim to reply within 30 days.
10. Changes
If we change this policy in a way that matters, we will update the date above and email account holders. The data handling section of the documentation describes the same practices in technical terms.