Privacy
Kröno.io is a shared content calendar and publisher used by an organization's own team. It isn’t open to new organizations yet; when sign-up opens, an organization signs up and its administrators invite the rest of the team. Everything below describes what the software actually does.
What is collected
- Your account. The email address you sign up or are invited with, a display name, and which organization and role you hold. Your email address is verified and held by our authentication service; Kröno.io never stores a password for you. If you add a passkey, only the public part of it is stored; the private part never leaves your device. If you turn on two-step sign-in, our authentication service also holds the secret key your authenticator app uses to make its codes.
- Your organization. The business name, address, phone number, contact email and website an administrator enters, and the time zone the organization schedules in.
- Billing. Whether the organization is on its free trial or subscribed, how many active members it has, and the identifiers our payment processor assigns to it. Card numbers and bank details are entered on the payment processor's own pages and never pass through Kröno.io.
- What you create. Posts, captions, hashtags, comments, approvals, schedules, campaigns, and the photos and videos you upload.
- AI drafts. When someone asks for a plan of drafts for a campaign, the request they typed, the drafts that come back, each decision made on them, and a record of each request (which model answered, how much text went in and out, and an estimated cost) are kept with the campaign. Nothing is published or scheduled by this; every draft still goes through the same review as any other post.
- Connected social accounts. When you connect a social media account, the access credentials that platform issues are stored encrypted. They are never sent to your browser. Kröno.io also keeps the identifiers the platform returns (the account's or Page's ID; for a Facebook Page, the ID Facebook assigns to the person who connected it; for an Instagram account, the ID Instagram gives Kröno.io for it), the account's name, username and profile picture link, and for each post it publishes, the post's ID and link. They are used only to show which account a post goes to, to check the connection, to publish, to show you a published Facebook post as your Page has it (read back from Facebook when you look at it, and not stored), to edit the caption of a Facebook photo or album post or delete it at your request, to link to the published post, to ask Facebook to end Kröno.io's access when a Page is disconnected or the person who connected it has their Kröno.io account deleted, and to act on Meta's notice when someone removes Kröno.io in Instagram or on Facebook, or asks for their data to be deleted. When a Facebook post's caption is edited or the post is deleted from Kröno.io, Kröno.io records who did it and when, and the new caption.
- The sign-in record. Each time you sign in, the server records who signed in, which organization, the time, the address your connection came from, a description of your browser, and whether you used an email link, a code or a passkey. The record exists for security: to notice an account being used by someone it should not be, and to investigate afterwards.
- Operational records. An audit history of actions taken in the workspace, and a record of each attempt to publish a post. These summaries deliberately contain no names, email addresses, credentials or post content.
- Bot protection. Signing up and signing in include a check that you are a person, provided by a third-party service. It sees the request it verifies; it does not run anywhere else in the application.
How signing in works
Access is by emailed sign‑in link or code, or by a passkey you have added. Kröno.io does not store passwords and does not offer password registration. If you turn on two-step sign-in under Account & Security, each sign-in also asks for a 6-digit code from your authenticator app. You can turn it on while you belong to an organization. If you lose your app, a super administrator of your organization can reset it: you are emailed at once, and the reset takes effect after 24 hours unless you cancel it. Your session is kept in your own browser's local storage. The application sets no cookies. The bot check on the sign‑up and sign‑in pages runs in a frame from its provider, under that provider's own policy.
What is not done
There is no advertising, no analytics, no behavioural tracking and no third‑party tracking scripts in this application. Your content is not used to train models and is not sold or shared for marketing. Fonts and every other asset are served from this site itself, so simply loading a page — including this one, signed out — contacts no one else. There are two exceptions. One is the bot check on the sign‑up and sign‑in pages, described above. The other: signed‑in pages that show a connected account load its profile picture from that platform's image servers, and a published Facebook post shown as your Page has it loads its photo from Facebook's. Those servers then see your connection's address and a description of your browser, as they would if you opened the picture there.
Who else processes this data
We rely on service providers to run Kröno.io: for hosting, the database, authentication and file storage, domains and networking, email delivery, payments, bot protection, and the AI models that write drafts. Each receives only what its part of the service needs, acts on our instructions to provide the service, and may not use what it receives for its own purposes. Payment handling receives your organization's name, contact email and billing address. A request for AI drafts sends the campaign's name, dates, channels, brief and objective; the brand profile (its voice, audience, required disclaimers and prohibited phrases); each program it covers by name, description, audience and default call to action, and whether it has a landing page; the text typed for the request and its settings (how many posts a week, the tone); and, for a rewrite, the draft being rewritten (its label, caption, call to action, hashtags and objective) with the note given for it. It never sends members' names or email addresses, connected-account credentials, media, the sign‑in record or anything from another organization, and what is sent is not used to train models. Posts you publish go to the social media platforms you connect, only for accounts you choose to connect, and what happens to a post after it reaches a platform is governed by that platform's own terms.
If you need to know which company fills one of these roles, write to privacy@krono.io.
How content is protected
Uploaded photos and videos are private by default. They are not publicly addressable; previews are served through short‑lived signed links that expire. Access to every record is enforced by the database itself on each read and write, scoped to your organization and your role — not by the interface. Social credentials are encrypted where they are stored. The sign‑in record can be read only by your organization's own super administrators and by the service itself.
Retention
- Your account and content exist while your account and your organization exist; deletion is described on the data deletion page.
- The sign‑in record is kept for 12 months from each sign‑in, then deleted automatically. If your account is deleted sooner, the entries lose their link to you but are kept to the same limit, as the organization's security record.
- Billing records are kept for as long as tax and accounting law requires.
- Audit and publication history has no fixed retention period yet, so none is claimed here. If you need to know how long a specific record is kept, write to privacy@krono.io and you will get a straight answer.
Your choices
You can ask for a copy of the personal data held about you, ask for it to be corrected, or ask for your account to be deleted. Requests go to privacy@krono.io. An account can also be deleted in Kröno.io itself, as the data deletion page explains. Content you created on behalf of your organization belongs to that organization and is not removed when your own account is deleted.