Privacy policy

This policy covers two things: what happens when you visit cernia.ai, and what happens to the data of a business that uses the Cernia service. It is written to be read, not skimmed past.

• Who we are
• Visitors to this site
• Client data in the service
• What is never collected
• Service providers
• Retention
• Your rights
• Children
• Changes
• Contact

Who we are

Cernia LLC, a Wyoming limited liability company, operates cernia.ai and the Cernia service. For this policy, "Cernia", "we" and "us" mean that company. Questions go to hello@cernia.ai.

Visitors to this site

Server logs. The site is served by Cloudflare, which records standard request logs (IP address, user agent, the page requested, time) for security and performance. Cernia does not combine these with anything else.

Analytics. Cernia uses Cloudflare Web Analytics, which counts page views without cookies and without storing your IP address. Cernia also uses Google Analytics 4 with IP anonymization to understand which pages are read; Google sets a first-party cookie for this. You can block it with a browser setting or an extension and the site works the same.

The contact form. What you type into the contact form (your name, email address, company, website and message) is delivered to Cernia's mailbox by Web3Forms and used only to reply to you. It is not added to a marketing list.

Email. If you write to hello@cernia.ai or security@cernia.ai, the message is kept as ordinary business correspondence.

The film and the example report. Both are served from this site. No third-party video or document host is involved.

Client data in the service

A business that uses Cernia connects its advertising, analytics, attribution, call-tracking, lifecycle and commerce platforms. What Cernia does with that data is governed by the service agreement with that business; this section describes it so the people whose data it touches can see it too.

Account data. Names, work email addresses and roles of the people the business invites, their sign-in records, and their Slack identities where the Slack app is installed. Sign-in is handled by WorkOS.

Platform data. Campaign, ad, keyword, spend, click, conversion and revenue reporting from each connected platform, read live when a question is asked or a procedure runs. Cernia does not keep a standing copy. What is kept is declared on the security page: dashboard series, recurring-report figures, plans and read-backs, and the audit log.

Credentials. Encrypted at rest, decrypted only inside the request that uses them, never logged. See Security.

Questions and answers. The questions people ask Cernia, the answers, the reports and the plans are kept for the business that asked them, so the service can remember what it decided and why.

What is never collected

Cernia never reads a client's customer records: no customer names, email addresses, phone numbers, postal addresses, order histories tied to a person, or anything else that identifies a client's customers. Connectors request aggregate reporting fields, not records, and every report, chart and message passes a personal-data scan before a person sees it. Cernia also does not read the contents of a client's email, documents or messages beyond the Slack channels its app is explicitly bound to.

Service providers

Cernia uses a small number of providers to run the service. Each handles data only to provide its function and under its own terms:

• Cloudflare: hosting, delivery, DNS, email routing and web analytics.
• WorkOS: sign-in (email link, Google, Microsoft, SAML).
• A managed PostgreSQL database: the declared data above, isolated per organization.
• Anthropic and OpenAI: the models that produce answers and drafts, used under their API terms, which exclude data from model training. A client may run on its own key instead.
• Slack: where a client installs the Cernia app.
• Web3Forms: delivery of this site's contact form.
• Google Analytics: only if enabled, as stated above.

Cernia does not sell personal data and does not share it with anyone for their own marketing.

Retention

Contact-form messages and email are kept as long as the conversation is live and for a reasonable period after. Client account data is kept for the life of the engagement and removed within thirty days of its end, except the audit log and plan records, which the client may ask to receive first. Platform data that was read live is not retained at all beyond the declared series and figures. Server logs are kept by Cloudflare for its standard period.

Your rights

Wherever you are, you can ask what Cernia holds about you, ask for it to be corrected or deleted, and ask for a copy. People in the European Economic Area, the United Kingdom, California and other places with privacy statutes have specific rights under those laws, and Cernia honours them without asking you to cite the statute. Write to hello@cernia.ai; requests are answered within thirty days. If you are a customer of a Cernia client and your question concerns that client's data, Cernia will pass it to them, since it does not hold your records.

Children

cernia.ai and the Cernia service are for businesses. They are not directed at anyone under eighteen, and Cernia does not knowingly collect data from children.

Changes

When this policy changes, the date at the top changes with it and material changes are announced to clients directly. Earlier versions are available on request.

Contact

Cernia LLC, hello@cernia.ai. Security matters: security@cernia.ai.