1. Account security

The current Preview uses hashed passwords, expiring server sessions, session rotation, email verification, password reset, login alerts, device/session management, and rate limits on sensitive endpoints. Native mobile session credentials are stored using platform secure storage. Web authentication uses an HttpOnly session cookie.

2. Data access

Owner-based and role-based checks separate private account data from public data. Private certificate codes and Proof Vault records are owner-only. QR codes and public verification pages use a separate publicVerificationId and never require the private certificate code.

3. Data protection

Online deployments require HTTPS, protected application secrets, restricted database access, private object storage, and tested backup and restore procedures. Provider encryption-at-rest claims will be documented only after the production database and storage providers are selected and verified.

4. Upload security

The Preview validates supported file types and size limits, generates controlled file names, and keeps private originals separate from public certificate and QR assets. Production storage must use private access controls and time-limited delivery where appropriate.

5. Monitoring and audit

ContentReceipt records important audit events and uses structured logs, request correlation IDs, health/readiness checks, and error reporting interfaces. Preview integrations may be local or test-only. Production monitoring, alert ownership, incident response, and restore exercises must be completed before launch.

6. Responsible disclosure

Security reports should be sent to . This controlled marker is shown only while the Preview contact channel remains unresolved and must be replaced before production.

7. Limitations

Security is an ongoing process. ContentReceipt cannot guarantee that unauthorized access, service interruption, or misuse will never occur.

1. Data controller

Legal entity

Trading name

Registration number

Address

Country

Privacy contact

Clear review notices are shown while company details remain unresolved. Production is blocked until the required identity and contact fields are complete and professionally approved.

2. Data we collect

• Account data: name, email, password hash, email-verification status, authentication details, and sessions.
• Profile data: avatar, handle, display name, bio, categories, languages, region, ContentMatchup visibility choices, and a public contact method if enabled.
• Connected social data: platform, public username, public profile URL, connection status, permitted public metrics, and backend-only access-token metadata.
• Content and proof data: submitted files or URLs, metadata, content hash, timestamps, public verification ID, private certificate code, proof timeline, certificates, QR codes, and badge assets.
• Safety and AI-check data: declarations, scan status, detected categories, available confidence/provider results, and review decisions.
• Technical and security data: session and device information, audit events, security-relevant IP information, correlation IDs, and error or performance logs.
• Subscription data: plan, subscription status, and future payment-provider references. The Preview does not collect real card data.
• Support and reports: support messages, abuse reports, evidence packages, and reviewer decisions.

3. Why we use data

We use data to provide accounts and authentication; register and protect content; create proof records, QR links, and verification pages; review certificates; connect authorized social profiles; process uploads; prevent fraud and abuse; maintain audit records; support users; manage subscription access; meet legal obligations; and improve reliability where the required permission or other legal basis applies.

4. Legal bases

Draft basis map for professional legal validation. The final basis may vary by feature, jurisdiction, user type, and production provider.

5. Public information

Creators control whether eligible profile, bio, social-profile, follower-count, certificate, and protected-content information is public. QR verification pages can be accessed by anyone who has the public link. Private certificate codes and private Proof Vault records are not intended to appear on public pages.

6. Service providers and recipients

Production may use providers for hosting and databases, object storage, email, identity verification, payment, official social-platform connections, moderation and AI checks, timestamping, security, and monitoring. Data may also be shared with professional advisers or authorities where legally required. A verified subprocessor list must be published before production.

7. International transfers

Future providers may process data outside the EEA. Provider locations, transfer mechanisms, safeguards, and related notices must be documented before production. We do not currently claim that all processing remains in Denmark or the EU.

8. Retention

Some proof, security, transaction, or dispute records may need longer retention for fraud prevention, legal claims, compliance, or backup integrity. Final periods must be approved before production.

9. Your rights

Depending on applicable law, you may have rights to access, correct, delete, restrict, object to, or obtain portable copies of personal data, and to withdraw consent where processing relies on consent. You may also complain to the competent supervisory authority. Rights can be subject to legal exceptions and verified identity checks.

10. Automated checks and decisions

Safety and AI tools may assist certificate eligibility and review. Their signals can be uncertain. Human review may be available, and ContentReceipt should not make a significant solely automated legal decision without the safeguards required by applicable law.

11. Children

ContentReceipt is not designed as an account service for children, and child accounts are not part of the MVP. Users must meet the configured minimum age: . A Family-Friendly Certificate evaluates content; it is not child-account verification.

12. Security

We use technical and organizational safeguards appropriate to the current service, but no system is completely secure. See Security at ContentReceipt.

13. Changes

Material updates will receive a new version and last-updated date. Where required, we will provide additional notice or request renewed consent before a change takes effect.

14. Contact and complaints

