Privacy Policy

1. Summary

Aori is designed as a local-first personal AI app.

The most important point is this:

Aori does not operate an Aori-hosted backend for app data. Aori does not collect or store your app conversations, files, local memory, API keys, settings, provider responses, or local app data on Aori-controlled servers.

In the Aori app:

• Aori does not require an Aori account.
• Aori stores app data locally on your device.
• Aori does not upload your app conversations, files, local memory, API keys, settings, or AI provider responses to Aori-controlled servers.
• If you choose a cloud AI provider, Aori sends the content needed to answer your request directly from your device to the provider you selected.
• On desktop, if you configure a local model runtime such as Ollama, Aori may send prompts and related context to the local endpoint you configured, such as an Ollama service running on your own machine.
• If you opt in to in-app analytics, Aori sends limited product-usage information to Aptabase Cloud EU. These analytics are designed not to include prompts, AI responses, files, filenames, folder paths, API keys, emails, calendar contents, contacts, or local memory.
• Aori does not use Sentry or automatic crash-reporting for the initial launch unless this policy is updated before such tooling is enabled.

On the Aori website:

• The website is intended to be a static website without an Aori application database.
• We use Umami to understand website visits and interactions such as download-button clicks.
• Hosting, CDN, DNS, security, and download providers may process ordinary technical logs.
• The launch website does not require a user account.
• If a mailing-list form is later enabled, we will process the email address and related information you voluntarily provide.
• If you contact us, we process the information you choose to send, such as your email address and message content.

Aori may still process some personal data in limited contexts, such as website analytics, support emails, beta feedback, optional in-app analytics, and any mailing list that may be enabled later. This policy explains those contexts.

2. Scope of this policy

This Privacy Policy explains how we handle information in connection with:

1. the Aori desktop app for Windows, macOS, and Linux;
2. the Aori mobile app for Android and iOS, when available;
3. the Aori website at https://aori-ai.app;
4. Aori downloads, documentation, release notes, and beta builds;
5. support, feedback, and beta-testing communications;
6. optional integrations that you choose to configure in Aori.

This policy does not apply to third-party AI providers, local model runtimes, app stores, operating systems, analytics providers, hosting providers, integration providers, or websites that are not controlled by us. Their own privacy policies and terms apply.

3. Who is responsible for data processing

For data that we actually collect or receive, the controller is:

Robert Meliksetyan An individual based in Portugal Email: aori.support@gmail.com Aori is a product and brand operated by the controller listed above. Aori AI may be used as the public developer name, app-store publisher label, website/domain brand, or product brand. Aori AI is not currently a separate limited company, LLC, Lda., or other incorporated legal entity.

If Aori is later transferred to or published by a company, this section should be updated with the company’s legal name, registered office, company number, and privacy contact.

4. How Aori works by design

Aori is built to run on your device. The app stores its working data locally, such as:

• conversations and conversation history;
• app settings;
• selected AI provider settings;
• API keys or access tokens, where supported by the operating system’s secure storage;
• local memory and personalization data;
• persona settings;
• local files or file references you choose to use with Aori;
• local folder and Obsidian vault connection settings;
• local logs required for app operation or troubleshooting.

Aori does not upload this app data to an Aori-controlled server, because there is no Aori backend for app data.

You control when Aori uses external services, such as cloud AI providers, local model runtimes configured by you, website downloads, analytics, or optional integrations.

5. Information stored locally on your device

Aori may store the following information locally on your device:

You can delete local Aori data by using in-app deletion/reset controls where available, or by uninstalling the app and deleting the app’s local data directory according to your operating system.

Because Aori does not store your app data on Aori-controlled servers, we cannot recover your local conversations, local memory, local files, API keys, or local settings if they are lost.

6. Information sent to cloud AI providers

Aori supports cloud AI providers that you choose and configure yourself. Examples may include OpenAI, Anthropic, Google Gemini, Groq, Mistral, DeepSeek, OpenRouter, Cohere, or other OpenAI-compatible providers.

When you choose a cloud AI provider, Aori sends the information necessary to process your request to that provider. Depending on the feature you use, this may include:

• your prompt or chat message;
• relevant conversation context;
• selected memory/context snippets needed for the request;
• files, images, or documents you attach or explicitly ask Aori to use;
• tool results or integration outputs needed for the request;
• model parameters and request metadata;
• your API key or access token, as needed to authenticate the request with the provider.

Aori does not receive or store a copy of that content on Aori-controlled servers. The content is transmitted from your device to the provider you selected.

Your use of a cloud AI provider is governed by that provider’s own terms, privacy policy, data-retention rules, account settings, and safety policies. You should review those provider policies before sending sensitive content to a cloud provider.

7. Desktop local model runtimes such as Ollama

On desktop, Aori may support connecting to a local model runtime such as Ollama.

If you configure Aori to use a local runtime running on your own device, Aori may send prompts, relevant context, and related request data to the local endpoint you configured. Aori does not operate that local runtime and does not receive the prompts or responses on Aori-controlled servers.

