Trust
Security
Updated
LikePact holds two of the most sensitive things a person or company can share: a creator’s likeness, and proof of what they agreed to. This page describes how we protect both. To report a vulnerability, see the end of this page.
Data storage
- EU storage. Uploaded files, reference photos and signed assets are stored in Cloudflare R2 with EU jurisdiction enforced. The application refuses to start with storage outside the EU.
- Servers in Germany. The application and database run on dedicated infrastructure in Germany.
- Private by default. Media is never public. Files are served only through short-lived, signed URLs, after an access check.
- Encryption. All traffic uses TLS. Stored files are encrypted at rest.
- Backups. The database is backed up automatically.
Access control
- Tenant isolation. Every brand is a separate tenant. Each request is checked against an active membership of the organisation it targets. Queries without a tenant context return nothing, so the system fails closed.
- Roles. Brand members are admins, members or viewers. Viewers are read-only, and the API enforces this.
- Creators see only their own data, across every brand they work with.
- Likeness data is gated by licence. A brand can open a creator’s reference photos and style profile only while a licence between them is in force, and every view and export is logged.
- Staff access to production is limited to the people who run it.
Consent ledger
Every licence grant, approval, revocation, download and access to likeness data is written to an append-only, hash-chained ledger:
- Each entry includes the hash of the previous one, so any change breaks the chain.
- The database refuses updates and deletes on ledger entries.
- Entries are written in the same transaction as the change they record, so there is never a state change without a record.
- The whole chain is verified automatically every night.
Asset integrity and signing
- Every upload is hashed (SHA-256) when it arrives. The file is checked against that hash again before signing, so what is signed is exactly what was approved.
- Approved assets are signed with C2PA. The manifest records that the asset is AI-generated, links to the original as its parent, and references the consent record. Production signing uses LikePact’s own certificate.
- Visible AI labels are burned into approved images, or confirmed present in the brand’s own file.
Application security
- Passwords are stored only as salted hashes. Sessions use short-lived access tokens.
- Sign-up, sign-in and other forms are rate-limited against automated abuse.
- Every change is linted, tested and checked against a fresh database migration automatically before it is deployed.
Reporting a vulnerability
If you believe you’ve found a security issue, email [email protected] with the details and steps to reproduce. Please don’t access other people’s data or disrupt the service while testing.
We’ll acknowledge your report within two working days and keep you updated. We won’t take legal action against good-faith research that follows these rules.