Privacy questions and rights requests should be sent to . The competent supervisory authority and final complaint process remain subject to professional legal review.

1. Current inventory

This inventory reflects the current code. ContentReceipt does not currently load an analytics or marketing tracker. Non-essential cookies and similar technologies remain disabled until you provide the required consent and the relevant tool is actually enabled.

Provider for every listed item: ContentReceipt. Environment: website or web dashboard, including local Preview where applicable.

2. Categories

• Essential: authentication, session security, core functions, and remembering consent choices.
• Functional: optional convenience preferences if added and enabled.
• Analytics: optional usage measurement. No analytics tool is active in the current Preview.
• Marketing: optional advertising or campaign measurement. No marketing tool is active in the current Preview.

3. Your choices

You can accept all optional categories, reject non-essential categories, or manage each category. Rejecting non-essential use is as easy to find as accepting it. You can withdraw or change a choice later from this page.

4. Cookies, browser storage, and mobile storage

Cookies are sent with relevant web requests. localStorage stays in the browser until the app removes it or you clear browser data. Native mobile secure storage may hold a mobile session credential, but it is not a web cookie and is removed on logout or session revocation.

5. Blocking essential storage

Blocking the essential session cookie or required browser storage can prevent login, logout, security checks, or preference handling from working correctly. Public pages that do not require an account should remain available.

6. Changes to this inventory

We will update this page before enabling a new non-essential tool. A production consent system must prevent that tool from loading until the required choice is made.

1. About ContentReceipt

ContentReceipt is a creator-protection and content-verification service. It can create proof records, QR verification pages, ContentReceipt-issued certificates, Proof Vault, and reporting tools. Local development may use clearly labelled test providers and test records. Online services do not present test evidence as verified.

2. Eligibility and accounts

You must provide accurate information, protect your account access, and not transfer an account without permission. You must meet the configured minimum age: . Production certificate functions may require identity verification after account creation. Real MitID verification is not active in Preview.

3. User content

You retain your existing rights in content you submit. You give ContentReceipt the limited permissions reasonably needed to receive, store, process, hash, scan, display, and verify that content and its related metadata. You remain responsible for the content, links, and declarations you submit.

You must not register content that you do not own or have permission to register.

4. Proof records and QR verification

ContentReceipt may create a tamper-evident proof record containing information such as a content hash, registration time, public verification identifier, certificate status, and related metadata.

A proof record documents information available at registration. It is not a court judgment, a legal ownership ruling, or a guarantee of priority over every competing claim. QR pages display public-safe information only.

5. ContentReceipt certificates

ContentReceipt certificates are service-issued records based on information, declarations, checks, and provider results available at the time of registration or review. Current types are the Originality Certificate, Human-Created Certificate, Content Safety Certificate, and Family-Friendly Certificate.

Subscription access does not guarantee approval. A certificate may be pending, declined, not eligible, failed, needs review, issued, or revoked. Certificates do not replace professional, legal, editorial, safety, or regulatory review. Public verification pages show the current public certificate status.

6. Certificate limitations

Originality: An Originality Certificate records that content was registered by the identified ContentReceipt user. It is not a legal determination of copyright or ownership.

Human-Created: A Human-Created Certificate is based on a creator declaration and available technical signals. AI detection is not perfect.

Content Safety: A Content Safety Certificate records that the content passed the applicable check at the time of review. It does not guarantee that content is suitable for every person or context.

Family-Friendly: A Family-Friendly Certificate records that content passed a stricter review at the time of registration. It is not a legal child-safety certification and does not guarantee suitability for every child.

7. Prohibited use

You must not use ContentReceipt to:

• register stolen content, impersonate another person, or make false ownership claims;
• mislead viewers, brands, platforms, or authorities with certificates, altered badges, or fake QR codes;
• upload illegal content, child sexual abuse material, malware, malicious files, or content intended to facilitate serious harm;
• harass, abuse, threaten, defraud, or misuse report tools; or
• bypass security, scrape the service, or use unauthorized automated access.

8. Third-party services

ContentReceipt may connect to identity, social-platform, payment, storage, email, moderation, AI-check, security, and timestamp/notary providers. Those services have their own terms, privacy practices, technical limits, and availability. Real provider integrations are not active in the current Preview unless expressly identified.

9. Reports and takedown support

ContentReceipt may help users prepare evidence packages that can support reports to social platforms or other third parties. ContentReceipt does not guarantee takedown and does not decide for Meta, TikTok, YouTube, X, courts, or authorities. Reports are not legal advice, and users decide whether to share a report package.

10. Suspension and termination

ContentReceipt may restrict an account, limit public visibility, reject a request, or revoke a certificate where reasonably necessary for suspected fraud, stolen content, false declarations, illegal conduct, security threats, abuse, or repeated violations. Final notice, appeal, and data-handling procedures require legal review before launch.

