Privacy Policy

Optional intake quiz

Your quiz answers and pasted links are held in this browser tab while you answer. When you request an emailed plan, we save your email address, selected answer categories, link and website counts, follow-up preference, and a random journey identifier. The quiz lead record does not contain your pasted content links, images, or identity documents. We use it to deliver your plan, help with your next step, and understand where the intake process needs improvement. These quiz records expire after 90 days. If you buy a service or contact support, the resulting case, billing, and support records follow their own retention rules.

We send one plan email and only send the quiz follow-up if you select its optional checkbox. You can unsubscribe through either email. Email delivery is handled by our email provider. A return link contains your selected answer categories and a random identifier, but no email address or pasted content links. Treat it as private; opening it in another browser will not restore your pasted links.

1. Governing Law — The Illinois Biometric Information Privacy Act (BIPA)

IntimaShield, LLC operates out of Illinois and is strictly governed by the Biometric Information Privacy Act (740 ILCS 14), the most comprehensive biometric privacy law in the United States. BIPA carries statutory penalties of $1,000 per negligent violation and $5,000 per intentional violation — with a private right of action allowing individuals to sue directly.

We view this legislation not as a limitation, but as our foundational security guarantee to you. Because the legal and financial penalties for mishandling biometric data under BIPA are severe, our entire technical architecture is designed to strictly limit any storage of your facial geometry to documented, consent-gated purposes with a published retention and deletion schedule (see our Biometric Policy).

IntimaShield is a cybersecurity and legal takedown firm. We are not a social media platform, a reverse-image search engine, or an advertising company. We have zero financial incentive to retain your data.

2. How We Process Your Likeness

IntimaShield employs a minimal-retention architecture designed to protect your privacy at every step. Here is exactly what happens, stage by stage:

• Free scan (before any payment): The free scan is text-based. We search the name and handles you provide across search providers to locate pages that reference you. You do not upload a photo, and no facial recognition or biometric processing of any kind takes place before payment.
• Identity verification (paid customers): Your identity is verified by Stripe Identity, which collects your government ID and a live selfie on Stripe's own infrastructure. After verification, we retrieve the verified selfie and use AWS Rekognition facial comparison to confirm that the person who verified is the person depicted in the content on the case. This comparison runs transiently in server memory; the selfie is not written to our databases.
• Match confirmation (Shield monitoring and active cases): With your separate written biometric consent, a facial geometry template is enrolled in an isolated AWS Rekognition collection and used to confirm whether newly found content actually depicts you before we act on it. Retention of this template is governed by our Biometric Policy: it exists only for the active life of your case or subscription and is deleted when the case closes or the subscription ends. It is not destroyed mid-service, because ongoing match confirmation is the service you enrolled it for.
• Content checks: When we evaluate whether an image at a suspect URL depicts you, the comparison is transient. We never store intimate images, and content URLs are probed with header-only (HEAD) requests wherever possible so the content itself is never downloaded to our systems.

Third-Party Biometric Processors: IntimaShield uses two third-party biometric processors: Stripe Identity (liveness and document verification) and Amazon Web Services Rekognition (facial comparison and consent-gated match confirmation). All data in transit is encrypted with TLS, all data at rest is encrypted with AES-256, and sensitive fields such as your verified legal name are additionally encrypted at the application layer with AES-256-GCM.

3. Data Retention and Deletion Schedule

We do not maintain a honeypot of biometric data.

• Free Scans: Your scan results are held in a temporary cache for up to 1 hour to allow you time to review the threat assessment and decide if you want to activate protection. After 60 minutes, all session data is permanently and irreversibly destroyed. The free scan is text-based, so there is no uploaded image to retain in the first place.
• Active Subscribers (24/7 Shield): If you activate the monitoring shield, we retain your monitoring search terms (the name and handles you ask us to watch) solely for the purpose of running continuous automated monitoring scans. Facial enrollment for match confirmation, where you opt in, is governed by our Biometric Policy. You can permanently delete your monitoring data at any time from your dashboard.
• Abandoned Sessions: If you begin a paid signup but do not complete it within 24 hours, the session data associated with it (including any encrypted scan payload) is automatically hard-deleted. No manual intervention is required.

