Privacy Policy

This policy covers the Nemivo website at nemivo.co, the Nemivo web app, and the Nemivo browser extension. Together they are called “the service” below.

Nemivo is the party responsible for the personal data described here. If you have a question about anything on this page, write to support@nemivo.co.

Account information. Your email address, and your name if you provide one. If you sign in with Google we store the Google account identifier so we can recognise you next time, along with the web address of your Google profile picture, which is used only to show your avatar inside the app; we do not receive your Google password. If you sign up with a password we store only a hash of it, never the password itself.

Your saves. For every item you save we store what the platform published about it: the link, the platform it came from, the title, the caption or description, the creator name and handle, a thumbnail URL, and the embed information needed to show a preview. We also store what our AI derives from that text: a summary, tags, a topic, named entities and technologies, a detected language, a suggested collection, and a few classification labels.

Things you write. Collection names, notes, automation rules, questions you ask in Ask AI along with the answers returned, and any feedback you send us from inside the app.

Subscription information. Your plan, your AI credit balance and the identifiers of your subscription with our payment provider. Card numbers never reach our servers.

Product analytics. Events about how the product is used, such as an item being saved or a search being run. These are keyed to your internal account id; your email and name are attached as profile properties so we can support you. See the analytics section below for the strict list of what is never included.

Technical logs. Like any web service, our servers keep short-lived access and error logs which can include your IP address, browser user agent and the time of a request. They are used to keep the service running and to investigate abuse.

A saved post is written by someone else, so your library inevitably holds a little information about them: the creator name and handle the platform published, the caption they wrote, and anything a caption happens to mention. We process it because it is the only way to give you back the thing you asked us to remember, and we keep it to the minimum that job needs.

We do not copy the media itself. Nemivo stores a link to the thumbnail the platform serves, never the image or video file, so a post deleted at the source stops rendering here too. We build no profile of a creator, we do not group saves by who made them for anyone other than you, and none of this is sold, shared with advertisers, or used to train anybody’s model.

Your library is private by default. It becomes visible to another person only if you create a share link for a collection, and you can revoke that link at any time. If you are a creator and want a post of yours removed from our systems, write to support@nemivo.co and we will take it out.

On a supported platform the extension watches for you pressing that platform’s own save or bookmark button. When you do, it reads the public details of that one item, the same details listed above, and sends them to your library. It does not read your direct messages, your feed history, your followers, your contacts, or anything you type into the page.

Bulk import runs only when you press the import button on your saved page, and you can stop it before anything is sent.

On a couple of platforms a saved item arrives without any usable description, because the saved list simply does not show one. In that case the extension fetches that item’s own public page to fill in the missing text and author, such as a Pinterest pin’s page. This happens only for items you have already saved or chosen to import, never for anything else, and the pages fetched are the same public ones anyone could open.

The permissions the extension requests, and why:

• storage keeps your session token and the last save shown in the popup, on your own machine.
• scripting runs the capture logic on the supported platforms so a save can be detected.
• alarms refreshes the list of currently supported platforms on a timer, so a platform whose capture we have had to pause is not captured with broken results.
• host access to the eleven supported platforms plus nemivo.co, which is the minimum needed to detect a save and to hand the connection to your account.

The extension deliberately does not request the broad tabs permission. It can read the address of the tab you are on only when that tab is one of the sites listed above.

• To run the service: storing your saves, organizing them and searching them.
• To generate summaries, tags, collections and answers, as described below.
• To sign you in, verify your email address and let you reset a password.
• To operate your subscription and count AI credit usage.
• To understand which features are used so we know what to improve.
• To answer your support messages.
• To detect abuse and keep the service secure and available.

Nemivo does not run its own models. To produce a summary, tags and a collection for a save, the text that save carries, its title, caption and description, is sent to our AI provider and the result is written back to your library. The same applies to search: the text of your saves and the words of your query are converted into numerical embeddings by an embedding provider so that meaning-based search can work. When you use Ask AI, your question and the relevant excerpts from your own library are sent to the model that writes the answer.

Only text is sent. Nemivo does not upload your images or videos to any model, and it does not transcribe audio. This is also why a post with no caption produces a thin summary.

Our providers process this content to return a result to us. They are named in the next section.

We use a small number of service providers to run Nemivo. They act on our instructions and may only use the data to provide their service to us.

We also disclose data where the law requires it, for example in response to a valid legal request, and to protect the rights and safety of our users.

Product analytics tells us that a feature was used, not what it was used on. The following are excluded from every analytics event by rule, not by convention:

• The full caption, title or description of anything you saved.
• The URL of a saved item. We record the platform and the media type instead.
• Your Ask AI questions and the answers. We record only a length bucket and a category.
• Your collection names, your notes and your feedback text.
• AI free text such as summaries, topics, tags or detected entities.
• Authentication tokens, cookies and API keys.

There is no session recording, no autocapture of clicks and no advertising network in the product.

Nemivo uses cookies only where it needs them:

• A session cookie that keeps you signed in. It is set to be readable only by the server, not by scripts in the page.
• A short-lived cookie during Google sign-in that protects the sign-in request from being forged.
• Analytics cookies used to recognise a returning browser, one from Google Analytics and one from PostHog. The PostHog one is set only once you sign in; before that, PostHog runs without any cookie or other browser storage at all.

There are no advertising or cross-site tracking cookies.

Your saves, notes, collections, rules and conversations are kept until you delete them or until you delete your account. Deleting an item removes it and everything derived from it.

Deleting your account removes your saves, collections, notes, conversations, rules and suggestions from our database. We do not keep a separate copy of your library afterwards.

We do not hold your invoices or payment details. Those sit with our payment provider, which issues the receipt and keeps its own records for as long as its accounting obligations require. On our side a subscription is only a plan name, a status and the dates of the current period, and those go when the account does.

Server logs and database backups exist so the service can be recovered after a failure. They are rotated in the normal course of running the service, so a deleted account can persist in a backup for a short period before that backup is replaced.

Depending on where you live you may have the right to access your data, correct it, export it, delete it, restrict or object to processing, and to complain to a data protection authority. We apply these rights to everyone, not only where the law compels us.

• Export. The app has a built-in export. You do not need to ask us for a copy of your library.
• Correction. Every AI-generated field is editable. If the AI got something wrong you can change it, and the change sticks.
• Deletion. Delete individual items in the app, or your whole account from Settings. Write to us if you would rather we did it for you.

To exercise any of these, write to support@nemivo.co. We answer within 30 days.

Traffic to the service is encrypted in transit. Passwords are stored as Argon2 hashes. Email verification and password reset links are stored as hashes, expire, and can be used once. Session cookies cannot be read by page scripts. Access to production systems is limited to the people who operate the service.

No system is perfectly secure. If you find a security issue, please write to support@nemivo.co before disclosing it publicly, and we will work with you on it.

Nemivo and its providers operate in several countries, so your data may be processed outside the country you live in. Where a transfer leaves a region with data protection laws such as the EEA or the UK, it is covered by the safeguards those laws require, typically standard contractual clauses agreed with the provider.

Nemivo is not directed at children. You must be at least 16 years old, or the minimum age of digital consent where you live if that is higher, to create an account. If you believe a child has created an account, write to us and we will remove it.

We update this page when the product changes. The date at the top always reflects the current version. If a change materially affects how your data is handled, we will tell you in the app or by email before it takes effect.

Questions, requests and complaints about privacy go to support@nemivo.co.

If you want the mechanical detail of what happens to a save and where the limits are, How it works spells it out.