Legal
Privacy policy
Updated
This policy explains how LikePact (“we”) handles personal data on likepact.com, in the LikePact app and through our API. If anything is unclear, write to [email protected].
Who we are
LikePact, based in Slovenia, is the controller for the personal data described here, unless a section says otherwise.
When a brand uploads assets or invites team members, the brand decides what goes into its workspace, and LikePact processes that content on the brand’s behalf. Enterprise customers can sign a data processing agreement (DPA) with us.
The short version
- You decide what of your likeness we hold. Creators choose whether to upload reference photos. Brands see only a creator’s cover photo and summary until a licence is in force.
- We don’t use your likeness to train AI models, and we don’t sell personal data.
- Consent records are permanent by design. The consent ledger can’t be edited or deleted, so it can always prove what was approved. It holds identifiers and hashes, not photos.
- Our website analytics use no cookies and don’t identify you.
- Files are stored in the EU, and our servers are in Germany.
What we collect, why, and on what legal basis
Accounts (creators and brands)
- Data: name, email address, password (stored only as a secure hash), account type, organisation and role, and sign-in records.
- Why: to provide the service and keep accounts secure.
- Legal basis: performance of a contract (GDPR Art. 6(1)(b)) and our legitimate interest in security (Art. 6(1)(f)).
Creator profiles and likeness data
- Data:
- display name, avatar and verification status;
- standing terms: channels, territories, excluded categories, minimum fee, maximum term and hard no’s;
- reference photos and a written style profile, if the creator adds them.
- Why: so brands can find the creator, request licences within their terms, and, under a licence in force, create assets of them.
- Who sees what: brands see only the cover photo and a short summary in the directory. The reference photos and full style profile are available only to a brand with a licence in force that day, and every view and export is recorded in the consent ledger.
- Verification: our team reviews creator verification manually. We don’t use automated facial recognition.
- Legal basis: consent and performance of a contract (Art. 6(1)(a) and (b)). Where facial images count as biometric data, we rely on explicit consent (Art. 9(2)(a)).
- Withdrawing consent: creators can delete reference photos at any time. Ending an active licence follows the revocation terms of that licence.
Assets and approvals
- Data: files uploaded by brands, their SHA-256 hashes, licence checks, the creator’s decisions (approve, decline, request an edit), and signed versions with their C2PA manifests.
- Why: to check assets against licences, collect approval, and label and sign approved files.
- Legal basis: performance of a contract (Art. 6(1)(b)).
Consent ledger
- Data: an append-only record of licence grants, approvals, revocations, downloads and access to likeness data. It holds identifiers, timestamps and file hashes. It does not hold photos or files.
- Why: to prove what was consented to, by whom and when. That proof protects creators and brands alike.
- Legal basis: our legitimate interest in establishing, exercising and defending legal claims (Art. 6(1)(f), and Art. 17(3)(e) for erasure requests).
- Retention: ledger entries can’t be changed or deleted. When you close your account, your other data is deleted as described below, and the ledger keeps only the identifiers it needs to stay verifiable.
Payments
- Data: payout and billing details, fees and payment status.
- How: payments and payouts are handled by Stripe, a regulated payment provider. Brands save their card on Stripe’s own page, and creators give their identity and bank details to Stripe during payout onboarding. We don’t receive or store full card or bank numbers; we keep the card brand, its last four digits and expiry, and the status of each payment and payout.
- Legal basis: performance of a contract, and legal obligations such as bookkeeping (Art. 6(1)(b) and (c)).
- Data: your email address and the messages we send you.
- What we send: account email only: confirmations, password resets, approval requests and licence notices. We don’t send marketing email without your consent.
- Legal basis: performance of a contract (Art. 6(1)(b)).
Website analytics
We use Plausible Analytics. It sets no cookies, collects no personal data and counts visits in aggregate. Our legal basis is our legitimate interest in understanding how the site is used (Art. 6(1)(f)).
Abuse protection
To stop automated sign-ups, we briefly use your IP address to rate-limit forms. The IP address isn’t stored with your account.
Cookies
The website sets no cookies. The app uses one strictly necessary cookie to keep you signed in.
Who we share data with
We use these service providers (sub-processors), each under a written data processing agreement:
| Provider | Purpose | Location |
|---|---|---|
| Hetzner Online | Application servers and database | Germany |
| Cloudflare | Website hosting, security, file storage (R2, EU jurisdiction) | EU storage, global network |
| Resend | Transactional email | United States (Standard Contractual Clauses) |
| Stripe Payments Europe, Ltd. | Card payments, creator payouts and the identity checks they require | Ireland (EU), with transfers to Stripe, Inc. in the United States (Data Privacy Framework) |
| Plausible Analytics | Cookie-free website analytics | EU |
Brands receive creator data only as described above. We don’t sell personal data, and we don’t share it for advertising.
International transfers
Files, likeness data and the database stay in the EU. Where a provider processes data outside the EU or EEA, such as email delivery or Cloudflare’s global network, we rely on the EU–US Data Privacy Framework or the EU Standard Contractual Clauses.
How long we keep data
- Accounts: for as long as the account is open. After you close it, we delete your data within 30 days, except what we must keep for the reasons below.
- Reference photos: deleted when the creator removes them or closes their account.
- Approved assets and signed files: kept for the licence term plus 3 years, to support takedowns and legal claims.
- Invoices and bookkeeping records: kept for 10 years, as Slovenian tax law requires.
- Consent ledger: kept permanently, as described above.
- Earlier waitlist sign-ups: deleted 12 months after sign-up, unless you create an account.
Your rights
Under the GDPR you can:
- ask for a copy of your data;
- correct it;
- delete it;
- restrict or object to its processing;
- receive it in a portable format;
- withdraw consent at any time.
Write to [email protected]. We’ll answer within one month.
If you’re unhappy with how we handle your data, you can complain to the Information Commissioner of the Republic of Slovenia (Informacijski pooblaščenec, ip-rs.si) or to the data protection authority where you live.
Security
How we protect data is described on our security page.
Changes
If we change this policy in a way that matters, we’ll update the date above and email account holders before the change takes effect.