Privacy

What We Store

AION collects and stores the minimum information required to provide and secure the service:

• Account identifiers: email address and passkey credential used to authenticate your account
• Device-linked access state: passkey registration is device-linked; we store the passkey's credential identifier (and its public key, where your browser provides it). No biometric data is captured: your fingerprint, face or PIN is checked by your own device and never sent to us
• API key and recovery key: your API key is shown to you once, when you reveal it, together with a recovery key that is also shown once. We store only a one-way hash (SHA-256) of each, so we cannot show either again. The recovery key is 32 random bytes; it lets you replace your API key without your passkey. Recovery never uses email: we do not send keys or recovery keys by email and do not recover them by email. If you lose both your API key and your recovery key, there is no recovery, and you generate a new key
• Subscription status: active plan, billing cycle state, and Razorpay subscription identifier, managed in PostgreSQL
• Usage metadata: API request counts, rate limit counters, and model access logs used for abuse prevention and plan enforcement, including a one-way hash of each query, linked to your account for quota metering and billing
• Registration attempts: when you try to register an account we record the time of the attempt and a keyed one-way hash of your IP address, so that attempts can be limited to five per address per 24 hours. The address itself is not stored in that record, and the hash cannot be reversed to recover it. A successful registration is stored separately with the account it creates
• Free-plan signup: when you start the free plan, our page creates a random device pass, keeps it in your browser's local storage (you can delete it from your browser settings at any time) and sends it with the request. We record a keyed one-way hash of that pass together with a keyed one-way hash of your IP address, and use them only to limit free keys: one per device, one per device-and-network pair, and two per network, in any 30 days. Because many people can share one network address, a shared address can reach its limit before you sign up. Neither the pass nor the address is stored in that record, and neither hash can be reversed to recover them
• Queries the engine cannot classify: if a headline you send through the API cannot be classified, or has to be resolved through a fallback, we retain the headline text so that we can improve the engine, including by training its classifier. These records are linked to your API key by a one-way hash. The engine's own quality log records only a truncated one-way hash of such a headline, the model's prediction and confidence, a timestamp and the source label you supply; it holds no text and no account identifier. We do not store the text of any other API query.
• Terms of Service acceptance: when you check the acknowledgment box at checkout, we record your email, the exact version of the Terms of Service you accepted, the time, your IP address in full (not hashed, unlike the other IP uses on this page: a hash cannot later be shown as evidence of which address accepted, which is the only reason this record is kept this way), your browser's user agent, and the time zone and UTC offset your browser reported. This is processed under the Digital Personal Data Protection Act, 2023 for the specific, stated purpose of evidencing your consent to those terms, kept for as long as you hold an account with us plus the period needed to meet a legal claim, and for no other purpose.

What We Do Not Do

• We do not build personal financial profiles. AION does not store or infer information about your trading activity, portfolio, or investment history.
• We do not sell, share, or rent account data to third parties for marketing or analytics purposes.
• We do not sell or share your API queries. Other than the retained unclassified headlines described above, query data is kept only as a one-way hash, for rate limiting, quota metering, billing, access control and quality monitoring.
• We do not use third-party behavioral tracking scripts (e.g., Meta Pixel, Google Analytics behavioral tracking) on authenticated surfaces.

Platform State Use

The data we collect is used for three purposes only:

• Access control: verifying that the right account can reach the right model features
• Accountability: maintaining an audit trail of API access for security and compliance
• Service integrity: rate limiting, abuse prevention, and billing state management

Data Retention

Account data is retained for the duration of your account. API access logs are retained for 90 days for security purposes; registration-attempt records (a timestamp and a one-way hash) and free-plan signup records (a pair of one-way hashes) are retained for 30 days; this period does not apply to the unclassified headlines described above, which are not deleted automatically. Subscription records are retained as required for billing and tax compliance. Terms of Service acceptance records are retained for the duration of your account plus the period needed to meet a legal claim, consistent with their sole purpose of evidencing consent.

