Privacy Policy
How NSFW Check handles account records, image URLs sent for detection, the browser trial, payments via service providers, key protection and account deletion.
Last updated: 2026-10-25
Account and service records
NSFW Check uses Google sign-in. Account records include the name, email address, and profile image supplied through Google, together with profile changes you make in the service. Session cookies support sign-in; preference cookies support features such as language selection.
The service processes records needed for your account:
- API Key names, prefixes, authentication digests, encrypted complete Keys, and access or copy audit records.
- Image URLs, task status and timestamps, the selected policy, model version, classification probabilities, results, and failure reasons.
- Orders, subscription periods, payment references, credit grants, deductions, credit returns, and related ledger records.
- Messages and attachments submitted through the existing support tickets.
- Registration and security information, such as IP address, region, language, and referral information.
These records support authentication, detection, billing, history, support, security checks, and recovery from interrupted processing.
Commercial detection and image URLs
The commercial API accepts a public HTTPS image URL. The inference service downloads the content available at that URL when it executes the task. It does not keep a submission-time image snapshot, and the platform does not host detection originals. Keep the URL accessible during waiting, execution, and retries.
Task records, results, and encrypted image URLs are retained for the account's lifetime. They are not automatically removed when processing finishes or a link expires. Orders and credit history are also retained during the account's lifetime. A signed URL can contain access tokens; its expiry does not remove the saved encrypted URL record.
The account owner can view and copy the submitted URL. Services and authorized staff access data according to their responsibilities. Logs and public errors must not disclose complete Keys, signed image URLs, or service credentials. Customer detection images are not used to train models in this release.
Browser trial
The WASM trial performs inference in your browser. It does not create a commercial API task or consume account credits. Selecting an external image URL causes your browser to request the image directly from its source; if the source does not allow cross-origin access, this site's server requests it instead and passes it to your browser without storing it. Local inference therefore does not mean there is no network request: the source receives the URL request and the network information normally associated with it.
The browser trial and commercial API can differ in model or input processing. A trial result does not mean a commercial task has been accepted or saved.
Service providers and payments
Google supports sign-in and hosted inference. Cloudflare processes website and API traffic and task delivery. Supabase PostgreSQL stores account and business records. Waffo hosts checkout and processes payments; the platform keeps the order and payment references needed to confirm purchases and credit delivery.
The inference service receives the submitted image URL to perform detection. The image source receives download requests. Waffo payment processing and Google sign-in also involve their respective services and notices.
Key protection
Complete product Keys and saved image URLs use authenticated encryption with versioned keys. Key lists show names and prefixes. An explicit owner-only action provides the complete Key again and records access. Revoking a Key prevents future submission and query authentication with it; already accepted tasks continue.
Encryption, ownership checks, and separate access to encryption keys are protection measures, not a guarantee that disclosure is impossible. Use the existing support tickets or email support@nsfwcheckapi.com if you suspect unauthorized access.
Account deletion and questions
This release has no self-service account deletion or data export feature. Use the existing support tickets or email support@nsfwcheckapi.com for account or data questions. An administrator handles deletion after external renewal has stopped and outstanding tasks, credit returns, payments, and financial exceptions have been settled.
After those prerequisites, the platform deletes the account's tasks, results, URLs, orders, payment records and credentials, credit records, and API Keys. Shared redemption codes and other accounts' history are preserved. No extra identity marker is retained to prevent rewards being claimed after deletion and re-registration.
Deletion of online records does not mean every controlled backup copy disappears at the same instant. Backup retention and deletion propagation follow the operating arrangements disclosed for the service; this page specifies no retention period or immediate deletion guarantee for all copies.
Detection output is a technical assessment under the selected policy, not a legal determination. Detection and privacy questions use the same support tickets or email support@nsfwcheckapi.com; there is no separate content complaint portal.