1. Who this policy covers
This policy explains how Stopnetic handles personal information when you visit our website, create an account, contact us or use our website access-control service.
Stopnetic is responsible for its own account administration, billing, support and service security. When a website owner installs Stopnetic, that owner decides which routes and visitors to check. For that visitor information, the owner normally acts as the controller and Stopnetic processes information on its instructions. The website owner’s privacy notice also applies. A data processing agreement, where required, is separate from this policy.
2. Information we process
- Account information: your email address, a salted password hash, account status, authentication and recovery records, and sessions. If you choose Google sign-in, we receive your Google account identifier and verified email. This sign-in requests identity and email access, not access to your Gmail messages.
- Your websites: domains, origin URLs, ownership verification, access rules, integration settings, installation credential records and subscription status.
- Private previews: the enabled status, protected scope, selected paths, configuration revision and a salted preview-password hash. The password is processed when an owner sets it and when a visitor submits it through the website’s server for validation. We store the hash rather than a recoverable password. Raw preview passwords and hashes are not included in access-event evidence. A newly typed password can remain in the owner’s open form after saving so it can be revealed or copied; refreshing clears those fields without disabling the saved password.
- Security checks: site and request references, request path and method, timestamps, allow/challenge/block outcomes, verification results and limited browser or device signals. Optional features can report country, device category, browser consistency information and rotating network or connection groups. Paths may contain information chosen by the website, so owners should avoid including personal data in them.
- Interactive checks and usage limits: the selected verification mode, short-lived challenge and confirmation records, completion status, network-based usage counters, declared request costs and budget outcomes. The optional checkbox flow records completion, not human identity. Data and action budgets use cost metadata supplied by the website’s server; the budget check does not require the protected response contents.
- Support: the name, email, subject and message you submit, and related correspondence. Please leave out passwords, payment details and installation secrets.
- Payments: subscription, customer, checkout and payment-status references. Stripe handles payment details when you use Stripe checkout; Stopnetic does not collect full card numbers through its own forms.
- Infrastructure records: hosting, email and security providers may process IP addresses and request or delivery logs to operate and protect the service. A hashed or rotating identifier may still be personal data; we do not treat it as automatically anonymous.
3. Why we use information
We use information to provide accounts and access decisions, verify website control, deliver account messages, administer subscriptions, answer requests, prevent fraud and repeated trial abuse, investigate errors and protect the service.
Where the GDPR or a similar law applies, the relevant grounds are performance of our agreement with you, legitimate interests in operating and securing the service, and legal obligations such as accounting. If a feature requires consent, we seek it separately; you can withdraw it without affecting earlier lawful processing. Customers must establish their own lawful basis for visitor checks.
Required account and integration information is necessary to provide the corresponding service. You can browse these legal pages without an account.
6. Retention and deletion
Account, site and policy records are kept while needed to provide the service. Security and support records are kept according to their operational purpose, fraud-prevention needs, dispute requirements and applicable law. Expiring challenges, sessions and rate-limit records stop authorizing actions at expiry; physical cleanup may happen later.
A saved preview-password hash is retained while preview protection is enabled, replaced when a new password is saved, and removed from the application’s active password record when protection is disabled or the owning account is deleted. Saving preview settings revokes existing unlocks; it does not recall content already downloaded. Backup retention is separate from removal of an active record.
Detailed traffic logs have monthly recording allowances and plan history windows of up to 30, 90 or 180 days. Once the recording allowance is used, accepted reports can still contribute to compact totals without a new detailed record. Scheduled and activity-triggered maintenance removes expired details in batches after preserving summaries; deletion is not instantaneous and depends on the worker running successfully. Backups have separate retention.
Compact hourly traffic summaries are kept for up to 365 days, and account/site daily usage and monthly recording counters for up to 400 days, subject to batched cleanup. These contain counts and broad categories rather than a copy of every request path or browser signal. Short-lived report deduplication records expire separately and are cleared by maintenance. Usage tracking counts service work and is not a unique-visitor measurement.
Purchased-event balances, lifetime credit totals and purchase records are kept while the account exists to preserve unused credits, confirm payments and process adjustments. Monthly credit-use counters follow the batched usage-counter retention above. Purchase records include pack, amount, status and payment-provider references; Stopnetic does not store payment card details. Account deletion removes these application records. Independent payment-provider, legal, support and backup records may have separate retention.
You can request account deletion through Account security or contact us. Completed account deletion removes the account and its owned site and event records from the application database. Limited hashed domain trial-use records remain to prevent repeated free trials. Payment providers may retain historical invoices, and independent support, security, legal or backup records may remain where needed. Contact us about a specific record or retention period.
7. Automated access decisions
Stopnetic evaluates website rules automatically. A website can allow access, require automatic or interactive browser verification, require a shared preview password, or deny access based on its rules and configured security controls. Country controls, request limits, data or action budgets and temporary network pauses can restrict access. Network allowances are shared across a rule rather than allocated to an identified person; new cookies or verified sessions do not reset them. People sharing a network can affect each other’s access.
A successful browser check does not prove someone is human, and a denial does not establish that someone is an AI agent. If you believe a website incorrectly blocked you, contact that website’s owner for review. Contact Stopnetic if the issue concerns our own service.
8. Your privacy choices and rights
Depending on the law that applies, you may request access, correction, deletion, restriction or portability of your information, object to processing based on legitimate interests, or withdraw consent. You may also complain to your local data protection authority. We may need to verify your identity before acting on a request.
Email stopnetic@gmail.com or use our contact form. If your request concerns a customer’s website, contact its owner first so the request can be handled under that website’s instructions and obligations.
The service is intended for website owners and authorized administrators, not for children to create accounts. If you believe a child has provided account information, contact us.
9. Security and policy updates
We use safeguards including access controls, hashed passwords and credentials, signed integration decisions and protected sessions. No system can guarantee absolute security. Keep credentials private and report suspected exposure promptly.
We update this policy as the service changes and show the revision date above. Where required, we will provide additional notice of material changes. See also our Terms and Conditions.
