Privacy Policy

Inceptix LLC, a Wyoming limited liability company doing business as OmniFlag (“the Company”), is the data controller for personal data processed through omniflag.app. Contact for anything in this policy: cyrus@omniflag.app.

• Account data: your email address and authentication identifiers (password hash or Google account identifier). Passwords are handled by the authentication provider and never visible to the Company.
• Intake answers: what you provide in the planning wizard, such as citizenships, current tax residency, city, motivations, income and savings bands, family situation, constraints, and free-text context. Bands are used instead of exact figures by design.
• Newsletter data: if you subscribe to the rule-change newsletter, your email address and whether you have confirmed or unsubscribed. Subscribing is separate from having an account, and every newsletter email carries an unsubscribe link.
• Payment data: if you buy a verified plan or an exit plan, Stripe processes the payment. The Company receives a record that the payment happened, its amount, and Stripe’s identifiers for it. Your card number is given directly to Stripe and never reaches the Company.
• Technical data: standard server logs (IP address, user agent, timestamps) kept by the hosting providers for security and operations.
• Session recordings: a record of how you move through the pages, covering clicks, scrolling, and where you pause. Every piece of text and every input is replaced with a blank block in your browser before anything is sent, so a recording shows the shape of the page and what you did on it, never what you read or typed. Your intake answers, your name, and your email address are not in it.
• Advertising click data: if you arrive from a Google ad, the link carries Google’s own click identifier. Google’s tag reads it in your browser so that a later submission can be attributed to that ad. It is not stored in the Company’s database.

Intake answers are used for one purpose: producing your free report and, if you buy one, preparing and reviewing your verified plan. Your account email receives what you asked for and messages about your submission. A notification with your submission summary goes to the founder. Intake answers are never used for the newsletter and are never sent to an advertising network. Personal data is never sold.

While the site is running paid search ads, the fact that a submission happened is reported to Google as a count, with no answers attached. Your citizenship answer decides whether that count happens at all, because submissions from US persons are excluded from advertising measurement. That decision is made in your browser and the answer itself is never sent.

A newsletter subscription is used only to send the newsletter. Subscribing does not add you to anything else, and unsubscribing does not affect your account or your report.

The free report involves no language model at all. It is assembled directly from the Company’s own researched material, so nothing you submit is sent to a model to produce it.

Preparing a verified plan does use a large language model, with two protections. First, personal identifiers and free-text fields are stripped before any model call: your email and open-ended notes are never sent to the model. Second, the model provider operates under a zero-data-retention agreement, meaning submitted content is not stored by the provider or used to train models.

Session recordings are reviewed automatically, to find the places where people get stuck. That review is performed by a Google model through the analytics provider. Because a recording is masked in your browser before it is sent, what reaches the model is a wireframe of clicks, pauses, and scrolling with no readable content in it.

The Company uses a small set of service providers to run the Service, each processing data only on the Company’s instructions:

• Supabase (database and authentication hosting, United States)
• Vercel (web hosting, United States)
• Resend (transactional email and the newsletter, United States)
• Stripe (payment processing, United States): used only if you buy something. Card details go to Stripe directly and are never held by the Company.
• Anthropic (language model processing under zero retention, United States)
• Google (United States): used if you choose Google sign-in, while the site is running paid search ads for advertising measurement, and for the automated review of masked session recordings described in section 4. The advertising tag reports that a submission happened and reads Google’s own ad-click identifier from the link you arrived on. It is never given your name, your email, or any intake answer.
• PostHog (product analytics and session recording, United States): page views, product events such as which step of the intake was completed, and the masked recordings described above. Neither the events nor the recordings include your name, email, or intake answers.

If you are outside the United States, your data is transferred to and processed in the United States by the providers above.

Account data and intake answers are kept while your account exists. Email cyrus@omniflag.app from your account address to request a copy of your data or deletion of your account and submissions; deletion is completed within 30 days, except records the Company must keep to meet legal obligations, including sanctions-screening records and records of payments, which tax and accounting rules require the Company to retain.

The site sets cookies for three purposes. The first is keeping you signed in (authentication session). The second is advertising measurement: while the site is running paid search ads, Google’s tag sets a cookie so Google can tell that a visit which followed one of its ads later completed the planning wizard. What Google receives is that a submission happened. It is not given your name, your email, or any answer you gave.

The third is traffic measurement: while it is enabled, Google Analytics sets cookies to count visits, tell returning browsers from new ones, and show which pages are read and whether the planning wizard gets finished. What Google receives is how this site is used. It is not given your name, your email, or any answer you gave.

Wizard progress before you sign in is stored in your own browser’s local storage and never leaves your device until you submit. Product analytics and session recording use local storage rather than cookies, and do not track you across other sites.

If you are reading this in the United Kingdom or the European Economic Area, neither the advertising cookie nor the analytics cookies are set at all. The site tells Google to withhold them for those regions before any Google tag loads, and it does not ask you to agree to anything to make that happen.

Everywhere else, you can block the advertising and analytics cookies with any standard ad or tracker blocker, or by refusing third-party cookies in your browser. Nothing on this site stops working if you do.

Material changes to this policy are posted on this page with an updated date. If a change meaningfully affects how existing data is used, account holders are notified by email first.