Effective date: 24 June 2026 · Last updated: 22 October 2026

1. Who we are

This Privacy Policy explains how Niravi Inc. ("Niravi", "we", "us", or "our") collects, uses, and protects your personal data when you use our marketing site (niravi.io), our web application (web.niravi.io), our API (api.niravi.io), and the Niravi ACE desktop app for macOS (ace.niravi.io) (together, the "Service"). Niravi ACE indexes the footage, pictures and documents on your Mac so you can find the exact moment you need, and helps you edit, make and publish videos. Most of its work happens on your Mac; this policy says exactly when something leaves it.

For the purposes of the EU/UK General Data Protection Regulation (GDPR), Niravi Inc. is the data controller of the personal data described in this policy.

Niravi Inc., a Delaware C-corporation.
Postal address: 1111B South Governors Ave, Ste 94007, Dover, DE 19904, USA
Privacy contact: [email protected]

2. What data we collect

We collect the following categories of personal data:

Account data. When you sign up or sign in, authentication is handled by our identity provider, Auth0 (an Okta company). We receive your email address, name (where provided), and an account identifier. We do not store your password — credentials are managed by Auth0.
Content you upload for processing. Videos, audio, images, and related metadata that you (or your organisation) submit to the Service so that we can index, search, transcribe, and analyse them on your behalf, together with the analysis outputs we generate from that content.
Usage data. Information about how you interact with the Service, such as features used, queries run, and actions taken.
Technical and log data. IP address, browser and device type, and server log information generated when you access the Service, used for security, debugging, and service reliability.
Website visit data. When you visit niravi.io or download our app, we log each page request or download: your IP address, the approximate location and timezone derived from it (country, region, city), your network provider, the page requested and any campaign tags in its link (utm and ref parameters), the referring page, your browser's preferred language, and its user-agent string. A small first-party script on niravi.io also reports, without cookies, which links and buttons you click (including links within the site and mail links, with the link's text or target), which of its sections came into view, how far down a page you scroll (25/50/75/100%), and how many seconds the page was visible. We use this to understand how the site is used, to measure downloads, and to detect abuse. No cookie or other identifier is placed on your device for this. Legal basis: legitimate interests (Art. 6(1)(f)).
App update checks. Once a day, the Niravi ACE desktop app asks our server whether an update is available. That request carries your IP address (and the location and network provider derived from it), the app version, a random install identifier created by the app on first launch, and a basic device profile: macOS version, chip, Mac model, memory, processor count, and language setting. It carries nothing about your files, your library, or your identity. We use it to count active installs, see which versions and Macs are in use, and support you. You can turn it off with defaults write io.niravi.ace ace.shareInstallInfo -bool false; update checks keep working without it. Legal basis: legitimate interests (Art. 6(1)(f)).
Niravi's cloud (Nira, voice, pictures, stock). Niravi ACE does its indexing and search on your Mac. Some things it does through our server at api.niravi.io instead, and only then is anything sent:
- Asking Nira, when you have not set up a key or a model of your own: your question and the earlier messages of that conversation, the passages Nira read to answer it, and the names of those files (never their paths). We pass them to the model on Microsoft Azure that writes the answer.
- Narration (voice): the words of the line to be spoken. Microsoft Azure speaks them.
- Pictures: the words you asked for and the shape of the picture. Google makes the picture.
- Clips: the words you asked for, the length and shape of the clip, and any frame or reference picture you attached. Google makes the clip.
- Stock: the words you searched for. We ask the stock libraries (Pexels, Unsplash and Freesound) and send back what they found; the libraries see our server, not your Mac. When you take a stock file, our server confirms the take with that library, and your Mac then downloads the file from the library's own servers, which see your IP address and the app version, but not your install identifier or token. If you sign in to Freesound, the sign-in passes through our server because it holds Niravi's Freesound key. Your Freesound token goes back to your Mac, travels through our server only when you take a Freesound sound, and is never stored or logged by us.
Every one of these requests also carries your IP address, the app version, a token the app gets from our server the first time it asks, and, unless you turned it off, the same random install identifier the update check sends. The install identifier is there so that our counts belong to one Mac.
What we keep is counts, not content: for each Mac and each day, how many answers, lines, pictures, stock searches and stock files it used, how many failed or were refused, the number of characters spoken and tokens used, and what they cost us. Beside those counts we keep the install identifier, the app version, and when that Mac first and last asked. To limit how many new Macs one network can sign up in a day, we count sign-ups against a keyed hash of the network address, not the address itself. We do not keep your questions, the passages, the words you asked for, or what came back. Our server logs record the same counts and identifiers (see "Technical and log data" above), never the content.
We use this to apply each Mac's daily limits, to see what the service costs, and to stop abuse. The same command, defaults write io.niravi.ace ace.shareInstallInfo -bool false, stops the app sending the install identifier here too, from the next time the app starts; the counts are then kept against the token alone. Answering with your own key or a model on your Mac keeps your questions off our server, and NIRAVI_RELAY_URL=off in ~/.niravi-ace/env (or ~/.arrow/env on a Mac that had Arrow) stops every one of these requests. Legal basis: performance of a contract (Art. 6(1)(b)) for sending what you asked for, and legitimate interests (Art. 6(1)(f)) for the counts.
"Counts, not content" describes these requests. When you sign in to Niravi ACE, some content is kept on your account on purpose; the next two items say what.
What Nira knows, kept on your account (signed in only). When you are signed in to Niravi ACE, what Nira has learned to work with you is kept on your Niravi account, so that another Mac you sign in on starts with it: Nira's memory of you and your projects, the skills you saved, the rules Nira learned about which services to use, your preferences (model choices, editing and making choices, the look of your reels) and the templates you made. Each entry is stored with its title, its text, a version, when it changed and which install changed it. We store at most 64 KB per entry, 2,000 entries and 8 MB per person. It never includes your keys or passwords (those stay in your Mac's Keychain), your files, or Nira's conversations, and a learned rule's words are redacted on your Mac before they are kept. You can turn syncing off for each kind, or for a single entry, in Niravi ACE; when signed out, nothing is sent. When you delete an entry, its text is deleted from our server and only a deletion marker (its name and version, with no text) is kept so your other Macs delete it too. When you delete your account, every entry is deleted with it. Legal basis: performance of a contract (Art. 6(1)(b)).
How Nira's turns went. For each request you make to Nira, Niravi ACE sends our server a record of how it went, not what was said: which tools ran and whether they worked, the model used, the time taken, the tokens used and any error, with the install identifier and, when signed in, your account. The words of your question and the answer are sent only if you turn on "Share conversation details" or choose "Send this conversation", and are scrubbed of email addresses and file paths first. We keep these records for 90 days and any shared words for 30 days; turning sharing off deletes the shared words at once. We use them to find and fix where Nira fails. Legal basis: legitimate interests (Art. 6(1)(f)); consent (Art. 6(1)(a)) for shared words.
Plans, codes and access requests. When you are signed in, we keep your plan, the credits granted to and used by your account, any code you redeem (a giveaway code may be bound to your email address), failed code attempts (counted per account and per network, to stop guessing), and any request you make for a feature your plan does not include, with the note you wrote (up to 280 characters) and our decision. If you pay, our payment processor (Stripe) handles your card; we keep the payment record, never the card number. We keep these as billing records for as long as tax and accounting law requires; the email on a code and the note on a request are deleted when you delete your account. Legal basis: performance of a contract (Art. 6(1)(b)) and legal obligation (Art. 6(1)(c)).
Your own keys and accounts. If you give Niravi ACE your own key or account for another service (for example Deepgram for transcripts, OpenAI, Google Gemini, or your own Google Cloud project), Niravi ACE sends that service what it needs directly from your Mac, under your own agreement with that provider. That data does not pass through our servers, and the provider is not our sub-processor. The key stays in your Mac's Keychain.
Google and YouTube. If you connect your Google account or your YouTube channel, see Section 6, "Google API Services and YouTube".
Register your interest. If you use the "Register your interest" form on niravi.io, we receive the email address you enter, the optional message, the page you were on, the country derived from your IP address, and the time. It is delivered to our mailbox through Resend (Section 5) so we can write back. We keep it until the request is answered and for up to twelve months after. Legal basis: consent (Art. 6(1)(a)) and legitimate interests (Art. 6(1)(f)).
Cookies. Strictly-necessary authentication and session cookies. See our Cookie Policy for details. On niravi.io, and only if you allow it, Google Analytics measures how the site is used, and the Meta Pixel and the Google Ads tag measure which of our ads led to a visit or a download and let Meta and Google show you Niravi ads after you visit (see Section 4).