11. Service availability

Uninterrupted availability is not guaranteed. Maintenance, provider outages, and changes may occur. Preview data, providers, and features may be changed or reset. Production service obligations will be finalized before launch.

12. Liability and disclaimers

To the extent permitted by applicable law, ContentReceipt is provided without guarantees that every check, report, certificate, provider integration, or verification result will be complete or error-free. Nothing in these Terms excludes mandatory consumer rights or liability that cannot lawfully be excluded.

13. Governing law and disputes

Governing law: . Competent courts: . Mandatory consumer protections and dispute rights continue to apply where relevant.

14. Contact

Legal questions should be sent to . This controlled Preview marker must be replaced by an active contact before launch.

1. Scope

This policy applies to uploads, protected content, public profiles, public verification pages, certificate requests, certificate and badge assets, evidence packages, and abuse reports.

2. Prohibited content

ContentReceipt may restrict, reject, remove, preserve, or escalate content involving:

• child sexual abuse or exploitation material and illegal sexual content;
• non-consensual intimate content, credible threats, or unlawful terrorism-related content;
• severe graphic violence where prohibited, instructions facilitating serious harm, or unlawful hate content;
• scams, fraud, impersonation, stolen content, malware, or malicious files; and
• content that violates another person's rights or is otherwise illegal.

Illegal content may be restricted and reported where legally required.

3. Sensitive or adult content

Lawful adult or sensitive content may still be eligible for an Originality Certificate where the ownership and protection requirements are met. It may be ineligible for a Content Safety or Family-Friendly Certificate, and its public visibility may be restricted. ContentReceipt applies this distinction neutrally and does not shame lawful creators.

4. Content Safety Certificate

This certificate records that a content item passed the applicable safety check at the time of registration or review. It does not guarantee permanent safety or suitability for every audience.

5. Family-Friendly Certificate

This certificate records that the content passed a stricter family-friendly review at the time of registration. It is not a legal child-safety certification and does not guarantee suitability for every child.

6. Human-Created Certificate

Human-Created review combines the creator's declaration with available technical signals. AI detection is not perfect, can produce false results, and cannot prove with certainty that no AI tool was used.

7. Review and enforcement

A certificate may be pending, issued, needs review, not eligible, failed, or revoked. ContentReceipt may revoke a certificate when new evidence appears, a false declaration is discovered, the underlying content changes, a QR or badge is misused, or a policy violation occurs. Provider results are test-only in the current Preview.

8. Reporting concerns

Report suspected harmful content, impersonation, certificate misuse, or child-safety concerns through the working Report Abuse route. A report receives a reference and is kept private; production launch requires a staffed and documented escalation process.

1. Plans

The trial starts automatically, requires no card, does not renew automatically, and does not create an automatic charge.

Subscription access does not guarantee that any specific certificate will be issued.

2. Billing cycle and renewal

The free trial ends after 30 days and does not convert into a charge automatically. The planned paid Full Protection subscription is monthly and may renew automatically only after the user explicitly completes a reviewed checkout flow. The exact charge date, renewal notice, and billing language remain subject to payment-provider and legal review. No real financial transaction occurs in Preview.

3. Price, currency, and taxes

The displayed future price is $12.99 per month. Final supported currencies, VAT or sales-tax treatment, invoice information, and tax-inclusive presentation must be confirmed before live billing.

4. Payment authorization

Live payment authorization terms will be added before real charges are enabled. ContentReceipt does not collect card data. Preview may use Stripe test checkout, which cannot create real charges.

5. Failed payments

The future retry, notice, grace-period, and access rules for failed payments require payment-provider and legal review. Preview billing status is mock data only.

6. Plan changes

The final upgrade, downgrade, proration, and effective-date rules will be presented before a user confirms a paid change. Preview controls only change local test state.

7. Cancellation and access afterward

The production service will provide a clear cancellation method. Unless mandatory law requires otherwise, planned access is expected to continue through the paid period; existing records should remain viewable, while new protection and certificate review require active Full Protection. Final timing and data-access rules require review.

8. Refunds and statutory rights

Refund rules are unresolved. Where mandatory consumer law provides a withdrawal or cancellation right, those rights remain unaffected. No exception for immediate service activation will be used until the activation and consent flow has received professional review.

9. Service changes and suspension

ContentReceipt may change or suspend test features during Preview. Production notice, price-change, material-change, fraud, and account-suspension rules must be finalized before billing begins.

10. Required review before live billing

Checkout wording, the obligation-to-pay action, immediate service activation consent, withdrawal information, renewal notices, cancellation, refunds, VAT and currency, business identity, and payment-processor privacy disclosures are release blockers.

11. Contact

Billing and subscription questions will use once the support channel is active.