1. Information processed by FauxGuard
When you use the detector, FauxGuard receives the image you choose, technical request information such as the content type and size, and network information needed to route and protect the request. The server may see an IP address or the forwarding headers supplied by the hosting platform, the browser user agent, the requested route, the time of the request, and error information. The client also sends the selected file name as part of the multipart upload, although the browser-generated compressed file may use a new name.
Image metadata is part of the image file. Depending on the format and editing history, it may contain camera make and model, an editing software name, timestamps, orientation, provenance-related text, or other descriptive fields. FauxGuard reads available fields as unverified clues; it does not verify C2PA signatures or SynthID watermarks. You do not create a FauxGuard account. Waffo may request an email address and billing information during payment.
2. How information is used
FauxGuard uses the upload to inspect metadata, estimate AI-generation and face-manipulation model scores, and return a result. Technical request information is used to deliver the response, enforce purchased-check balances, apply shared request limits, prevent abuse, troubleshoot errors, and protect the service. Aggregate operational information may be used to understand reliability and capacity needs.
FauxGuard does not use the detector to train its own foundation model, build an advertising profile, or sell uploaded images. The service does not make automated decisions that directly produce legal effects. You decide what action, if any, to take from the result, and that action should include human judgment and other evidence.
3. Sightengine and other service providers
Metadata inspection can run inside the FauxGuard server without sending the image to a visual model. When a visual check is required, the processed image is transmitted to Sightengine so its generative and deepfake models can evaluate it. The request includes the image and the model selection. FauxGuard's API credentials are server environment variables and are not exposed in the browser.
Sightengine processes the image according to its own service terms and privacy practices. Hosting, network, and security providers may also process limited request data to deliver and protect the site. FauxGuard does not control every retention decision made by an independent provider, so do not upload content you are not authorized to disclose to a third-party detector.
4. Cookies and local storage
FauxGuard uses the essential fg_wallet cookie to connect your browser to a prepaid balance. It contains a random private recovery code, is httpOnly and SameSite=Lax, is Secure in production, and can last for up to one year. Only a hash of that code is used as the server-side balance identifier. The code can be displayed and downloaded in your browser so you can restore access on another device. Anyone with it can spend your checks, so keep it private. Deleting the cookie disconnects this browser but does not erase or increase the balance.
Essential service measurements count detector visits, checkout starts, confirmed payments, and completed or failed checks. Detector visits are estimated using a daily hash of a network address, rather than an advertising identifier. Counts can include bots and multiple people sharing a network and are not precise unique-person measurements. FauxGuard does not use advertising cookies, social pixels, or third-party analytics scripts. Waffo processes payment information on its own checkout and under its own privacy policy; FauxGuard does not receive full card numbers or security codes.
5. Retention and deletion
FauxGuard does not maintain a user account history or a gallery of uploaded images. The image is kept in request memory during detection and may be held by infrastructure or the upstream provider during processing. A result, including readable metadata clues, is cached on the server for up to ten minutes after completion so retrying an interrupted request does not require another paid analysis. Durable cleanup removes expired cached results. Minimal request identifiers and settlement states remain to prevent duplicate charges. Upload bytes are not saved in the billing ledger.
Server-side balance records, purchase references, payment and refund identifiers, and aggregate service measurements are retained to provide purchased checks, reconcile payments, and prevent duplicate fulfillment. Payment notifications may include a billing email and address; the FauxGuard ledger retains the order reference and balance changes rather than copying those details. Waffo maintains its own payment records. Contact hello@fauxguard.ai with an order reference for access or deletion questions. Records required for an unresolved balance, transaction, or legal obligation may need to be retained. Do not send a new copy of sensitive content or your recovery code in a support request.
6. Security, international processing, and changes
FauxGuard uses server-side credentials, HTTPS, private cookies, request-size limits, transactional balance reservations, signed payment callbacks, and shared capacity limits. No internet service is completely secure, and no method of transmission or storage can be guaranteed. You should not upload highly sensitive material unless you have determined that the processing is appropriate for your situation.
The service and its providers may process information in countries other than your own, subject to the provider's safeguards and applicable law. We may update this policy when the service, retention practices, or providers change. The date at the top shows the latest revision. Material changes should be reviewed before you continue using the detector.
7. Children and contact
FauxGuard is not directed to children under 13, and the service should not be used to upload a child's personal or sensitive images. If you believe a child has submitted personal information, contact us so we can review the request. Privacy questions can be sent to hello@fauxguard.ai. For the rules that apply to use of the detector, read the Terms of Service.
Privacy FAQ
Does FauxGuard store my uploaded images?
FauxGuard does not create a user account history or save uploads in its own database. The image exists in request memory for the current detection and may be sent to Sightengine when visual analysis is needed.
How is my purchased balance stored?
An essential httpOnly cookie holds a private recovery code. Its hash identifies your server-side balance. The balance is not stored in the cookie and clearing cookies does not reset it. Save your recovery code to restore access.
Does FauxGuard sell personal information?
No. FauxGuard does not sell personal information or use uploaded images to build advertising profiles. Processing is limited to operating, securing, and improving the detection service as described in the policy.
Can I request deletion of data?
Because FauxGuard does not maintain an account database or scan history, there is usually no stored image record to delete. You can contact the privacy address to ask about a specific request or an operational log.