To request deletion of your account and associated data, contact us at [email protected]. Deletion requests are processed within 30 days.

Open-Source Package Users

The AION Indian Market Calendar Python package operates entirely offline after installation. No network requests are made to AION servers during normal usage. No usage data is collected from package installations or queries.

Public Demo

The public demo opens with a free demo key. The Highest Risk Companies list and the two interactive tools all need that key (since 7 October 2026). Reading the list does not use up a lookup.

We issue the demo key against an email address. This is the only point at which the demo collects personal data, and it is collected with your explicit consent: you tick a box saying we may contact you, and the request is refused without it. We store the address to issue the key, to keep to one key per address, and to contact you about AION. The key is shown to you on the page; it is not sent by email. We do not sell it, do not share it with third parties, and do not combine it with any tracking. The key itself is stored only as a one-way hash. Ask us at [email protected] and we will delete your address.

There is still no cookie and no password. Beyond the address you gave us, we do not know who you are.

The demo allows two company lookups and three analyses per browser, every 7 days, and everyone on one network together at most twenty lookups and thirty analyses in 7 days. A request is refused when either is used up. Only a request that returns a result counts. The Highest Risk Companies list needs the demo key but is unmetered; reading it never counts against your allowance.

Both limits are enforced on our server. That requires recognising a returning browser and a returning network, which we do in the least identifying way available to us:

• Keyed one-way hashes of your device pass and your IP address, kept for 7 days. We compute them with a secret key held on our server and store them with the two counts. A scheduled job deletes each record 7 days after it is created. Your IP address is never written to disk, neither hash can be reversed without that key, and neither is ever written to any log. The network ceiling is a limit on a network, not a record of a person.
• Your browser also generates a random session token when the page loads, held in memory only. Combined with your IP address and hashed the same truncated, one-way way, it is kept for 24 hours as a per-visit counter and then deleted.
• One value is written to your browser's local storage: a device pass. It is a random identifier this page generates; its keyed hash is what the per-browser count is kept against. It is not derived from your device: no canvas rendering, no WebGL, no font or hardware enumeration, nothing biometric. You can delete it at any time from your browser's site-data settings.
• No cookies and no session storage are used.

Passkey option. If you enrol a passkey on the demo page, the allowance rises to five company lookups and ten analyses, counted against that passkey instead of your network. A passkey is checked by your own phone or computer: no biometric data is captured, and your fingerprint, face or PIN never reaches us. What we store is the passkey's credential identifier, its public key and a signature counter (all three are needed to check the passkey next time), the two usage counts, and when it was created and last used. Nothing else: no email, no name, no IP address and no device identifier, apart from the 7-day network hash described next. While you are signed in, the page keeps a signed sign-in token in local storage for up to 12 hours. To stop passkeys being created in bulk, each network can enrol five in any 7 days, counted against a keyed hash of the IP address that expires after 7 days. Daily usage records for a passkey carry that hash for 7 days; after that the hash is deleted and only the counts remain. Because the record is not linked to your name, email or address, we cannot pick yours out on request; deleting the passkey from your own device makes it unusable.

We do not fingerprint your device. No canvas rendering, no WebGL probing, no font or hardware enumeration, no cross-site identifier. This was a deliberate choice: fingerprinting would give us stronger abuse control at the cost of tracking people who have not asked to be tracked, and we are not willing to make that trade for a demo.

Demo requests are recorded in an access log containing a timestamp, the endpoint, the truncated caller hash, a hashed user agent, and the response status. The usage record for each demo request also includes a one-way hash of the submitted text. It contains no IP address, no user agent string, and no request content. Text you submit to the Market Intelligence demo is analysed and returned; it is not stored and is not used to train or update any model.