If you configure Aori to use an endpoint that is not actually local, such as a remote server using an OpenAI-compatible API, then prompts and related context may be sent to that endpoint. You are responsible for understanding where your configured endpoint is hosted and what privacy terms apply to it.

Aori may still use the network for other features you enable, such as cloud AI providers, app updates, website downloads, optional integrations, or analytics.

8. Optional integrations and channels

Aori may support optional integrations and channels that you choose to configure, such as:

• Telegram;
• WhatsApp;
• Google Account features such as Gmail or Calendar;
• Notion;
• Local Folder;
• Obsidian Vault;
• Zapier or other integration providers, if enabled in a future build;
• cloud AI providers and desktop local runtimes such as Ollama.

When you connect a third-party service, Aori may access or process information from that service according to the permissions you grant and the features you use. For example, if you connect Google Account features, Aori may access the Gmail or Calendar data needed to perform the task you requested.

Aori does not upload integration data to Aori-controlled app-data servers. However, integration data may be sent to:

• the integration provider itself;
• a cloud AI provider you selected, if needed to answer your request;
• your own device or local runtime;
• other third-party services you explicitly ask Aori to use.

Third-party services have their own terms and privacy policies.

9. WhatsApp integration warning

WhatsApp integration is different from Telegram bot integration.

Telegram supports creating a bot account for this type of assistant workflow. WhatsApp does not provide the same simple bot-account model for Aori’s use case. If you connect Aori to WhatsApp, you connect Aori to a WhatsApp account controlled by you.

For privacy and account-separation reasons, we recommend using a separate WhatsApp account and, where needed, a separate SIM card for Aori rather than connecting Aori to your main personal WhatsApp account.

You are responsible for complying with WhatsApp’s terms and for understanding the risks of connecting automation software to a WhatsApp account, including the possibility of account limitations, delivery issues, unsupported behavior, or platform changes.

10. Local Folder and Obsidian Vault

Aori may let you grant access to a specific local folder or Obsidian vault.

In the launch scope, these features are intended to let Aori:

• read files inside the folder or vault you choose;
• search and index supported files locally;
• use relevant content from those files to answer your requests;
• create new files where the feature allows it;
• append to files where the feature allows it.

In the launch scope, Aori is not intended to autonomously delete or directly edit user-created notes in Local Folder or Obsidian Vault. Future file modification features may require explicit approval and updated documentation.

If you ask Aori to use a cloud AI provider while working with local files or vault content, Aori may send the relevant extracted content to the selected provider to process your request. Do not use cloud providers with confidential or sensitive local files unless you have assessed the risks and the provider’s terms.

11. Personas, channels, and conversation separation

Aori supports personas, including Assistant and Friend-style presets, and may allow you to switch personas using commands in supported channels.

Aori may support multiple in-app conversations and multiple external channels or threads. Aori is designed so that conversations, channels, and threads are handled as separate contexts rather than being automatically mixed together.

The content of your conversations and persona settings is stored locally on your device.

12. Website analytics with Umami

We use Umami to understand website traffic and download interest.

Website analytics may help us understand:

• which pages are visited;
• which referrers bring visitors to the website;
• which download buttons are clicked;
• which platforms visitors are interested in, such as Windows, macOS, Linux, Android, or iOS;
• basic technical information needed to operate and secure the website.

We do not use website analytics to track you across unrelated websites.

Depending on our configuration, Umami analytics data may be processed by Umami and/or by infrastructure providers used to host the analytics service.

Website hosting, CDN, DNS, security, and download providers may also process ordinary technical logs, such as IP address, browser information, request URL, timestamp, and error logs, as part of delivering and securing the website.

13. Optional in-app analytics with Aptabase

Aori includes optional in-app product analytics using Aptabase Cloud EU.

In-app analytics are disabled by default. You can choose whether to enable them during onboarding or later in Settings → App Settings → Privacy & Data. You can disable them again at any time.

If you enable in-app analytics, Aori sends limited usage and technical information to Aptabase Cloud EU to help us understand how the app is used and where users encounter problems. This may include information such as:

• that the app was opened;
• whether onboarding was completed;
• whether users start, complete, or fail to complete AI provider setup;
• whether a chat request was sent, completed, or failed;
• whether users open major settings areas;
• whether analytics were enabled or disabled;
• broad technical information such as app version, platform, operating system family, build type, and broad feature area.

Aori in-app analytics are designed NOT to send:

• prompts;
• AI responses;
• conversation titles;
• memory contents;
• file contents;
• file names;
• local folder paths;
• Obsidian vault paths;
• API keys;
• OAuth tokens;
• email contents;
• calendar contents;
• contact data;
• provider responses;
• screenshots;
• raw logs;
• crash stack traces;
• advertising IDs;
• stable device identifiers;
• persistent user identifiers.

Aori does not use a stable install ID for analytics in the launch implementation. Aori does not keep a persistent analytics queue. If analytics cannot be sent during a session, unsent in-memory analytics events may be dropped.

If you use “Delete all local data,” Aori resets analytics consent to disabled and clears any unsent in-memory analytics events. After local data is reset, analytics defaults back to disabled.