3. Purposes and legal bases

We process your personal data for the following purposes, relying on the legal bases in Article 6 GDPR:

To provide the Service — creating and maintaining your account, processing the content you submit, and returning analysis and search results. Legal basis: performance of a contract (Art. 6(1)(b)).
To secure and improve the Service — preventing abuse, maintaining reliability, debugging, and improving features. Legal basis: our legitimate interests (Art. 6(1)(f)) in running a secure, functional service.
To communicate with you — service announcements and responses to your requests. Legal basis: performance of a contract and/or legitimate interests.
Where you give consent — for any processing that requires it (for example, measuring how niravi.io is used with Google Analytics, measuring our ads and showing you Niravi ads after a visit with the Meta Pixel and the Google Ads tag, or marketing communications). Legal basis: consent (Art. 6(1)(a)), which you can withdraw at any time.
To comply with the law — where we are subject to a legal obligation. Legal basis: legal obligation (Art. 6(1)(c)).

4. Cookies

We minimise cookies. The Service sets strictly-necessary authentication and session cookies (via Auth0). We set no analytics or tracking cookies unless you allow them (below). Every website visit is also measured from server request logs, without cookies (see Section 2). Fonts are self-hosted, so no font data is transferred to a third party. For full details, see our Cookie Policy.

Analytics and advertising on niravi.io. On the niravi.io website we use Google Analytics (Google) to see how the site is used: which pages and sections are seen, which buttons are clicked, and downloads. We use the Meta Pixel (Meta Platforms) and the Google Ads tag (Google) to learn which of our ads lead to a visit or a Niravi ACE download, and to show you Niravi ads on Meta and Google after you visit. They load only after you tap Allow on the consent bar; until then nothing is sent to Meta or Google and no analytics or advertising cookie is set. When allowed, Meta and Google receive the page address, the event (a visit, a section seen, a click or a download), your IP address, browser details and their own cookie identifiers, and process them under their own privacy policies. Google Analytics keeps the event data of our property for 14 months; the cookies live up to 13 months (Google Analytics) and 90 days (Meta, Google Ads). We do not send them your name, email address, account details or any content you index or upload. A yes is kept in your browser for twelve months, after which we ask again, and a no until you change it; a browser that sends the Global Privacy Control signal is treated as a No. You can withdraw consent at any time with Cookie settings in the footer of every page or on our Cookie Policy page; withdrawing tells Meta and Google to stop and clears their cookies. Data we receive through Google APIs or YouTube (Section 6) is never used for these tags.