Counting who tried a demo. The Lithuanian tax calculator runs entirely in your browser, so we cannot see that you used it. When you change a field or ask for the report, the page sends one request telling us which page it was, and nothing else. It carries no figure you entered and no identifier. To avoid counting the same device twice in a day, the server derives a truncated one-way hash from your network address and browser string; the hash and the daily key used to make it are both discarded when the day ends, so the record that remains is a count and a date. Your network address is never written down. The totals are published at /api/public/demo-usage, and the page-view figures shown beside them come from our content delivery network, not from anything stored here.

Know Your Rights pilot

The Know Your Rights pilot works differently in one respect, and it is the respect that matters most, so it is stated first: the questions you ask it are stored, and so are the answers you get. That is the entire purpose of the pilot. We cannot find out which legal questions this system answers badly without keeping the ones it answered.

What is kept for each question: the question text, the answer text, the language it was detected as, the identifiers of the legal sections it drew on, whether it declined to answer, and a timestamp. If you leave feedback, the rating and any comment are kept as a separate record linked to that question.

Your email (from 21 October 2026). To try the pilot you give an email address and confirm two statements: that the pilot gives legal information, not legal advice, and that you have read how your email and questions are handled. We keep the email with the time you confirmed, the IP address you confirmed from, the version of the text you confirmed, and three counts: how many questions you asked, how many were answered and how many it declined. We use these to know how many people try the pilot and how often it works, and to record your confirmation. The email is kept by the website, apart from the question log: the service that answers never receives it, and the questions we keep cannot be linked to it. It is not added to any mailing list and not shared. Your browser keeps a random access code so the same device does not ask again. The email record is deleted 12 months after your last question, or earlier if you write to [email protected].

What the question log does not keep: anything that identifies you. No email, no IP address, no user agent, no session token, no cookie, no device fingerprint. Rate limiting uses the per-visit IP-and-session hash described above, expiring after 24 hours (the 7-day network hash is not used for the pilot); the service that answers your question and writes the log is never given your IP address at all, so it has no way to record one.

Because the questions are read by us, please do not type anything that identifies you or anyone else: no names, phone numbers, case numbers or addresses. Describe the situation, not the people. The pilot page says the same thing above the box.

This log is used to find and fix failures in the pilot. It is not sold, not shared with third parties, and not used to build a profile of anyone: there is nothing in it to build a profile from. The pilot closes once it has gathered the feedback it was opened to collect.

Know Your Rights provides legal information, never legal advice, and has not been reviewed by practising advocates. It is not a substitute for a qualified lawyer or a legal aid service.

Newsletter

Sign-up for product-update emails is temporarily unavailable while we repair the confirmation email. No email address is collected for the newsletter while sign-up is paused. The rest of this section describes how the newsletter works when sign-up is open.

