Skip to content
Sign inTry it free

Privacy policy

As of November 2026

Controller

DIGITALPASSION Ltd., Tassou Papadopoulou 16, House 2, 8270 Tremithousa, Cyprus, represented by Kevin Damiani. Email: info@kontiqo.io.

In brief

kontiqo schedules your posts and publishes them at send time to LinkedIn, Facebook and Instagram. We store the text and media of a post only until it is sent; exceptions and what remains afterwards are listed under "How long we keep data". In the desktop app, your drafts and their history stay on your computer; a post only comes to us when you schedule it, an image from it when you choose it as the start of a Canva design and, if you turn it on, an encrypted backup. We use no cookies and no tracking across other websites; how often our pages are visited is counted by our own server (see "Audience measurement"). No AI runs on our servers.

Hosting and logs

Our servers run at Hostinger International Ltd., 61 Lordou Vironos Street, 6023 Larnaca, Cyprus, in the Frankfurt am Main data centre. For kontiqo.io, app.kontiqo.io, server.kontiqo.io and data.kontiqo.io our web server keeps no access log; it only passes on page views on kontiqo.io and app.kontiqo.io, shortened, for audience measurement (see "Audience measurement"). If it cannot reach one of our services, it writes an error line with the details of the request: time, method and protocol, host, path and referring page (both without the query part), the remaining headers such as browser identifier and language setting, the result and your IP address with port, shortened to the first 24 bits (IPv4) or 48 bits (IPv6); it does not record cookies or sign-in credentials. Like the logs of our services, these lines are overwritten continuously (see below).

Our services log errors and events without IP addresses, for account events with the account ID. One exception is the sign-in service behind data.kontiqo.io: when it rejects a request or a request fails (such as a wrong or expired code, an expired sign-in or too many attempts), it logs the time, type of request, path, result, referring page and your IP address in order to detect and fend off misuse such as guessing codes. It does not log successful requests. The gateway to the database, sign-in and file storage (data.kontiqo.io) logs each request with time, type of request (such as download or upload), path (for files including your account ID), result, size of the response, referring page and browser or program identifier, without your IP address. The logs are overwritten continuously: we keep at most 50 MB per service, and older entries drop out as new ones arrive. There is therefore no period in days; the fewer requests, the longer an entry remains. The legal basis is our legitimate interest in secure and stable operation and in fending off misuse (Art. 6(1)(f) GDPR).

Audience measurement

We count how often the pages of kontiqo.io and app.kontiqo.io are visited with the open-source software Umami, which we run ourselves on our server at Hostinger in Frankfurt am Main. No script runs in your browser for this; we store nothing on your device, read nothing from it and set no cookie. Instead, for every page view that loads successfully, our web server passes the following to Umami: the address of the page and of the page you came from, each without the query part, the time, the browser identifier and your IP address, shortened to its first 24 bits (IPv4) or 48 bits (IPv6). It passes on no other details of the request, such as cookies, sign-in data or language settings, and it keeps no log itself.

Umami stores neither your IP address nor your browser identifier. From them it derives browser, operating system, device type and approximate country, region and city, and it forms an identifier from the website, the shortened IP address, the browser identifier and a random value that changes daily, which groups page views of the same day. On the next day the same browser gets a new identifier, so we do not recognise you across days. We do not link this data to your account and draw no conclusions about you as a person.

Umami deletes every entry after 363 days. We keep encrypted backups on our own hardware in Cyprus and Germany; at the latest 400 days after a page view, the last copy is deleted as well. No further service provider is involved.

Counting does not access your device and therefore needs no consent (Art. 5(3) of Directive 2002/58/EC, in Germany Section 25 TDDDG). The legal basis is our legitimate interest in knowing which pages are read and where visitors come from, so that we can improve our offering (Art. 6(1)(f) GDPR). You can object to the measurement at any time on grounds relating to your particular situation (Art. 21 GDPR), for example by writing to info@kontiqo.io.

Account and sign-in

For your account we store your email address, your settings and the status of your subscription. You sign in with a code we send you by email. For each session, the IP address and browser identifier are stored until you sign out or delete your account.

Every sign-in, code request, sign-out and session refresh is recorded in a sign-in log with the time, the ID and the email address of your account, without the IP address. It serves to investigate misuse of your account and is deleted after 30 days, immediately when you delete your account. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR).