14. Crash reporting and diagnostics

Aori does not use Sentry or automatic crash-reporting for the initial launch at this time.

If Aori later adds automatic crash reporting or error-monitoring tools, this Privacy Policy and any relevant app-store disclosures should be updated before those tools are enabled in public or test builds.

If you voluntarily send us logs, screenshots, crash descriptions, or bug reports, we process the information you choose to send for support, troubleshooting, and product improvement. You should remove confidential information, prompts, AI responses, files, API keys, personal messages, email contents, calendar details, contact data, and other sensitive information before sending support materials.

15. Mailing list and email communications

The launch website does not include an email-subscription form. If we later enable a mailing list or early-access signup, we may collect information you voluntarily provide, such as your email address and optional name.

We would use this information to send Aori updates, beta invitations, release notes, or related communications. You would be able to unsubscribe using the instructions in those emails.

If we use a third-party email provider, that provider will process mailing-list information according to its own terms and privacy policy. This policy should be updated with the provider name before the mailing list is enabled.

16. Support, feedback, and beta testing

If you contact us for support, send feedback, report a bug, or participate in beta testing, we may process information you choose to provide, such as:

• your email address;
• your name or display name, if provided;
• your message content;
• app version and platform information;
• screenshots, logs, or diagnostic details you choose to attach;
• information needed to respond to your request.

Do not send confidential information, prompts, AI responses, files, API keys, email contents, calendar contents, contact details, or other sensitive data unless you intentionally choose to share it for support.

We may use support and feedback information to respond to you, diagnose problems, improve Aori, and maintain support records.

17. Legal bases for processing

Where EU/Portuguese data-protection law applies, our legal bases may include:

You may withdraw consent for optional in-app analytics by disabling analytics in the app settings. You may withdraw consent for mailing-list communications, if enabled, by unsubscribing.

18. Data sharing and recipients

We may share or make data available to the following categories of recipients, depending on what you use:

• cloud AI providers you choose and configure;
• local or remote model runtimes you configure, such as Ollama or compatible endpoints;
• integration providers you connect, such as Google, Notion, Telegram, WhatsApp, or other services;
• Umami and/or infrastructure providers used for website analytics;
• Aptabase Cloud EU for optional in-app analytics if you opt in;
• website hosting, CDN, DNS, security, and download providers;
• app stores and operating-system providers;
• email/support providers if you contact us or subscribe to a mailing list when available;
• legal, accounting, or compliance advisers where necessary.

We do not sell your app conversations, files, local memory, API keys, provider responses, or local app data.

19. International transfers

Some third-party providers you choose may process data outside Portugal, the European Economic Area, or your country of residence.

This may include cloud AI providers, analytics providers, hosting providers, app stores, email providers, and integration providers.

When you choose a third-party provider, that provider’s own terms, privacy policy, and transfer mechanisms apply. You should review those policies before sending sensitive content to a provider.

For Aptabase analytics, the launch configuration is intended to use Aptabase Cloud EU.

20. Retention

Because Aori stores app data locally on your device, retention of conversations, local memory, files, settings, and provider keys is primarily controlled by your device, app settings, and deletion choices.

We may retain limited information that we actually receive, such as:

• support emails and feedback for as long as reasonably needed to respond and maintain support records;
• mailing-list information, if enabled, until you unsubscribe or we delete the list;
• website analytics according to the retention settings of Umami and hosting providers;
• optional in-app analytics according to Aptabase retention settings;
• security or technical logs according to hosting and infrastructure retention settings.

21. Your rights

Depending on your location and applicable law, you may have rights to:

• access personal data we hold about you;
• correct inaccurate personal data;
• delete personal data;
• restrict or object to processing;
• withdraw consent where processing is based on consent;
• receive a copy of data you provided to us;
• complain to a data-protection authority.

Because Aori does not store your app data on Aori-controlled servers, we cannot access, correct, export, or delete local app data for you. You can manage local app data on your own device through app controls, operating-system controls, or by uninstalling the app and deleting local data.

To exercise rights for data we actually hold, such as support emails, mailing-list information, website analytics information where identifiable, or optional analytics information where identifiable, contact aori.support@gmail.com.

22. Children

Aori is not intended for children under the age required by applicable law to use online services without parental consent.

If you believe a child has provided personal data to us, contact aori.support@gmail.com

23. Security

Aori is designed to reduce central data risk by keeping app data local and avoiding an Aori-hosted backend for app data.

However, no app, device, network, storage method, or third-party provider is perfectly secure. You are responsible for:

• keeping your device secure;
• protecting your API keys and credentials;
• using operating-system security features;
• reviewing third-party provider terms and settings;
• avoiding sending sensitive content to providers you do not trust;
• keeping backups of important local data.

24. Changes to this policy

We may update this Privacy Policy as Aori changes.

We aim to update this policy before enabling any material new data collection, such as automatic crash reporting, additional analytics, new mailing-list providers, or new cloud services that process user data.

25. Contact

For privacy questions or requests or general support contact:

aori.support@gmail.com