Privacy Policy

Effective date: October 5, 2026

AINativeLang Inc. (“we,” “us,” or “our”) operates ArmaraOS and related AI inference services through armaraos.com and affiliated properties. “Armara” and “ArmaraOS” are product names for our software and hosted services (collectively, the “Services”). We respect your privacy and are committed to protecting personal information we collect in connection with the Services. This Privacy Policy explains what we collect, why we collect it, how we use and share it, and the choices and rights available to you.

This Policy works together with our Terms of Service, which govern your use of the Services. By accessing or using the Services, you acknowledge this Policy. If you do not agree, do not use the Services.

1. Scope

This Policy applies to personal information we process when you:

• Visit or interact with our websites (including armaraos.com and related domains)
• Create or use an ArmaraOS account
• Use hosted chat, API, or inference features we provide
• Download, install, or run ArmaraOS when it communicates with our services
• Contact support, participate in affiliates/referrals, or otherwise interact with us

ArmaraOS local-first use. When you run ArmaraOS entirely on your own machine without connecting to our hosted services, most processing occurs locally on your device. Local-only use is governed by this Policy only when you connect to our hosted services. If ArmaraOS is configured to send anonymous telemetry or connect to hosted inference, those flows are covered by this Policy.

Bring-your-own-key inference. If you supply third-party API keys (for example, keys you configure in ArmaraOS), those providers process data under their own policies. We do not control and are not responsible for third-party model providers you choose to use directly.

2. Personal information we collect

We collect personal information in three broad categories: information you provide, information collected automatically, and information from third parties.

2a. Information you provide

• Account data — email address, display name, password (stored in hashed form via our authentication provider), and profile preferences
• Billing data — subscription tier, transaction identifiers, and billing metadata. Payment card details are collected and processed directly by Stripe; we do not store full card numbers on our servers
• Support communications — messages, attachments, and contact details you send to us
• User content — prompts, messages, files, agent configurations, and other content you submit through hosted Services (for example, web chat or API requests routed through our infrastructure)
• Games Studio content — game prompts, brand-kit details you enter (such as names, logos, tickers, or lore), the games and versions we generate, titles, descriptions, publishing settings, and the websites you allow to embed your games
• Linked Solana wallets — if you link a wallet for $ARMARA holder builds, its public address and when you linked it. We check a signed message to confirm you control the wallet, then discard the signature. We never receive your private keys or seed phrase
• Referral and affiliate data — referral codes you use or share, and related attribution metadata

2b. Information collected automatically

• Device and usage data — browser type, operating system, app version, language, pages viewed, feature interactions, timestamps, and diagnostic events
• Log and security data — IP address, approximate location derived from IP, browser and device metadata, timestamps, rate-limit counters, authentication events (successful sign-in and sign-out), and error logs used for security, abuse prevention, and reliability. We do not collect hardware MAC addresses from browsers (they are not available to websites). Chat message contents are not included in these security logs.
• Inference and quota data — API key identifiers (not full secrets after initial display), message counts, token or usage quotas, and service performance metrics
• Game data — a record of every game build (time, plan allowance or pack used), build pack purchases, your acceptance of the Games Studio terms and any game ownership transfers you confirm (with time, IP address, and browser), play counts, your best score and cloud saves from games you play while signed in, and error messages from the automatic test run of a new build in your browser, which we use to repair it. A game you play while signed in can read your display name to show it in the game; games run in a sandbox that blocks them from contacting any server
• Cookie and local storage data — session cookies, authentication tokens, referral cookies, and similar technologies described in Section 6

2c. Information from third parties

• Public blockchain data — for wallets you link, your $ARMARA balance, read from the Solana blockchain several times a day through a Solana network provider, and a daily record of the lowest balance, used to work out your holder builds
• Authentication providers — if you sign in with OAuth (for example, Google), we receive basic profile information permitted by your provider settings
• Payment processors — Stripe and CopperX provide transaction status, customer identifiers, and subscription lifecycle events

We do not intentionally collect sensitive categories of personal information (such as health data, government ID numbers, or financial account credentials beyond what payment processors handle) unless you voluntarily submit them in user content. Do not submit sensitive personal information or third-party confidential data through the Services unless you have a lawful basis and appropriate safeguards.

3. How we use personal information

We use personal information to:

• Provide, operate, maintain, and improve the Services
• Authenticate users, manage accounts, and enforce usage quotas
• Process subscriptions, payments, referrals, and affiliate commissions
• Route, execute, and monitor hosted AI inference requests you initiate
• Detect, prevent, and respond to fraud, abuse, security incidents, and violations of our terms
• Communicate with you about the Services, updates, billing, and support
• Analyze product performance and reliability through anonymous telemetry (see Section 5)
• Comply with legal obligations and protect the rights, safety, and property of AINativeLang Inc., our users, employees, contractors, and the public
• Develop new features, conduct internal research, and improve model routing and system quality

We do not sell personal information and we do not share personal information for cross-context behavioral advertising. Where required by law, we provide mechanisms to opt out of certain processing as described in Sections 9 and 10.

