Bite-FinderPrivacy
Who is responsible?
Konstantinos Evangelopoulos, Costa Colorado, Taunusstraße 26, 65779 Kelkheim (Taunus), Germany, costa@costacolorado.com.
What is this Cockpit for?
Your company has commissioned Costa Colorado to produce content. In this Cockpit you review that content, comment on it, approve it and download it. We process your data to carry out this engagement with your company (Art. 6(1)(b) GDPR) and because we have a legitimate interest in a traceable, secure approval process (Art. 6(1)(f) GDPR).
The content in this Cockpit is produced with AI tools (text, image, video). Its origin is stated in the text file that comes with every download.
What do we store?
- Your account: e-mail address, name and role — as your company invited you.
- Your work: comments, replies, decisions, approvals and hand-offs, each with your name and time. Downloads are recorded with file and time.
- Usage: which content you opened and when. From this we measure how long an approval takes and how often follow-up questions are needed — not to rate you, but to improve the process.
- Sign-in and session: time of sign-in, a device label (e.g. “desktop · Chrome”) and your IP address in hashed form only, to detect sign-in abuse.
- Sign-in attempts: for every request of a sign-in link we store the e-mail address entered, the IP address, the browser identifier, the time and the result — also when the address has no account. This protects the Cockpit against attacks that try out addresses (legitimate interest, Art. 6(1)(f) GDPR). An IP address that tries several unknown addresses within a short time is blocked from signing in for 24 hours.
- Mail: we send you a mail to sign in and when something in the Cockpit needs you. We only keep that and when a mail went to your account (90 days), not its content.
Cookies
Only technically necessary ones: your session, a one-time value for sign-in and your language. No tracking, no advertising, no third-party services in the browser. That is why there is no cookie banner.
Where is the data?
On a server in Frankfurt am Main, Germany (Hostinger International Ltd., data processor). Database, files and mail delivery run on this server. A daily encrypted backup copy is stored with Google (Google Drive); the key stays on our server only, Google cannot read the copy. Files are delivered through short-lived signed links.
We also hand scheduled posts over to Zernio (see “Publishing on social media (Zernio)”). The image of such a post is sent as a copy; the originals stay on this server.
Publishing on social media (Zernio)
When a planner schedules an approved post, we hand it over to Zernio, a service for scheduling and publishing posts on social media channels. Provider and data processor: ZERNIO SOFTWARE SL, Palamós (Girona), Spain.
- When: only after the post is approved in the Cockpit and a planner has scheduled it with a click. Nothing that is not approved goes to Zernio.
- What: the text of the post, the first comment under the published post if there is one, the image, the planned time and the target channel (for example LinkedIn).
- Why: Zernio creates the post in the brand’s social media account and publishes it at the planned time.
- What does not go to Zernio: your comments and approvals in the Cockpit, sign-in data and files from requests.
Where Zernio processes data and which service providers it uses are described in the Zernio privacy policy (https://zernio.com/privacy-policy) and in its list of subprocessors (https://zernio.com/subprocessors).
Passkeys
To schedule posts, planners confirm with a passkey (Face ID, Touch ID or Windows Hello). We store only a public key, a counter, the device name of the session (for example “desktop · Chrome”) and when the passkey was set up and last used. Your fingerprint or face never leaves your device. The passkeys are deleted when your access ends or when the operator resets them.
For how long?
- Sign-in links: 24 hours. Sessions: 60 days after they end. Mail log: 90 days. Backups: 30 days.
- Comments and approvals: as long as your company uses the Cockpit — they document who approved what and when.
- Usage and sign-in log (which content you opened and when, sign-ins with hashed IP address): as long as your company uses the Cockpit — as an audit trail against abuse and to measure the process.
- Sign-in attempts (e-mail address entered, IP address, browser identifier): 90 days.
- Website review access (overlay grant: which member, website and device session; only a hash of the token): 30 days after it ends, or earlier on sign-out.
- If you leave the team, your account is disabled immediately. On request we anonymise name and e-mail; the approval record remains without your name.
- When the engagement with your company ends, it receives all content as an export; then we delete database and files. Backups expire within 30 days.
Your rights
Access, rectification, erasure, restriction, data portability and objection under Art. 15–21 GDPR — an e-mail to costa@costacolorado.com is enough. You may also lodge a complaint with a data protection authority, for example the Hessian Commissioner for Data Protection and Freedom of Information.
No automated decisions: we make no decisions about you based solely on automated processing.
Last updated: October 2026.
← Welcome back
Imprint · Privacy