Signet

Frequently asked questions

Can't find it? Email support@signetsentry.com. Looking for code? See the developer guide.

How accurate is it?

Signet recognises a returning browser by combining many device attributes with a per-browser token, and reports how it matched (match_type and match_confidence on every response). No browser fingerprint is perfect: the same person can look different after a browser update, and privacy tools (or two identical office laptops) can blur the line. That is why Signet gives you a score, a decision, and the reasons, rather than a verdict you have to trust blindly. Scoring is rules-based and transparent: you can see every rule and its points in How scores are calculated and tune thresholds per event with profiles. We don't publish accuracy percentages because they depend on your traffic. The best test is to run it on your own site in review mode first and compare its decisions with your outcomes (the dashboard and feedback endpoint make that easy).

What does Signet collect?

From the visitor's browser: device and browser attributes (user agent, screen, timezone, language, hardware hints, canvas/WebGL/audio rendering results, installed fonts, automation and tampering hints), a random per-browser token kept in local storage, the IP address and its network type (datacenter, VPN or Tor), and coarse behaviour counts and timing (for example how fast actions happen and whether there was pointer or keyboard activity). Signet never reads what is typed. From you, the merchant: your account email and, if you pass them, order amounts and an account id or email (emails are salted-hashed and never stored in clear). Details are in the privacy policy.

Is it private and compliant?

Signet is for fraud prevention and security only: no advertising, no cross-site tracking, and visitor ids are different for each customer, so nothing is shared between merchants. Data is deleted automatically after 90 days by default, and you can erase a device and everything linked to it with DELETE /v1/visitors/{id}. As the merchant you decide how to disclose the tag and, where your law requires it, get consent first (fraud prevention is often treated as a legitimate interest, but that depends on where your customers are). Our privacy policy and terms are plain-language templates, not legal advice: have your own counsel confirm what you need for your business.

How fast is it?

The tag loads asynchronously and does not block your page. It collects a profile in the background shortly after load, so by the time someone clicks Pay the session id is ready. The server-side call (POST /v1/assess) is a single request that, in our measurements from a laptop, typically returns in a few hundred milliseconds including network time (the first call after a quiet period can be slower, see below). Set a short client timeout (5 to 8 seconds) and decide what happens on a timeout; we recommend failing open and logging it (see Quotas, rate limits and errors).

Why was my first request slow? (free-tier cold start)

The service currently runs on a free hosting tier that puts it to sleep after a period with no traffic. The first request after a quiet spell can take up to a minute while it wakes; after that it is fast. If you can't tolerate that, keep it warm by calling /healthz every few minutes from your own monitoring, and always use a timeout with fail-open handling so a cold start never blocks a customer.

How do pricing and quotas work?

Free: 1,000 assessments a month. Starter: $29 a month for 25,000. Growth: $99 a month for 150,000. An assessment is one successful /v1/assess (or /v1/sessions/{id}) call. Collecting sessions with the tag, feedback, dashboard and account calls don't count. Quotas reset on the first of each month (UTC). If you reach your quota, calls return HTTP 429 quota_exceeded with the reset date, and nothing is charged for overage; upgrade any time at /pricing. Need more than 150,000 a month? Email us to ask about a custom quota.

How do I pay?

Paid plans are monthly memberships sold through Gumroad. Click Subscribe on the pricing page, pay on Gumroad, and your account upgrades automatically (it matches your Gumroad email, or the account id we pass along). Gumroad sends your receipt and handles card details; Signet never sees your card number.

How do I cancel?

Open the Gumroad receipt email for your subscription and use the manage/cancel link (or manage it from your Gumroad library). You keep your plan until the end of the period you paid for and then drop to the Free plan; nothing is deleted. If a payment fails, API calls return 402 subscription_inactive until the payment is fixed or you resubscribe. To close your account and erase your data, email us.

Can I try it without real traffic?

Yes. Signup gives you sandbox keys (pk_test_ / sk_test_) that use no quota and store nothing, with magic session ids for allow, review and deny. See Test mode. You can also check your own device live on the guide or the demo page.

How do I integrate it?

Add one script tag, put data-signet on your form, read the signet_session_id field on your server and call POST /v1/assess. The developer guide has copy-and-paste JavaScript, C#, curl and Node/Express examples, and there is a sample ASP.NET project.

Will it block real customers?

Only if you tell it to. Signet returns a decision; you choose the action. We suggest using review to add friction (2FA, a captcha, a manual look) rather than blocking outright, starting in observe-only mode (log the decision, don't act) and tightening once you trust it. Use feedback to mark good customers legit so their devices earn trust, and use profiles to make high-risk events stricter than low-risk ones.

Who is behind Signet and how do I get support?

Signet is a product of Main Street Playbooks. For support, billing questions, data requests or a lost key, email support@signetsentry.com.