If you subscribe to product updates, we store your email address and the date you subscribed. We use it to send occasional product announcements. We do not sell it, do not share it, and you can unsubscribe at any time using the one-click link in every email, which deletes your address from our database rather than marking it as inactive. You are added only after you click the link in a confirmation email; a sign-up that is not confirmed within 48 hours is deleted. To limit repeated sign-ups, a sign-up also stores a keyed one-way hash of your IP address (made with a secret key and that day's date, so it cannot be linked across days). This hash is used only for that limit: it is erased as soon as you confirm, and removed with an unconfirmed sign-up after 48 hours. Nothing about your browser is stored. The raw IP address is never stored.

Launch waitlist: AION Prahari and AION Sargas

The pages for AION Prahari (India) and AION Sargas (Baltic region) let you ask for one email when the app is available on Google Play. The app is not available yet.

What we keep. Your email address, which of the two products you asked about, the version of the notice you agreed to, when you signed up, when we sent the confirmation email and when you confirmed. The confirmation and leave links in the email contain random codes; we keep only a one-way hash of each. We do not keep your name, your IP address or anything about your browser or device.

No IP tracking. Your IP address is not stored with your sign-up and is not written to our security log for these pages. To stop one network sending many sign-ups, the server keeps a keyed one-way hash of the address in its memory only, never on disk, and uses it only to count sign-ups from that network in the past hour. The key is random and is replaced whenever the server restarts.

What we use it for. Only to send the confirmation email and then one email when the app is available. We do not use it for the newsletter or for anything else, we do not sell it and we do not share it. Our email is hosted by Tuta, based in Germany, which carries these emails.

How long we keep it. You are on the list only after you click the link in the confirmation email. If you do not confirm within 48 hours, your sign-up is deleted. A copy of your address kept with the queued confirmation email is deleted when its link expires, 48 hours after it was queued. If you confirm, we keep your address until we have sent the launch email, and then delete it. Our encrypted database backups are kept for 14 days, so a deleted address can remain in a backup for up to 14 days before that backup is deleted.

Leaving and deletion. Every email we send about the waitlist has a link to leave the list. Leaving deletes your address from the list and from our email queue; it is not kept as inactive. You can also ask us to delete it, or to tell you what we hold, by writing to [email protected]. We process these requests within 30 days. Under the Digital Personal Data Protection Act, 2023 we rely on your consent, which you give by ticking the box on the page, and you can withdraw it at any time by leaving the list.

If you are in the European Union or the European Economic Area, including Lithuania, Latvia and Estonia. The General Data Protection Regulation (GDPR) applies to your sign-up. The controller is AION Analytics, India, contact [email protected]. We process your email address on the basis of your consent (Article 6(1)(a) GDPR). You can withdraw consent at any time by leaving the list; this does not affect the emails already sent. You have the right to access your data, to have it corrected or deleted, to restrict its processing, to receive it in a portable form and to object, by writing to the address above; we answer within one month. Your data is stored on our servers in India, which the European Commission has not recognised as giving an adequate level of data protection; we apply the safeguards on this page to it. You have the right to complain to the data protection authority of your country; in Lithuania this is the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija).

Security logs

Our servers keep a security log of the requests they answer: the time, the address requested without anything after the question mark, and the response status. For all requests except those of the public demo, the Know Your Rights pilot, newsletter sign-up and the launch waitlist, it also records the IP address the request came from. The log with IP addresses is encrypted, can be opened only by AION's administrator, and is kept for one year for legal and regulatory audits, then deleted. Our everyday operational logs contain no IP addresses.

Website Analytics

AION uses Cloudflare Web Analytics to understand aggregate website usage, including page views, estimated visits, referral sources and performance information.

Cloudflare Web Analytics does not use analytics cookies or browser fingerprinting to identify visitors. Analytics information is processed by Cloudflare as our infrastructure and analytics provider; it is not collected by a self-hosted AION analytics service.

AION uses these aggregate reports to understand website performance and improve its public information and services. We do not use these analytics reports to identify individual anonymous visitors or reconstruct their personal browsing histories.

Analytics collection is excluded from authenticated account, access and credential-management pages. Separate security and operational records required to provide our services are described elsewhere in this policy.

Some links that AION shares on social media pass through an address of the form aionanalytics.in/go/…, which sends you on to the page and adds one to a daily count for that link. On the subscription pages, the first time you start filling in the form in a browser tab, a similar daily count is increased by one. These counts are plain numbers per day: no IP address, cookie, browser details or other identifier is stored with them.

Proprietary Methodology

AION does not publish the internal methodology behind its models and platforms, including retrieval architecture, feature derivation, evaluation methodology and governance layers. These details are withheld pending intellectual property protection.

Public model and platform pages describe what a system does and who it serves; they do not describe how it is built. Research partners and institutional collaborators may request a technical briefing under confidentiality: [email protected]

Changes to This Policy

If we make material changes to how we collect or use data, we will update this page and notify active subscribers by email. Continued use of AION services after notification constitutes acceptance of the updated policy.

Contact

For privacy questions or data deletion requests: [email protected]