Privacy

What this page describes

This page explains what data Cirtonia Business handles today, in Beta, who can see it, and which cookies the application uses.

It is not the formal privacy notice: no document identifying the data controller or its address has been published yet. When that notice exists, Cirtonia will publish it as such. In the meantime, what the platform does is described here.

The purchase conditions live in a separate, versioned document, accepted before reserving inventory and starting payment.

What data the platform handles

The platform keeps what it needs to operate the service:

• Account: your name, your avatar, your email and its verification state, the method you sign in with, and your membership of an organization.
• Organization: the business details captured at sign-up, memberships, and invitations sent and accepted.
• Preferences: language, theme, notification preferences, and the two optional privacy preferences you can change in Settings.
• Campaigns: quotes, contracted periods and slots, the catalogue version and prices frozen at purchase, campaign states, and operation requests with their reason.
• Creatives: the files you upload and their review history, including the reason for a rejection.
• Payments: the internal record of each transaction, the Stripe receipt, and the history of pending, confirmed and failed refunds.
• Evidence: the audio witnesses of each emission, with their before, ad and after segments.
• Records: the acceptance of each legal document version — exact version, organization, person, date and time — and the decisions on operation requests with their reason and date.
• Vybe conversations: your chat history with the assistant, isolated per organization.

Payment data

Payment is processed with Stripe. Cirtonia neither receives nor stores card data.

What stays on the platform is the internal record of the transaction and, once the provider makes it available, the Stripe receipt for the charge. That receipt is not a fiscal invoice: issuing a CFDI is not included in this Beta.

Who can see your data

Your campaigns, quotes, creatives, payments, evidence and reports belong to your organization and are not visible to other organizations on the platform. The catalogue, by contrast, is the same for the whole platform and Cirtonia administers it.

Cirtonia accesses your organization's data to operate the service: moderating creatives, scheduling, recording emissions, resolving requests and providing support.

Files are not public: they are delivered through signed, temporary links, authorized per object and for the owning organization.

Inside your organization, what is in the account is seen by the people your organization gives access to. Withdrawing that access is your organization's decision.

Cookies the application uses

The application uses its own cookies to work. It uses no advertising or third-party tracking cookies, which is why it shows no cookie consent banner.

Cookies needed to use the application:

• Your account session, managed by the authentication provider: without it you cannot stay signed in.
• cirtonia.activeOrgId: the organization you are working with, so data from different organizations is never mixed.
• NEXT_LOCALE: the language the interface is served in.
• cirtonia_onboarding: your progress through sign-up while you complete it.

Interface preference cookies, which you can clear from your browser without losing access:

• cirtonia.sidebar.collapsed: whether you left the sidebar collapsed.
• cirtonia.onboardingDismissed: whether you dismissed the first-steps list.
• cirtonia.vybeWelcomeSeen: whether you have already seen the Vybe welcome.

None of these cookies is shared with third parties for advertising, and none builds a profile of you outside Cirtonia.

What you can change yourself

In Settings you can turn two optional privacy preferences on or off: non-essential product analytics and interface personalization. Both are off by default and are stored as a preference of your account.

You can also choose whether to receive campaign updates and product updates by email.

What cannot be turned off are the essential security, invitation and account-recovery emails, because they are what protect access.

The Vybe assistant

Vybe is the platform's assistant and runs on a language model from an external provider. It only reads: it looks up available inventory, your campaigns, your payments and your witnesses, always inside your organization.

Vybe does not buy, schedule, pay, refund or modify a campaign, and it invents neither audience nor delivery. When a figure does not exist, it says so.

What is sent to the assistant is your messages and the data those read-only lookups return. Your conversation history stays isolated per organization.

Third parties involved

To operate, the platform relies on external providers:

• Stripe processes payments and refunds.
• A cloud storage provider holds creatives and witnesses, delivered through signed, temporary links.
• An authentication and database provider backs accounts, sessions and platform data.
• A transactional email provider sends notices and account security emails.
• A language model provider serves the conversations with Vybe.

No published document sets a formal list of sub-processors or a downloadable data processing agreement today. When they exist, they will be published as such.

How information is kept

No published document sets a retention period or an automatic deletion today, and the platform does not yet offer an on-request data export or deletion feature. This is what does happen:

• A campaign's history — what was contracted, scheduled and aired, the payments and refunds, and the witnesses — is kept as the record of that campaign.
• What has already aired is neither deleted nor rewritten: a confirmed operational cancellation releases for resale only future traditional reservations that have not aired.
• The acceptance of each legal document version is kept as evidence of the purchase.

If you need to raise something about your data, use the routes the platform offers today; they are described in Help.

Changes to this page

This page describes the platform as it works today and is updated when the product changes. Unlike the Purchase conditions, it is not a versioned document accepted before buying.