Privacy

Your data

The studio's engine runs on your machine. No upload path exists in the code; the browser's own security policy on the studio origin additionally refuses any network request to anywhere but the studio itself, and an automated test fails our build if one appears. Your files, tables, mappings, dashboards, and every number derived from them stay with you.

The identity service stores

Email address, optional display name, sign-in and sign-out events, licence issuance and attachment, tier changes, session records. That is the whole list; adding to it is a revision of our identity plan, reviewed like the original.

The identity service never stores

Event data, object ids, file names, file contents, mapping files, table or column names, row counts, dollar figures, dashboards, or anything else derived from a loaded file. No request the studio makes after sign-in carries content derived from your data — the door authenticates a person, then gets out of the way.

Counting visits

We count how many times each page is asked for. The counting happens on our server, from the request your browser already made — there is no analytics script on any page, no cookie, no pixel, no fingerprint, and nothing to opt out of because nothing about you is collected. An ad blocker has nothing to block.

What is kept is a set of running totals, one per day, per page, per channel — a row that reads “on 27 August, the pricing page was asked for 41 times, 12 of them from a search engine, on a desktop”. There is no visitor identifier of any kind, hashed or otherwise, and no time recorded finer than the day. So we cannot tell you apart from anyone else, cannot follow you between pages, and cannot join a visit to an account — not as a policy we keep, but because neither side holds a key the other could be matched on. Your browser’s address and user agent are used to decide which total to add one to, and are then discarded; neither is written down.

What this costs us, since it is the honest half: we do not know how many people visit, only how many visits there were, and we know nothing at all about what anyone does inside the studio.

Retention, in numbers

Sign-in links and codes work once and expire after 15 minutes; their records are deleted within a day of expiring. Sessions last 30 days of rolling use with a hard maximum of 90 days from sign-in; expired session records are deleted within 7 days. Your IP address is never stored raw — a one-way hash is kept briefly for rate limiting and deleted within about two hours. Account details (your address, any display name, and the sign-in history above) are kept until you ask us to delete them. The daily page totals are kept indefinitely; there is nothing in them to delete, because there is nothing in them about you.

Deletion

Mail support@objectiveintelligence.ai from your sign-in address and ask. We hard-delete your personal values — address, display name, licence text, side records — and what remains is anonymous shape: an account existed, signed in, and was deleted. Licence files you hold keep verifying offline; they are yours.

No joining, no third parties

There is no analytics or telemetry in the product — nothing in the studio reports what you load, map, or look at, and the page counts described above stop at the front door. Those counts cannot be joined to your account: no shared key exists, and no build may create one. If an opt-in product-telemetry contract ever ships, it is held to the same rule. The marketing pages you are reading load nothing from third parties; fonts are served from this site, and there is no advertising, retargeting, or measurement tag on any page — including on pages we pay to send people to. We use Netlify to host, Neon to store the identity list above and the page counts, and Resend to deliver sign-in mail — each sees only what that job requires.