Nirmind

Privacy Policy

Last updated: 15 November 2026

Data controller: Nireya Teknoloji A.Ş.

Fulyalı Sokak No:35, 34394 Beşiktaş / İstanbul, Türkiye

Privacy and data requests: [email protected]

Scope and feature availability

This policy covers the nirmind.io website and web application, the iOS/Android Super App and the macOS app. Processing depends on the features you use, accounts you connect and permissions you grant; features vary by platform. Reading this notice does not constitute consent to optional processing.

Account, device and usage information

Name, email, phone number, profile photo, user ID, language and session information support accounts and synchronization. IP address, device/platform, app version, sign-in and last-active times, feature/action events, errors and usage records may be processed for security, troubleshooting and service operation. Activity history may record actions within the app.

Email connections and content

Gmail and Outlook/Microsoft use granted OAuth permissions; corporate IMAP/SMTP and the current Yahoo app-password connection use supplied credentials. Yahoo OAuth developer approval is not yet complete. Account address/photo, folders, counts, senders/recipients, subjects, text/HTML, attachments, drafts and read/flag status support email functions. OAuth tokens may be stored on devices and where needed on servers; IMAP/SMTP passwords may be stored encrypted on servers. Relevant content may be cached; AI analysis/reply tools may send necessary email content to AI providers. Disconnecting does not delete the provider mailbox; deleting/moving messages in Nirmind may affect it.

Contacts, calendar and location

With permission, contact names, phone/email and source accounts support matching, finding people and communication; calendar titles, times and participants support planning. Location permission may enable coordinates, visited/saved places and place memory for suggestions and reminders. These data may enter the context of relevant assistant requests. OS permissions and connected-account permissions can be revoked separately.

Health data

On supported devices, Apple HealthKit and Android Health Connect use read-only access. Depending on permission, activity/steps, sleep, workouts, heart rate, body measurements, nutrition and other health metrics may be read and synchronized to servers. Separate health consent is required; relevant summaries and personal replies may involve AI context. Health data is not used for advertising, sale or ad targeting. Health features are not a medical diagnosis. Withdraw consent in Settings → Privacy and read permissions in OS settings; withdrawal does not automatically delete existing records.

Voice, meetings, photos and files

Selected/uploaded photos and files may be stored and analyzed for the requested task. Voice chat, dictation, translation and meetings may process audio, transcripts, speaker/participant information, summaries and tasks on servers or with relevant providers. Wake-word mode is off by default; when enabled, short audio clips may be transcribed on servers. You are responsible for informing participants and obtaining required permissions before recording or inviting the assistant to a meeting.

Assistant, personal memory and AI

Chats, preferences, tasks/projects and relevant connected-account data may support personal memory, responses, suggestions and automation. NirAIHub/NirArmy route tasks to models or tools, which may transfer content to third parties. Not all data is sent with each request; context depends on the feature. AI outputs and conversations may be stored on devices or servers. Provider retention and use depend on service configuration; we do not promise universal zero retention or automatic exemption from model training across all providers. AI outputs may be inaccurate.

Social content, messages and reports

Profiles/bios, follows, posts, stories, comments, reactions and messages support social features. Visibility depends on audience and sharing settings; recipients may retain copies outside your control. A story expiring from view does not mean its records are immediately deleted. Report reasons, descriptions, photos, reporting/reported users and decision history may be kept for review. Authorized administrators may access user, session, social and report records for their duties and create internal notes, assignments and action logs.

Other tools and connected services

Flight and music tools may process searches, flight/route details, recognition and playlist history; relevant information may reach services such as Flightradar24 or Apple iTunes. Creating tasks, events or messages in external services may transfer data to your chosen recipients. Connecting an account does not by itself grant unrestricted access to your entire device.

Service providers and international processing

Depending on the feature, providers may include Anthropic, OpenAI, OpenRouter and xAI through NirAIHub; ElevenLabs/OpenAI Realtime for voice; OneSignal/Expo for notifications; Cloudflare R2 for files; Google Maps/People/Gmail and Microsoft Graph for maps/contacts/mail; Brave/Tavily for research; Replicate/Gamma for generation; Resend for service email and hosting providers. IMAP/SMTP contacts your chosen mail server. Not every provider receives all data. Providers and servers may be outside Türkiye; request countries, contractual safeguards and transfer details at [email protected]. This notice alone is not authorization for international transfers.

Web storage and technical logs

Web and Mac renderers may store session, user/language preferences and interface state in browser local storage; mobile apps use local and supported secure storage. Servers may process IP addresses, request times, errors and security logs. When configured, Sentry may process error/performance data. Clearing browser data or resetting the device does not delete your server account. Opening third-party links or embedded content subjects that interaction to the relevant service’s own policy.

Security and access

TLS in transit, account/session checks and service-specific access restrictions are used. Corporate mail secrets are encrypted on servers; this does not mean all content has identical encryption. Nirmind does not offer a general end-to-end encryption guarantee for messages, email, files or AI processing. Authorized servers, providers and administrators acting within their duties may process relevant data. No internet service can guarantee absolute security; do not include passwords or verification codes in support requests.

Limits on data use

Connected email, contacts and health data are used to operate relevant user-facing features, not to sell that content or create advertising targeting audiences. Personal assistant suggestions and memory are distinct from ad targeting and fall within the relevant feature processing. This limitation does not mean necessary feature data is never sent to the providers described above.

Google API data (Limited Use)

Nirmind's use and transfer to any other app of information received from Google APIs (Gmail, Google Calendar, Google Contacts and Sign in with Google) will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We use this data only to provide and improve the user-facing features you see and use in the app; we do not use or transfer it to serve advertising, sell it, determine creditworthiness, or train generalized AI/ML models. Humans do not read this data except with your explicit permission, for security and abuse investigations, or when required by law. You can revoke Google access at any time in the app settings or in your Google Account permissions.

Collection methods and legal grounds

Data is collected electronically from your entries/uploads, device permissions, connected accounts and service use. Account, messaging, email and synchronization rely on contract performance; security/abuse review on legitimate interests balanced against your rights and protection of legal claims; mandatory records on legal obligations; optional processing and health data on separate explicit consent where required. Relevant frameworks include KVKK Articles 5/6 and, where applicable, GDPR Articles 6/9. OS permission alone is not legal consent for every processing activity.

Retention, disconnecting and account deletion

Account and feature records may be retained while the service and relevant purpose require them; there is no single fixed period for all data. Account deletion disables access and sessions; owned account, chat/memory, health, contact, mail credentials, task and file records are cleaned in the background. Provider failures are retried. Shared content, others’ messages and shared-reference files may remain; some moderation/security identifiers are pseudonymized, not fully anonymized. Backup and legally required record cleanup may differ. Device reset, permission withdrawal and account deletion are distinct; contact us for status and timing.

Your choices and data rights

Manage OS permissions, connected accounts, notifications and language in the relevant settings. Request confirmation of processing, access to data/recipients, correction, deletion or restriction where applicable, objection and portability where applicable at [email protected]. Consent may be withdrawn for future consent-based processing. We may verify identity but do not request passwords. You retain rights to complain to competent authorities under KVKK and, where applicable, GDPR. You may also challenge automated analysis or moderation outcomes at this address.

Updates and contact

This policy is updated as the product and data flows change; the revision date appears on this page. Updating a notice alone does not replace any new permission or consent required for a new purpose. Contact [email protected] or the postal address above about privacy, retention, international transfers or deletion. Include only information necessary for your request when contacting support.