Model training. We do not use your hosted inference prompts or outputs to train third-party foundation models. We may use aggregated or de-identified telemetry and feedback to improve our own software, routing, safety filters, and reliability. If we ever introduce optional training-related uses of user content, we will provide clear notice and choice before doing so.

4. AI services and inference data

When you use hosted AI features, we process the content you submit (prompts, context, attachments, and generated outputs) to deliver the requested functionality, enforce plan limits, maintain logs for security and debugging, and improve service quality.

• AI outputs may be inaccurate, incomplete, or inappropriate. Do not rely on outputs as professional, legal, medical, financial, or safety-critical advice
• You are responsible for reviewing outputs before use and for ensuring your inputs comply with our Terms of Service and applicable law
• We may use automated systems to detect abuse, spam, malware patterns, or policy violations. Flagged content may be retained longer for investigation even if you delete an account, as permitted by law
• API keys and inference credentials are encrypted at rest. Full API keys are shown only at creation or rotation; thereafter we display masked values

4A. Google user data (Gmail connector)

If you choose to connect Gmail in chat, you authorize ArmaraOS through Google to read your mail and create drafts. Connecting is optional, and nothing below happens unless you connect and then act in the Gmail panel.

• What we access — when you open your inbox in the panel, the sender, subject, date, and a short preview of your 15 newest inbox threads; when you pick a thread, the text of the messages in that one thread; your Gmail address, to show which account is connected; and, when you press Save to Gmail drafts, the draft you reviewed is created in your Gmail Drafts folder. We never send email on your behalf, and the permissions we request cannot send mail
• How we use it — only to show your inbox and threads to you, and to send the thread you pick to the AI model for the request you make in that chat (for example, to summarize it or draft a reply), processed as described in Section 4
• Storage — your Google refresh token is stored encrypted at rest with AES-256-GCM. The Gmail connector does not store message text itself; thread text is kept only where you put it, as part of the chat messages or research reports you create, and is deleted with them. An activity log lists what Armara did with your Gmail (listed, read, drafted, connected, disconnected) with a thread subject or a count — never message bodies
• Sharing — we do not sell Google user data, do not use it for advertising, and do not use it to train or improve AI models. We transfer it only to the service providers needed to deliver the feature you asked for, to comply with law, or as part of a business transfer described in Section 7b. No one at Armara reads it unless you ask us to (for example, in a support request), it is needed for security or abuse investigation, or the law requires it
• Revoking access — press Disconnect in the Gmail panel at any time. We delete the stored token and revoke it at Google. You can also remove access from your Google Account at myaccount.google.com/permissions

Armara's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. Product analytics and telemetry (PostHog)

We use PostHog (PostHog, Inc.) to collect anonymous product analytics and telemetry across our website, ArmaraOS (when enabled), and hosted AI services. This helps us understand feature adoption, diagnose crashes, measure performance, and prioritize improvements.

PostHog data may include, for example:

• Page views, navigation paths, and UI interactions
• App version, operating system, and device class
• Error and diagnostic events, including failed or degraded requests
• Aggregated inference or API usage events (such as request counts or latency buckets)

We configure analytics to minimize identification of individual users. We identify you to our analytics only by your account identifier — never by your email address or your name. Our analytics is configured to run without cookies and without storing any analytics identifier on your device, so you are not tracked between visits while signed out, and not across other sites at any time. While you are signed in, activity is linked to your account identifier so we can measure whether features are actually useful over time. We do not use session recording or replay, so the contents of your screen and your conversations are never captured by analytics. We also honour your browser's Do Not Track setting. PostHog processes data as our service provider under contractual data protection terms. Learn more at posthog.com/privacy.

You can limit analytics collection by adjusting browser cookie settings, using privacy tools that block analytics scripts, or — where available in ArmaraOS — disabling telemetry in product settings. If you opt out of analytics in a jurisdiction that requires consent, we will honor that preference for future collection once applied.

6. Cookies and similar technologies

We use cookies and similar technologies for:

• Essential operations — authentication sessions, security, load balancing, and checkout flows (these are necessary for the Services to function)
• Referral attribution — storing referral codes (for example, armara_ref) for up to 30 days to attribute signups and affiliate commissions
• Analytics — none. Our analytics is configured to run without cookies and without storing an identifier on your device, as described in section 5

Most browsers let you block or delete cookies. Blocking essential cookies may prevent you from signing in or completing purchases.

7. How we disclose personal information

We disclose personal information only as described below. We require service providers to process personal information on our instructions and under appropriate contractual safeguards.

7a. Service providers and subprocessors

We may update subprocessors from time to time. Material changes will be reflected in this Policy or a linked subprocessor list.

7b. Other disclosures