4. Zero Third-Party Monetization

IntimaShield will never sell, lease, trade, or otherwise profit from your biometric data. We will never use your facial geometry to train AI models, build advertising profiles, or enrich third-party datasets.

Our revenue is generated exclusively through our takedown services and monitoring subscriptions — never by monetizing our users. This is not merely a policy choice; it is a legal requirement under BIPA (740 ILCS 14/15(c)).

5. Our Promise

IntimaShield is built on a minimal-retention, privacy-first architecture. We never store your intimate images on our servers. Content is checked without downloading it to disk, facial comparisons run transiently in memory, and the only retained biometric artifact is the consent-gated facial template described in our Biometric Policy, which you can delete at any time.

We built IntimaShield this way because we believe that protecting your privacy should never require surrendering it. You deserve safety without compromise.

6. What We Collect

We collect the minimum information needed to provide our service:

• Email address: Used for magic link authentication, account notifications, and match alerts.
• Verified legal name and authorization record (paid customers): To file removal notices as your authorized agent we record your verified legal name (encrypted at the application layer with AES-256-GCM and never transmitted to platforms) and your signed Letter of Authorization. The signature record includes your typed name, a timestamp, and the IP address of the signing device, retained as legal evidence that you authorized us to act. IP addresses are recorded only at these signature and sworn attestation moments; we do not use them for tracking. When your ID check completes we compare the name on your ID with the name you signed with. We keep the result of that comparison and a keyed, one-way fingerprint of the ID name, so a later signature can be checked against it. The fingerprint is not readable as a name. It can only be used to test whether a name typed later matches.
• Monitoring search terms (Shield): The name and handle variants you ask us to watch.
• Scan results: URLs and metadata about where matches were found. These results do not contain your images.
• Payment information: Processed securely by Stripe. We never see or store your full card number.

7. What We DON'T Collect or Retain

We want to be completely transparent about the data we do not collect or store:

• Intimate images: We never download, store, or view the content we work to remove. Content URLs are probed with header-only requests; the images and videos themselves never touch our systems.
• Uploaded photos: The free scan takes no photo upload. For paid identity verification, your ID document and selfie are collected and held by Stripe Identity on Stripe's infrastructure, not ours.
• Biometric templates without consent: No facial geometry template is ever created without your separate written biometric consent. Where you consent, the template lives in an isolated AWS Rekognition collection under the retention schedule in our Biometric Policy, never on IntimaShield's own servers.
• Cross-site browsing history: We do not track what you do elsewhere on the web.
• Device fingerprints: We do not create or store device fingerprints for tracking purposes.

8. How Our Free Scan Actually Works

When you run a free scan, here is exactly what happens:

• You provide the name and handles you want checked, plus an email address for your results. No photo is requested or accepted.
• Our server sends text search queries built from those names and handles to our search providers.
• The raw results are filtered against our directory of known leak sites, tube sites, and pirate platforms, then categorized into a threat assessment.
• Only the scan results (matched URLs and threat data) are shown to you, and they are destroyed from our cache after 1 hour.

Biometric processing happens only after payment, during identity verification, as described in Section 2. Verification imagery is processed transiently and is subject to automated deletion; any enrolled facial template is governed by the retention schedule in our Biometric Policy. All stored scan evidence is encrypted at rest.

9. Third-Party Services

We use a small number of trusted third-party services to operate IntimaShield:

• Serper and SerpAPI: Text-based search providers. They receive search keywords (names, aliases, handles) to locate unauthorized content across forums, file hosts, and tube sites. No biometric data and no images are ever transmitted to either provider.
• Amazon Web Services (Rekognition): Performs the facial comparison used in identity verification and, with your consent, holds the enrolled facial template used for match confirmation in an isolated collection. Retention and deletion are governed by our Biometric Policy.
• Stripe: Handles all payment processing and identity verification. Stripe Identity collects your government ID and live selfie on Stripe's infrastructure. We never receive or store your full payment card details. See the Stripe Privacy Policy.
• Supabase: Provides our database and authentication infrastructure. Your email and scan metadata are stored in Supabase with Row Level Security enabled. See the Supabase Privacy Policy.
• Resend: Transactional email delivery service. Receives recipient email addresses for sending takedown notices, portal links, and case updates. No biometric or OSINT data is transmitted to Resend.
• Google Ads: We use Google's advertising tag to measure whether our ads lead to signups and to build remarketing audiences. Google may set advertising cookies in your browser (see Section 13). No scan results, case data, or biometric data are shared with Google.
• Railway: Application server hosting (railway.app). Our backend API runs on Railway infrastructure. No biometric data is stored on application servers; all data is processed in-memory and transmitted to the secure storage and verification services described above. Railway does not have access to decrypted user data.
• Vercel: Frontend hosting and content delivery (vercel.com). Serves our static website files. Vercel does not process, store, or have access to any biometric data, scan results, or personal information beyond standard web server access logs.

All third-party processors listed above are bound by their published data processing terms, and we do not sell, share, or provide your data to any other third parties for marketing or advertising purposes. With the sole exception of Stripe Identity, which must process your identity documents and selfie together in order to verify you, no third-party scan or search service receives both your identity (name or email) and your image — those data points are kept separate across services.

10. Data Storage & Security

We take the security of your data seriously. Our measures include:

• Row Level Security (RLS): Database policies ensure that you can only access your own data. No other user can view your records, and access by IntimaShield staff is limited to what is needed to work your case. Staff never view intimate images — our systems do not download or store them.
• Encrypted at rest: All data stored in our database is encrypted using AES-256 encryption, and your verified legal name carries an additional application-layer AES-256-GCM encryption.
• Encrypted in transit: All communication between your browser and our servers uses TLS encryption.

11. Your Rights

Depending on where you live, you may have specific rights regarding your personal data:

• GDPR (European Union): You have the right to access, correct, delete, and export your personal data. You may also object to or restrict processing. To exercise these rights, contact us at help@intimashield.com.
• CCPA (California): You have the right to know what personal information we collect, to request deletion, and to opt out of the sale of your data. We do not sell your data. To exercise your rights, contact us at help@intimashield.com.
• All users: Regardless of your location, you can request a copy of your data or ask us to delete your account at any time.

12. Data Retention

You are in control of your data. You can delete your account and all associated data at any time through the Settings tab in your dashboard. Deletion is instant and irreversible — once you delete your data, it is gone permanently from our systems.

If you delete your account, all stored search terms and monitoring configurations will be removed. We will no longer be able to monitor for or take down matches on your behalf.

13. Cookies

IntimaShield keeps cookies to a minimum.

• Authentication: A session credential keeps you logged in. It expires when you log out or after a period of inactivity.
• Google Ads measurement: Our site loads Google's advertising tag (gtag.js) to measure ad conversions and support remarketing. Google may set advertising cookies in your browser as part of this. See Google's advertising policies for details.
• Nothing else: We do not run any other analytics, session-replay, or third-party tracking tools.

14. Changes to This Policy

We may update this Privacy Policy from time to time. When we make significant changes, we will notify you via email at least 30 days before the changes take effect. Minor clarifications or formatting changes may be made without notice.

The "Last updated" date at the top of this page will always reflect the most recent revision.

15. Contact

If you have any questions about this Privacy Policy or how we handle your data, please do not hesitate to reach out. We are here to help and want you to feel safe.

Email: help@intimashield.com
Phone: (773) 234-4448