We run the database, sign-in and file storage ourselves on our servers at Hostinger in Frankfurt am Main (using the open-source software Supabase); no further service provider is involved. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

Channels and publishing

When you connect a channel, the platform gives us an access key, the IDs of the account or page and the display name. We store the key encrypted. At send time we transfer the post's text and media to the platform and afterwards keep only whether and when it was published and its platform ID.

Media are kept in our file storage until sending (if a post is never sent, for example because you do not approve a suggestion from your AI, at most until the period under "How long we keep data"); Meta fetches them from there via an address valid only for that post. If you marked an image as made with AI, we tell Instagram, which then shows its "AI info" label. Statistics on your posts are fetched from the platform on demand, never stored in the database and kept in memory for at most five minutes.

Platforms: LinkedIn Ireland Unlimited Company, Wilton Place, Dublin 2, Ireland, and Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland. Their privacy policies govern what happens to your posts there. If you remove kontiqo in your Facebook settings, we are notified and stop using the connection. If you request deletion of your data there, we immediately delete the connection, channels, posts and media; the confirmation is shown at app.kontiqo.io/meta-deletion. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

AI applications via MCP (optional)

You can connect ChatGPT, Claude, Le Chat, Grok or another AI application to kontiqo via MCP. This only happens if you agree on our consent page. kontiqo then gives the application your channels and posts on your instruction and accepts posts from it. The provider of the AI application is responsible for its own processing. You can disconnect it at any time in your account under "AI applications"; the application then receives no more data. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

Canva and stock photos (optional)

When you connect Canva, Canva gives us an access key and the ID and display name of your Canva account; we store the key encrypted. We use it to show you your designs, create new ones on your request (optionally starting from an image of your post, which we send to Canva for that) and bring the finished design into the app as a file. We only pass previews and files through and do not store them. When you disconnect Canva, we revoke the access at Canva and delete the key. Canva is Canva Pty Ltd, 110 Kippax Street, Surry Hills NSW 2010, Australia; there is no adequacy decision for Australia, and Canva covers transfers with standard contractual clauses. Canva's privacy policy governs what you design in Canva.

When you search for stock photos, our server sends the search term and language to Pexels, a brand of Canva Germany GmbH, Pappelallee 78/79, 10437 Berlin, Germany; Pexels does not learn your account, and we do not store the search term. The app loads previews and the chosen photo directly from Pexels, so Pexels sees your device's IP address.

The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

Calendar (optional)

If you connect your Google Calendar in the app settings, we ask Google only for the ID and email address of your Google account and for the right to create a calendar "kontiqo" of our own and to edit only that one; we do not see your other calendars and events. We store the access key Google gives us for this encrypted. For each scheduled post our server adds to this calendar the channel, time, status, the first line of the text, your chosen reminder, a link to the post with an identifier of your kontiqo account and, after posting, the link to the published post. If you disconnect Google Calendar, we delete the calendar "kontiqo" in your Google account while the access still exists, revoke the access at Google and delete the key. Google is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

kontiqo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use this data only to add your posts to your calendar, do not share it, do not use it for advertising and do not train AI with it.

If you create a subscription link, our server delivers the same events as a calendar file to anyone who knows the link. We store only a check value of the link, never the link itself. If you create it anew or turn it off, the old one no longer works. How often your calendar program fetches the link is up to the program.

For Apple Calendar see "The desktop app". The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

Payment

You buy the subscription through Stripe Managed Payments. The seller towards you is Sold Through Link, LLC ("Link"), a Stripe subsidiary; for the EU, payments are processed by Stripe Technology Europe, Limited. Stripe and we are each independent controllers. We send Stripe your email address and your account ID and receive the status and term of your subscription. We never see your payment details. You can also manage purchases at link.com. If your bank reverses a payment or asks about it (chargeback), Stripe tells us; while the dispute is open, your subscription does not renew, if we lose it, your subscription ends immediately without a refund, and we store with your subscription the ID, status and times of the dispute and whether we lifted the hold: after an outcome without loss for us or after lifting the hold at most 35 days after the dispute is closed, otherwise until the subscription ends. For the state of chargebacks, the legal basis is our legitimate interest in protecting ourselves against payment defaults (Art. 6(1)(f) GDPR). Otherwise, the legal bases are the performance of the contract and statutory retention obligations (Art. 6(1)(b) and (c) GDPR).

Emails