5. Sub-processors and infrastructure providers

We use a small number of trusted infrastructure providers ("sub-processors") to operate the Service. Some of these providers may process data outside the European Economic Area (EEA); see Section 8 for the safeguards we apply.

Provider	Purpose	Processing location
Auth0 (Okta)	Authentication and session management	Outside the EEA may apply
Cloudflare	Static hosting (Cloudflare Pages), CDN, and DNS	Global edge network
Microsoft Azure	Storage and compute for content processing; the model and the voice behind Niravi's cloud	Azure regions including Central India and East US 2
Google Cloud	Making pictures and clips (Gemini image and video models) for Niravi's cloud	Outside the EEA may apply
Stripe	Payment processing, when you pay for a plan	Outside the EEA may apply
Resend	Delivering the "Register your interest" form to our mailbox	United States

We may update this list as our infrastructure evolves; material changes will be reflected in this policy.

When you publish to YouTube or connect your own Google Cloud project, your Mac talks to Google directly, under your own Google account and Google's terms; Google is not acting as our sub-processor there (see Section 6). The same holds for any service you use with your own key (see Section 2).

6. Google API Services and YouTube

Niravi ACE uses Google API Services in two optional features. Each asks for its own Google sign-in, only when you start that feature, and asks only for what that feature needs. Neither sends anything from your Google account or your YouTube channel to Niravi's servers: your Mac talks to Google directly.

Connect Google Cloud

This lets Niravi ACE make pictures, clips and answers with your own Google Cloud credit. When you press "Connect Google Cloud" and allow it, Google gives Niravi ACE permission to manage your Google Cloud resources (the "cloud-platform" permission) and to see your email address. With that permission, and only during setup, Niravi ACE, running on your Mac:

finds or creates one Google Cloud project in your account (labelled niravi-ace) and links it to your billing account;
turns on the services it needs there (Vertex AI, Pub/Sub, IAM and the billing and budget services);
creates one service account with two narrow roles (use Vertex AI in that project, and read that Mac's own budget alert), and one key for it;
sets a budget alert so it can stop before your credit runs out;
reads your email address, to show you which account is connected.

When setup ends, Niravi ACE revokes its sign-in at Google. It does not ask for offline access and keeps no Google sign-in token. What remains is the service account key, kept in your Mac's Keychain, and a small file on your Mac with the project id, the alert's name and the amounts spent. "Disconnect" in Niravi ACE deletes the key from your Mac. The project, the service account and its key are resources in your own Google account; you can delete them in the Google Cloud console at any time. Usage there is billed by Google to you, under Google's terms.

Publish to YouTube

Niravi ACE uses the YouTube API Services to publish the videos you make to your own YouTube channel. By publishing to YouTube from Niravi ACE you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.

When you connect your channel and publish, Niravi ACE:

reads your channel's name, id and picture, to show you which channel a video will be published to;
uploads the video you chose, with the details you reviewed and confirmed: title, description, tags, chapters, captions, thumbnail, playlist, privacy setting (private, unlisted or public), publish time, the "made for kids" setting and, when the video contains generated media, YouTube's altered or synthetic content setting;
reads back the uploaded video's status (processing, scheduled, live) and its link, to show you when it is published;
only if you use them: reads the names of your playlists so you can pick one, uploads the caption track Niravi ACE made from the video's transcript, and changes the publish time of a video you scheduled from Niravi ACE when you move it. Niravi ACE asks Google for this extra permission the first time you use one of these.

Nothing is published without your confirmation, and Niravi ACE suggests but never changes your title or description after you confirm them. It does not read your other videos, comments, subscribers or YouTube Analytics, and it does not post, like, comment or subscribe on your behalf.

Where it is kept. Your YouTube sign-in token is kept only in your Mac's Keychain; short-lived access tokens exist only in memory while a video uploads. The channel name and id, and the id, link and status of the videos you published from Niravi ACE, are kept only on your Mac. None of it is sent to or stored on Niravi's servers, and we do not share it with anyone. Niravi ACE refreshes this stored YouTube data from YouTube or deletes it within 30 days, checks at least every 30 days that your authorization is still valid, and deletes it if it is not.

Disconnecting and deleting. "Disconnect YouTube" in Niravi ACE's settings revokes Niravi ACE's access at Google immediately and deletes the token and the stored YouTube data from your Mac. Deleting data in Niravi ACE does not delete anything on YouTube; to delete a video, use YouTube or YouTube Studio.

Revoking access

Besides "Disconnect" in Niravi ACE, you can revoke Niravi ACE's access to your Google account or YouTube channel at any time on Google's security settings page: myaccount.google.com/permissions (also reachable at security.google.com/settings/security/permissions). When access is revoked there, Niravi ACE deletes any YouTube data it stored for you within 30 days, and as soon as it next runs.

Limited Use

Niravi ACE'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.

We use Google user data only to provide the features described above, which you can see in Niravi ACE. We do not sell it, do not use it for advertising, do not transfer it to anyone, do not let people read it, and do not use it to develop, improve or train AI or machine learning models.

Questions or complaints about how Niravi ACE handles Google or YouTube data: [email protected].

7. Data retention

We retain personal data only for as long as necessary to provide the Service and to meet our legal, accounting, and security obligations. Account data is retained for the life of your account. Content you upload is retained until you delete it or close your account, after which it is removed from active systems within a reasonable period, subject to routine backup cycles. Technical and log data, including website visit and app update-check data, is retained for up to three months for analytics, security, and debugging. Google Analytics keeps the event data it collects with your consent for 14 months. A "Register your interest" message is kept until it is answered and for up to twelve months after. The per-Mac daily counts, the install registry (install identifier, app version, first and last seen) and the sign-up counters described under "Niravi's cloud" are not log data: we keep them as service and billing records for as long as Niravi's cloud runs. We have not yet set a fixed deletion period for them, and will state one here when we do. What Nira knows (Section 2) is kept until you delete it or your account. Records of Nira's turns are kept for 90 days, and any words you chose to share for 30 days. We keep no Google or YouTube user data on our servers; what Niravi ACE keeps on your Mac is described, with its 30-day limit, in Section 6. After you close your account, we delete or anonymise your personal data within 90 days, except where we are required to retain it longer to comply with legal, tax, accounting, or security obligations, or to resolve disputes.

8. International transfers and safeguards

Because our providers (Microsoft Azure, Google Cloud, Cloudflare, Auth0/Okta, Stripe and Resend) operate globally, your personal data may be transferred to and processed in countries outside the EEA, including India and the United States. Where we transfer personal data outside the EEA/UK, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses (SCCs) and equivalent UK mechanisms, together with any supplementary measures required to ensure an adequate level of protection.

9. Your rights

Subject to applicable law, you have the right to access your personal data, request rectification of inaccurate data, request erasure, obtain data portability, object to certain processing, and request restriction of processing. Where we rely on consent, you may withdraw it at any time. You also have the right to lodge a complaint with your local data protection authority.

To exercise any of these rights, contact us at [email protected]. We will respond within the timeframe required by applicable law.

California residents (CCPA/CPRA) and residents of India under the Digital Personal Data Protection Act, 2023 (DPDP Act) have analogous rights, including rights of access, correction, and deletion. You can exercise these rights using the same contact above; we do not "sell" personal data as that term is defined under California law.

10. Security

We take reasonable technical and organisational measures to protect personal data against unauthorised access, loss, or misuse, including encryption in transit, access controls, and use of reputable infrastructure providers. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Children

The Service is not directed to children. We do not knowingly collect personal data from anyone under the age of 18. If you believe a child has provided us with personal data, please contact us and we will take appropriate steps to delete it.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, notify you. Your continued use of the Service after an update constitutes acceptance of the revised policy.

13. Contact

Questions about this policy or our data practices? Contact us at [email protected], or write to us at: Niravi Inc., 1111B South Governors Ave, Ste 94007, Dover, DE 19904, USA.