• Legal and safety — to comply with law, regulation, legal process, or governmental request, or when we believe in good faith that disclosure is necessary to protect rights, safety, security, or to detect and prevent fraud or abuse
• Business transfers — in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to standard confidentiality obligations
• With your direction — when you integrate third-party services or explicitly authorize sharing
• Public game content— when you publish a game, its title, description, thumbnail, and your display name are visible to anyone, including on websites where it is embedded. When you set a score on a published game while signed in, your profile display name and best score appear on its public leaderboard. You can remove your score from the game's page at any time
• Aggregated or de-identified data — we may share statistics that do not reasonably identify individuals

8. Legal bases for processing (EEA, UK, Switzerland)

If you are in the European Economic Area, United Kingdom, or Switzerland, we process personal data only where we have a valid legal basis, including:

• Contract — to provide the Services you request, manage your account, and process payments
• Legitimate interests — to secure the Services, prevent abuse, improve product quality through anonymous analytics, and communicate about the Services, balanced against your rights
• Consent — where required for non-essential cookies, analytics in certain jurisdictions, or optional features
• Legal obligation — to comply with applicable law, tax, and accounting requirements

You may withdraw consent at any time where processing is consent-based, without affecting the lawfulness of processing before withdrawal.

9. Your privacy rights

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or port personal information, and to lodge a complaint with a supervisory authority.

• Access and correction — review and update account information in your account settings or by contacting us
• Deletion — request deletion of your account and associated personal information, subject to legal retention exceptions
• Opt-out of marketing — unsubscribe from promotional emails using the link in the message or by contacting us
• Analytics preferences — use browser controls or in-product settings where available

To exercise rights, email hello@ainativelang.com. We may verify your identity before fulfilling requests. We respond within timeframes required by applicable law.

10. U.S. state privacy disclosures

Residents of California, Colorado, Connecticut, Virginia, and other U.S. states with comprehensive privacy laws may have additional rights, including the right to know categories of personal information collected, to delete personal information, to correct inaccurate personal information, and to opt out of certain processing.

Categories collected (last 12 months). Identifiers (email, account ID, IP address); commercial information (subscription and transaction records); internet or network activity (logs, analytics events); and user content you submit to hosted Services.

Business purposes. Providing Services, security, analytics, billing, support, and compliance as described in this Policy.

No sale or sharing for cross-context behavioral advertising. We do not sell personal information and do not share it for cross-context behavioral advertising as those terms are defined under California law. We do not use or disclose sensitive personal information for purposes other than those permitted by CPRA.

California residents may designate an authorized agent to submit requests on their behalf. We do not discriminate against you for exercising privacy rights.

11. International data transfers

We and our service providers may process personal information in the United States and other countries where we or our vendors operate. When we transfer personal data from the EEA, UK, or Switzerland, we rely on appropriate safeguards such as Standard Contractual Clauses, adequacy decisions, or equivalent mechanisms offered by our subprocessors.

12. Security

We implement administrative, technical, and organizational measures designed to protect personal information, including encryption of API keys at rest, server-side session validation, row-level database protections, rate limiting, webhook signature verification, content security policies, and access controls for production systems. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

Report suspected vulnerabilities or security issues to hello@ainativelang.com. See our repository SECURITY.md for additional hardening notes where published.

13. Data retention

We retain personal information only as long as necessary for the purposes described in this Policy, unless a longer period is required or permitted by law.

• Account data — retained while your account is active and for a reasonable period afterward for backup, dispute resolution, and legal compliance
• Billing records — retained as required for tax, accounting, and chargeback evidence
• Hosted inference logs — retained for operational, security, and abuse investigation purposes, then deleted or aggregated according to internal schedules
• PostHog analytics — retained according to PostHog project settings and our analytics retention configuration
• Authentication security events — successful sign-in and sign-out records (account identifier, timestamp, IP, approximate location, and browser/device metadata) retained for security and abuse investigation, typically up to 12 months, then deleted or aggregated
• Games — games, versions, scores, and saves are kept until you delete the game or your account. The record of builds and build pack purchases is kept after a game is deleted, for billing, allowance enforcement, and accounting. Records of Games Studio terms acceptance and ownership transfers are kept while your account exists, as evidence of what was agreed
• Linked wallets— kept until you unlink the wallet or delete your account. Daily balance records are kept by wallet address so a wallet can't be moved between accounts to reset its holding period
• Referral cookies — up to 30 days unless cleared earlier

14. Children

You must be at least 16 years old (or older, if your jurisdiction requires it) to create an account, and users under 18 need a parent or guardian's permission, as set out in our Terms of Service. The Services are not directed to children, and we do not knowingly collect personal information from anyone under 16. Published games can be played without an account; players who are signed out keep their scores and saves in their own browser, and we do not ask them for personal information. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.

15. Changes to this Policy

We may update this Privacy Policy from time to time. When we do, we will post the updated Policy on this page and revise the effective date above. If changes are material, we will provide additional notice where required by law (for example, by email or in-app notification). Continued use of the Services after the effective date constitutes acknowledgment of the updated Policy.

16. Contact us

Questions about this Policy or our privacy practices:

AINativeLang Inc.
Email: hello@ainativelang.com
Website: armaraos.com