We send sign-in codes and notices about posts that were not confirmed as published through Resend, Inc., 2261 Market Street #4103, San Francisco, CA 94114, USA. Resend is certified under the EU-US Data Privacy Framework; standard contractual clauses also apply. We do not send you advertising. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

Contact form and email to us

If you write to us through the contact form, we send your name, email address, message and the page language via Resend to our mailbox; we store none of it in our database. Our mailbox is hosted by Fastmail Pty Ltd, Level 2, 114 William Street, Melbourne, Victoria 3000, Australia. Fastmail stores emails in the EU or the USA and always keeps a copy, backups and logs in the USA. Transfers to Australia and the USA are covered by the European Commission's standard contractual clauses.

We use your details only to reply to you and delete the message once the request is settled and no statutory retention obligation applies. The legal basis is our legitimate interest in answering requests (Art. 6(1)(f) GDPR) or, where a contract is concerned, Art. 6(1)(b) GDPR.

The desktop app

The desktop app stores your drafts with their text and media, also as history after sending, the daily history of your statistics, your logo and the backup details in a database in the app's data folder on your computer, separately for each kontiqo account. The app remembers the font size and the language you last chose for all accounts on this computer in its own storage. We have no access to this database. Only what you schedule comes to us from it (text and media until sending, see "Channels and publishing"), an image you choose as the start of a Canva design (see "Canva and stock photos (optional)") and, if you turn on the backup, an encrypted copy only you can decrypt: your drafts with their send times (without media files) and the statistics history (see "How long we keep data").

The app keeps your sign-in, the backup key and the secret of the local interface in your operating system's keychain. When you sign out, it removes the sign-in and the backup key. If you delete your account in the app, it also removes that account's drafts, history and media on this computer; whatever cannot be removed right away, it removes at the next start. Otherwise the local data stay until you delete them in the app or remove the app together with its data folder.

Before a JPEG photo or a video leaves your computer, the app removes the location data (GPS) from its metadata (EXIF, XMP, video location). Not covered are location data a camera writes into the recording itself (such as action camera telemetry), motion photos that carry a video inside the photo, and further images or extended metadata inside a photo. The app converts other image formats to JPEG without metadata; GIF files and PDF documents go out unchanged.

For AI applications on the same computer, such as Claude, the app offers a local interface. It can only be reached from your computer and only used with a secret that you store in the AI application when setting it up. Besides the keychain, this secret is stored unencrypted in the setup file in the cache of the app and, once set up, in the files of the AI application (for Claude, in its extensions folder); anyone who can read these files can use the interface. If you remove the extension in the AI application and set it up again, the app creates a new secret. The provider of the AI application is responsible for what the application reads through it.

At start, then at most every 6 hours and when you check for updates yourself, the app asks data.kontiqo.io whether there is a new version and downloads it from there. It sends the operating system, the processor type and the identifier of the update program, not your account. Every new version is signed by us; the app does not install a file without a valid signature.

If you turn on Apple Calendar in the settings, the app asks for access to your calendars on Mac, iPhone or iPad and creates its own calendar "kontiqo": in iCloud if you use iCloud for calendars, otherwise only on the device. For each scheduled post it adds the channel, time, status, the first line of the text, your chosen reminder, a link to the post with an identifier of your kontiqo account and, after posting, the link to the published post; it does not read your other calendars. If the calendar is in iCloud, Apple stores and syncs it as part of your iCloud account; we ourselves do not send anything to Apple. If you turn it off, the app removes its events, and the calendar if it is empty afterwards, as soon as it syncs on a device with access; if you delete your account in the app, it does so right away on the device you delete it on, if that device has access. If the calendar is in iCloud, this applies on all your devices, otherwise only on the device concerned. Events more than 30 days in the past, and events in a calendar that no device with access syncs afterwards (for example after deleting your account in the browser or on another device), may stay until you remove them yourself; so may an empty calendar "kontiqo". You can withdraw access at any time in the system settings.

Storage on your computer is strictly necessary for the app and therefore needs no consent (Art. 5(3) of Directive 2002/58/EC, in Germany Section 25(2) no. 2 TDDDG). The legal bases are the performance of the contract (Art. 6(1)(b) GDPR) and, for checking for updates, our legitimate interest in secure and up-to-date software (Art. 6(1)(f) GDPR).

Storage in the browser

