Privacy Policy
Last updated: August 3, 2026 · Version 2.2
1. Data Controller and Contact Details
The data controller responsible for your personal data is:
Sanmarcsoft LLC
5900 Balcones Dr, Ste 100
Austin, TX, United States
Data Protection Contact: [email protected]
Website: verifieddit.com
Sanmarcsoft LLC is registered in Texas, United States, and Verifieddit is run from Vienna, Austria. Because the service is run from Vienna, the GDPR applies to it directly, and the Austrian Datenschutzbehörde is its supervisory authority.
Sanmarcsoft LLC acts as the data controller for all personal data processed through the Verifieddit platform. For any questions regarding the processing of your personal data, you may contact us at [email protected].
2. What Personal Data We Collect
2.1 C2PA Verification (Free Tier) – No Data Collected
Our core C2PA content credential verification is performed 100% client-sidein your web browser. When you use this feature:
- Your media files are never uploadedto any server
- All C2PA signature validation, metadata extraction, and provenance analysis occurs locally in your browser using WebAssembly
- No file content, metadata, or analysis results are transmitted to our servers
- When you close the browser tab, all data is discarded
- To check whether a signer's certificate has been revoked, your browser downloads our complete revocation list from revocation.verifieddit.com. The request carries nothing about you or your file, so we cannot tell which certificate you checked
- When you check a signed file, the live revocation check (on by default; you can switch it off above the drop zone) has your browser send the signing certificates of the file you are checking, and nothing else, to api.verifieddit.com, which asks the certificate's issuer and returns the answer. The file itself is never sent, and we keep no record of the request
This is privacy by design: the check itself never needs your file. The optional features listed below send data only after you choose them, each time.
2.2 Account Information (When You Register)
If you create a Verifieddit account through our authentication provider (Clerk), we collect:
- Email address– for account identification and communication
- Display name– for personalization of your dashboard
- OAuth profile data– if you sign in via GitHub, Google, or Apple (profile name, email, avatar URL as provided by the OAuth provider)
- Account role and subscription tier– to determine feature access (Free, Pro, Enterprise)
2.3 AI Detection Data (Logged-In Users Only)
If you opt in to AI content detection, the following processing occurs:
- Image data– sent to our analysis server, hosted by Hetzner Online GmbH in Germany, for server-side pixel analysis
- SHA-256 hash of the image– used as a cache key to avoid redundant analysis
- Analysis results– cached for 30 days, associated with the image hash
Important:AI detection requires your explicit consent before any image data leaves your browser. You are prompted each time and may decline. Images are not stored permanently– only the SHA-256 hash and analysis results are retained in cache for 30 days, after which they are automatically purged.
2.4 Billing Information
If you subscribe to a paid plan (Pro or Enterprise), payment processing is handled entirely by Stripe. We do notstore credit card numbers, bank account details, or other payment instrument data on our servers. We receive from Stripe only:
- Subscription status (active, cancelled, past due)
- Plan type and billing period
- Stripe customer ID (an opaque identifier)
2.5 Verification Records
For logged-in users who generate verification badges or certificates, we store:
- File hash(SHA-256 digest – not the file itself)
- Original filename
- C2PA verification status(verified, unverified, tampered)
- Timestampof verification
- Badge metadata(badge ID, short URL, creation date)
These records are tied to your user account and are used to power your verification dashboard.
2.6 Badge Scan Tracking
When someone scans or views a verification badge you created, we log:
- Country(derived from Cloudflare request headers, not precise geolocation)
- Timestampof the scan
- Referrer URL(the page where the badge was embedded)
No personally identifiable information (PII) of the person scanning the badge is collected or stored. IP addresses are not logged for badge scans.
2.7 Cloudflare Web Analytics
We use Cloudflare Web Analytics for aggregate site usage metrics. This service is:
- Cookie-free– no cookies of any kind are placed on your device
- Privacy-respecting– no personally identifiable information is collected
- Cookie-free: it stores nothing on your device
2.8 Referral Source and Self-Reported Role (This Website Only)
When you arrive at this website by clicking a link from one of our other products – for example the Verifieddit browser extension – the link may carry a referral sourcein the web address (a srcparameter such as ?src=extension-panel). It records which of our surfaces sent you here. It contains no identifier for you, your device, or your browsing history, and it is visible to you in the address bar.
We may also ask you, on this website, an optional question about your role(for example journalist, newsroom, developer, or enterprise) so we can point you at the right documentation and pricing. Answering is entirely voluntary, the question is skippable, and skipping it never restricts access to any verification feature.
To be unambiguous about the browser extension: the extension collects nothing about you, reports nothing, and keeps no history of what you inspected. It performs all verification locally on your device, as described in section 2.1. The referral source exists only in a link that you choose to click, and the role question is asked only after you have arrived on this website. Neither is a measurement of anything you did inside the extension. The one case in which the extension sends anything at all is the optional durable-credential check described in section 2.9, which is switched off unless you turn it on.
2.9 Durable Credential Check (Browser Extension, Off by Default)
Some Content Credentials declare a durable binding: an invisible watermark that allows the credential to be recovered even if the file's metadata is stripped by a re-encode or a screenshot. The extension can confirm whether such a credential is genuinely registered and recoverable by asking our manifest store at manifests.sanmarcsoft.com.
This check is off unless you switch it on.It is the only request the extension makes that you do not start with a click, which is why it is a choice rather than a default. You can turn it on from the "Cloud-recoverable" panel shown when you inspect a file, or from the extension's Options tab, and turn it off again in the same places.
When it is on, and only for images whose credential declares a durable binding, the request carries aperceptual fingerprintof the image: two short hashes (pHash and dHash) computed on your device. It does notcarry the image itself, any part of it, the page you found it on, or any identifier for you, your device, or your session. The request is sent without cookies. We use it solely to answer whether a credential is registered for that fingerprint, and we do not use it to build a profile or to track you across sites.
Turning the check on applies from that moment forward. It does not re-examine anything you have already looked at, so enabling it never sends a fingerprint for a file you inspected earlier. With the check off, such files still verify normally; their durable binding is simply reported as declaredrather than confirmed.
2.10 Other Credential Registries (Only When You Ask)
When a file you verify carries no Content Credentials, we offer to ask other public credential registries whether they hold a credential for it. Nothing is sent until you press the button, and the panel names each registry before you do. If you agree, the file is sent through our verification service to those registries (at the time of writing Trufo, aiwatermark.com, DeepMark for audio, and Monolith), which are independent companies and process it under their own policies. We do not keep the file. If you do not press the button, the file is not sent to them.
3. Lawful Bases for Processing
Under Article 6 of the GDPR, we process your personal data on the following lawful bases:
| Processing Activity | Lawful Basis | GDPR Article |
|---|---|---|
| Account creation and management | Contract performance | Art. 6(1)(b) |
| AI detection image analysis | Explicit consent | Art. 6(1)(a) |
| Payment processing (Stripe) | Contract performance | Art. 6(1)(b) |
| Badge tracking and scan analytics | Legitimate interest | Art. 6(1)(f) |
| Verification records | Contract performance | Art. 6(1)(b) |
| Server and security logs | Legitimate interest | Art. 6(1)(f) |
| Cloudflare Web Analytics | Legitimate interest | Art. 6(1)(f) |
Where we rely on legitimate interest, we have conducted a balancing test to ensure our interests do not override your fundamental rights and freedoms. Our legitimate interests include maintaining the security of our platform, preventing abuse, and providing aggregated usage analytics to improve the service.
4. How We Process Your Data
We process personal data for the following purposes:
- Providing the Service:Authenticating users, managing subscriptions, generating verification badges and certificates, and delivering AI detection results.
- Security and Abuse Prevention:Monitoring for unauthorized access, DDoS attacks, and misuse of the platform through server logs and Cloudflare security features.
- Service Improvement:Using aggregated, non-identifiable analytics from Cloudflare Web Analytics to understand traffic patterns and optimize performance.
- Communication:Sending essential service notifications (account changes, security alerts, billing updates). We do not send unsolicited marketing emails.
- Legal Compliance:Retaining data as required to comply with applicable laws, respond to legal requests, and protect our legal rights.
5. Data Retention Periods
| Data Category | Retention Period | Deletion Method |
|---|---|---|
| C2PA verification data | Not retained (client-side only) | Discarded when browser tab closes |
| AI detection cache | 30 days | Automatic purge |
| Account data (Clerk) | Until account deletion | Deleted upon request |
| Verification records | Until account deletion | Deleted upon request |
| Billing data (Stripe) | As required by law (typically 7 years for tax records) | Managed by Stripe per their retention policy |
| Badge scan logs | Until account deletion | Deleted upon request |
| Server/security logs | 30 days | Automatic rotation and deletion |
6. Third-Party Data Processors
We engage the following third-party processors to deliver our services. Each processor is bound by a Data Processing Agreement (DPA) that requires GDPR-compliant data handling:
| Processor | Purpose | Data Location | Transfer Safeguard |
|---|---|---|---|
| Clerk | User authentication, account management, session handling | United States | Standard Contractual Clauses (SCCs) |
| Stripe | Payment processing, subscription management, invoicing | United States / EU | Standard Contractual Clauses (SCCs) |
| Cloudflare | CDN, DNS, DDoS protection, Workers (API endpoints), Web Analytics | Global edge network | Standard Contractual Clauses (SCCs) |
| Hetzner Online GmbH | Application hosting, AI detection processing, data storage | EU (Nuremberg and Falkenstein, Germany) | No transfer outside the EU |
7. International Data Transfers
Verifieddit is run from Vienna, Austria. Our application servers are hosted by Hetzner Online GmbH in data centres in Nuremberg and Falkenstein, Germany. Some of the processors listed above operate outside the EU; those transfers are described below.
Certain third-party processors operate in the United States:
- Clerk(authentication) – US-based. Data transfers are protected by EU Standard Contractual Clauses (SCCs) as adopted by the European Commission under Decision 2021/914.
- Stripe(payments) – US-based with EU data processing capabilities. Data transfers are protected by SCCs and Stripe's binding corporate rules.
- Cloudflare– Global edge network with US headquarters. Data transfers are protected by SCCs and Cloudflare participates in the EU-US Data Privacy Framework.
We regularly review the data transfer mechanisms of our processors to ensure ongoing compliance with GDPR Chapter V requirements. If a processor's transfer safeguards are invalidated, we will implement supplementary measures or transition to an EU-based alternative.
8. Your Rights Under GDPR
If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, you have the following rights under the GDPR and equivalent legislation:
- Right of Access (Art. 15):You have the right to request a copy of the personal data we hold about you, along with information about how it is processed.
- Right to Rectification (Art. 16):You have the right to request correction of inaccurate personal data or completion of incomplete data.
- Right to Erasure (Art. 17):You have the right to request deletion of your personal data when it is no longer necessary for the purposes for which it was collected, when you withdraw consent, or when there is no other legal ground for processing.
- Right to Restriction (Art. 18):You have the right to request restriction of processing of your personal data in certain circumstances, such as when you contest the accuracy of the data or object to processing based on legitimate interest.
- Right to Data Portability (Art. 20):You have the right to receive your personal data in a structured, commonly used, machine-readable format and to transmit it to another controller.
- Right to Object (Art. 21):You have the right to object to processing of your personal data based on legitimate interest. We will cease processing unless we demonstrate compelling legitimate grounds that override your interests.
- Right to Withdraw Consent (Art. 7(3)):Where processing is based on consent (e.g., AI detection), you may withdraw consent at any time. Withdrawal does not affect the lawfulness of processing performed before withdrawal.
- Right Not to Be Subject to Automated Decision-Making (Art. 22):You have the right not to be subject to decisions based solely on automated processing that produce legal or similarly significant effects. Our AI detection feature provides informational results only and does not make automated decisions affecting your rights.
9. How to Exercise Your Rights
To exercise any of the rights described above, contact our privacy team at:
Email: [email protected]
Subject line:"GDPR Data Subject Request – [Your Request Type]"
We will respond to your request within 30 daysof receipt, as required by Article 12 of the GDPR. If the request is complex or we receive a large number of requests, we may extend the response period by an additional 60 days, in which case we will notify you of the extension and the reasons within the initial 30-day period.
We may ask you to verify your identity before processing your request to ensure we do not disclose personal data to unauthorized persons.
All data subject requests are handled free of charge. If requests are manifestly unfounded or excessive (particularly if repetitive), we reserve the right to charge a reasonable fee or refuse to act on the request, as permitted by Article 12(5) of the GDPR.
10. Cookies and Tracking
Verifieddit is designed to be cookie-freefor anonymous users. We do not use:
- Advertising cookies
- Third-party tracking cookies
- Analytics cookies (Cloudflare Web Analytics is cookie-free)
- Social media tracking pixels (no Facebook Pixel, no Google Analytics)
The only cookies set on your device are:
| Cookie | Purpose | Set By | Type |
|---|---|---|---|
| __session | Maintains authenticated session state | Clerk | Strictly necessary (only when signed in) |
| __cf_bm | Cloudflare bot management | Cloudflare | Strictly necessary (security) |
These are strictly necessary cookiesexempt from consent requirements under the ePrivacy Directive (Directive 2002/58/EC, Article 5(3)) because they are essential for the service to function. We use browser localStoragefor session state and feature flags; this data stays on your device and is never transmitted to our servers.
11. Children's Privacy
Verifieddit is not directed at children under the age of 16 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal data from children. If you believe we have inadvertently collected data from a child, please contact us at [email protected]and we will promptly delete the data.
12. Security Measures
We implement appropriate technical and organizational measures to protect your personal data, including:
- Encryption in transit:All connections use TLS 1.3 (HTTPS) enforced by Cloudflare
- Access controls:Strict role-based access controls limit who can access personal data
- Content Security Policy:Strict CSP headers prevent unauthorized script execution
- Minimal data collection:We collect only the data strictly necessary for each processing activity
- Client-side processing:Core verification functionality processes data locally, eliminating server-side exposure
- EU hosting:Application servers are hosted in Germany by Hetzner Online GmbH
13. Right to Lodge a Complaint
If you believe that our processing of your personal data infringes the GDPR, you have the right under Article 77 to lodge a complaint with a supervisory authority. You may file a complaint with:
- The supervisory authority in your EU/EEA member state of residence
- The supervisory authority in your place of work
- The supervisory authority in the member state where the alleged infringement occurred
In Austria, where Verifieddit is run from, the supervisory authority is the Austrian Data Protection Authority:
We encourage you to contact us first at [email protected]so we can address your concerns before you escalate to a supervisory authority.
14. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our data processing practices, legal requirements, or new features. When we make material changes:
- We will update the "Last updated" date at the top of this policy
- We will post a prominent notice on our website for at least 30 days
- For material changes affecting the lawful basis for processing or introducing new categories of personal data, we will notify registered users by email
- Where required by law, we will obtain your renewed consent before applying changes
We encourage you to review this policy periodically. Your continued use of the Service after changes are posted constitutes your acknowledgment of the modified policy.
15. Contact Us
For any questions, concerns, or requests regarding this Privacy Policy or our data processing practices, please contact us:
Sanmarcsoft LLC
5900 Balcones Dr, Ste 100
Austin, TX, United States
Data Protection Inquiries: [email protected]
General Legal Inquiries: [email protected]
Sanmarcsoft LLC– Building trust through transparent, privacy-respecting media verification
Privacy Policy Version 2.2 – Effective August 3, 2026