The web app keeps your sign-in in your browser's local storage so that you stay signed in. This is strictly necessary for the service and therefore needs no consent (Art. 5(3) of Directive 2002/58/EC, in Germany Section 25(2) no. 2 TDDDG). Until 15 November 2026 the same storage remembers on the public pages that you have seen the notice about the new kontiqo, so that it does not appear again; this entry stays in your browser. Fonts are loaded from our own server.

How long we keep data

Our database and file storage delete automatically according to these rules (the periods for audience measurement are listed under "Audience measurement"):

  • Text of a scheduled post or one awaiting your approval: at most 30 days after the scheduled time (after a retry, from the time of the retry), earlier on sending, discarding, disconnecting the channel or deleting the account.
  • Images and videos of a scheduled post or one awaiting your approval: at most 30 days after the scheduled time (after a retry, from the time of the retry), earlier on sending, discarding, disconnecting the channel or deleting the account.
  • Uploaded media not attached to any post: at most 1 day after creation, earlier on deleting the account.
  • Text and media of a failed or unclear post: at most 30 days after the failure, earlier on sending, discarding, disconnecting the channel or deleting the account.
  • Record of a published post (status, time, platform ID, the name of the AI app that scheduled it, if any; without text and media): at most 730 days after sending, earlier on deletion by you, disconnecting the channel or deleting the account.
  • Record of a discarded post (without text and media): at most 30 days after discarding, earlier on disconnecting the channel or deleting the account.
  • First comment or reshare by another account: text and time until it runs, afterwards status, time, platform ID and address, and the error reason if any: at most 730 days after creation, earlier on discarding, deletion by you, disconnecting the channel or deleting the account.
  • Connected channel (type, platform IDs, display name): until disconnecting the channel or deleting the account.
  • Platform access keys, encrypted: until disconnecting the channel or deleting the account.
  • Canva access keys, encrypted, with the ID and display name of your Canva account: until disconnecting Canva or deleting the account.
  • Chosen reminder for calendar events, a check value of the subscription link (never the link itself) and whether Apple Calendar is turned on: until deleting the account.
  • Access keys for your Google Calendar, encrypted, with the ID and email address of your Google account: until disconnecting Google Calendar or deleting the account.
  • Link between a post and its event in your Google Calendar (without text); also removed as soon as the post no longer appears in the calendar: until disconnecting Google Calendar or deleting the account.
  • Backup of drafts and history that only you can decrypt: until turning off the backup or deleting the account.
  • Uploaded backup until it is confirmed, and turned-off or replaced backup until it is removed (encrypted): at most 3 hours after creation, earlier on deleting the account.
  • ID of a deleted account and its files, until they are removed from storage: right after the deletion and, as a safeguard, a second time once no previously issued upload address is valid: at most 2 days after creation.
  • Process of connecting a channel, Canva or your Google Calendar: at most 1 day after creation, earlier on deleting the account.
  • Account: email address, settings, subscription status: until deleting the account.
  • Chargeback on your subscription and the renewal hold (ID, status and times of the dispute, how long the subscription is paid for, when we lifted the hold): until the subscription ending or deleting the account.
  • Closed chargeback without loss for us or after the hold was lifted (ID, status, times): at most 35 days after the dispute is closed, earlier on deleting the account.
  • Sign-in log: type of event (such as sign-in, code requested, sign-out), time, account ID and email address, without IP address: at most 30 days after creation, earlier on deleting the account.
  • ID and type of a payment notification (against double processing): at most 30 days after creation.
  • Heartbeat of our background services (no user data): at most 7 days after the last change.

Your rights

You have the right of access, rectification, erasure, restriction of processing and data portability (Art. 15 to 20 GDPR). You can withdraw consent at any time with effect for the future. You can delete your account with all data yourself in the app. For anything else, write to info@kontiqo.io.

Right to object (Art. 21 GDPR): where we process data based on our legitimate interest, you can object at any time on grounds relating to your particular situation.

You can lodge a complaint with a data protection supervisory authority, in particular in the member state where you live or work (Art. 77 GDPR). Our lead authority is the Commissioner for Personal Data Protection, Iasonos 1, 1082 Nicosia, Cyprus, www.gov.cy/dataprotection.

Obligation to provide data and automated decisions

You are under no statutory or contractual obligation to give us data. Without an email address, however, we cannot create an account, and without a connected channel we cannot publish anything. There is no solely automated decision within the meaning of Art. 22 GDPR.

Security

All connections are encrypted with TLS. Platform access keys are additionally stored encrypted.