1. Who we are
This service is published by Bubl, a sole proprietorship based in the United States ("we," "us," "our"). "You" means the person texting Nessi, visiting bubl.co, or using the Nessi App — our free app for iPhone and Android, also on the web at dashboard.nessi.chat. The app is the main way to use Nessi, and you can also just text her; nothing requires you to install the app.
For any privacy question, request, or complaint: support@bubl.co. A real person reads everything sent to that address.
2. Information we collect
Nessi only collects what's needed to text you back and remember you between conversations. The following is a complete list of information we (or a service provider acting on our behalf) receive:
- Your phone number. Required — it's the only way Nessi can text you back. We store it in our database in a one-way hashed form (so it can't be reversed) plus an encrypted form (so we can re-deliver replies). We don't have your name, your email, your address, or any other identifier unless you choose to tell Nessi during a conversation.
- Your messages and the assistant's replies. Stored so Nessi can remember context across conversations. Sent to the AI provider that generates each reply (see section 3). Not used for advertising, not sold, not shared with third parties beyond the providers listed below.
- A small profile and memory file. When Nessi learns useful things about you ("prefers vegan products," "buys gifts in June," "based in Lisbon," "is a beginner runner," "writes in a casual tone") it saves a structured profile and a short notes file so future conversations don't make you repeat yourself. You can ask Nessi to forget any of it at any time, or delete everything as described in section 7.
- Images you send. If you text Nessi a photo (for example, "find me this product," "what kind of plant is this," or "is this a typo"), the image is downloaded from the SMS provider's temporary URL, resized, and sent to an image-recognition model so Nessi can describe what's in it. The image bytes and Nessi's text analysis of them are both stored on our infrastructure and remain there until you ask us to delete them (see section 7).
- Voice notes you send. If you send an audio message, it is downloaded from the SMS provider, sent to a speech-to-text model (see section 3) to convert it to text, and Nessi reasons over the transcript the same way it would over a text message. The audio bytes and the resulting transcript are both stored on our infrastructure and remain there until you ask us to delete them.
- Documents (PDFs) you send. If you text Nessi a PDF — for example a school form, a schedule, or an appointment summary — the file is downloaded from the SMS provider's temporary URL and its text is read so Nessi can answer questions about it. For PDFs that can't be read from their text layer alone (such as scans), the document is sent to the AI provider to be read (see section 3). The file and the text read from it are both stored on our infrastructure and remain there until you ask us to delete them (see section 7).
- YouTube videos you share. If you send a YouTube link and ask Nessi about the video, Nessi fetches the video's transcript through a transcript provider (see section 3) and reasons over it the same way it would over text. The transcript is stored on our infrastructure for a short period and remains there until it expires or you ask us to delete it.
- Google account data (only if you connect). If you choose to connect Google so Nessi can help with Gmail or Calendar, we store an OAuth token (encrypted), your Google account email address, your Google display name, your Google account ID, and the list of permissions you granted. While the connection is active, Nessi reads Gmail messages and Calendar events on demand each turn to answer your request; we do not maintain a long-running copy of your inbox or your calendar. There are three exceptions. The first is the order details kept by package tracking, only if you turn it on (see the next item). The second is the daily summary: each time the Nessi App loads your day, the summary it shows you — your unread count, your next few events with their titles and locations, your next reminder, and the weather for the town we have for you — is saved so the home-screen widget can show it without waking your accounts. It is refreshed when the app next loads your brief, never kept longer than 26 hours, and disconnecting Google deletes it immediately. The third is the inbox brief: for each email it picks out for you, Nessi keeps the sender's name and address, a short summary, a topic, and suggested replies. These are kept for 14 days, and disconnecting a Google account deletes that account's items immediately. If you text
STOP GOOGLE, your OAuth token and Google profile fields are immediately erased from our database and the grant is revoked with Google; a non-identifying record that a connection once existed is kept so we can recognize a different Google account if you reconnect later.
- Outlook (Microsoft) account data (only if you connect). If you choose to connect Outlook — a personal Microsoft account or a work or school account — so Nessi can help with your mail, calendar and contacts, we store an OAuth token (encrypted, and used only for you), your account email address, your display name, the account and organization IDs Microsoft issues, and the list of permissions you granted. While the connection is active, Nessi reads your Outlook mail, calendar events, contacts, the list of people you email most, and your mailbox's time zone setting on demand to answer your request; as with Google, we do not keep a long-running copy of your inbox or your calendar, and the only stored order details are those of package tracking, if you turn it on. The inbox brief keeps the same items from your Outlook mail as from Gmail — the sender's name and address, a short summary, a topic, and suggested replies for each email it picks out — for 14 days, and disconnecting an Outlook account deletes that account's items immediately. Disconnecting Outlook (by asking Nessi, or in the Nessi App) deletes the grant we hold. After you disconnect, we keep only the account and organization IDs Microsoft issued, so a reconnect of the same account returns to its place; deleting your account removes them. Microsoft offers no way for an app to withdraw its own access, so to finish removing it, you remove Nessi from your Microsoft account yourself: at account.microsoft.com/privacy/app-access for a personal account, or at myapps.microsoft.com for a work or school account. Deleting your account deletes every Outlook account record we hold.
- Package tracking (only if you turn it on). If you turn on package tracking — by text or in the Nessi App — Nessi looks through your connected Gmail or Outlook mail for order and shipping emails so it can tell you when something ships and arrives. Connecting Google or Outlook does not start it on its own; you have to turn it on. For each shipment it keeps only: the store, at most one item name, the order and tracking numbers, the carrier, the delivery status and its timeline, an expected delivery date (only when the email gives one), the carrier's own words for where a parcel was left (for example "Front porch"), and a reference to the email it came from. The emails themselves are never stored, and no prices, totals or payment details are kept. Finished orders are deleted after 30 days, any other order after 60 days without an update, and we keep at most 200 orders per person. Everything is deleted at once when you turn tracking off, disconnect the Google or Outlook account the emails came from, or delete your account. If you never turn tracking on, we keep only two timestamps and no order details.
- Third-party app connections (only if you connect). Nessi can connect to certain third-party apps on your behalf through our integration provider, Composio (see section 3). If you choose to connect one, we store a small connection record — which app you connected, a connection reference ID issued by Composio, and the connection's status — so Nessi knows the app is available to you. The login credentials (OAuth tokens) that grant access to that app are held by Composio in their secure vault; we do not store those tokens in our database. You can disconnect at any time (see section 7), which revokes the connection at Composio.
- Scheduled reminders and routines. If you ask Nessi to remind you or to set up a routine ("every weekday at 7 send me a morning brief"), we store the intent text you wrote ("send me a morning brief"), the schedule, and the timezone so we can fire the reminder when it's due. Cancelled or completed reminders are hard-deleted from our database within 30 days.
- Operational logs. Standard hosting logs (timestamps, request IDs, error traces) plus an audit log of events like "message received," "reply sent," "memory saved." When an error occurs, a scrubbed diagnostic report is also retained by our error-monitoring provider, Sentry (see section 5). These are retained for debugging and abuse prevention; they do not include the content of your messages.
- The Nessi App (only if you use it). The app shows you things Nessi already holds — your day, your reminders and routines, your lists, your notes, what Nessi remembers about you (including things you have told it about other people), your calendar events with their titles, guests and locations, and your Google profile picture. The app is almost entirely a window: everything it displays is described elsewhere in this list, and was already stored because you told Nessi (by text or in the app's chat) or because you connected Google or Outlook. The one thing using the app creates is the saved copy of your daily summary described in the Google bullet above — opening the app is what writes it, so the home-screen widget has something to show. It contains nothing that was not already on your screen. Signing in uses your phone number and a one-time code texted to you by our verification provider (see section 4) — no separate account, no email address, no password. If you turn on notifications, your device's push token — a random identifier Apple or Google issues so a notification can reach your phone — is stored with your account so we can send you replies and reminders; it says nothing else about you and is deleted when you delete your account. On your device the app keeps three things and nothing else: a marker that you are signed in, whether you chose light or dark appearance, and (on the web only) a count behind the "add to home screen" prompt. On iPhone the credential that keeps you signed in is held in the iPhone's own Keychain, marked so it cannot travel to another phone inside an encrypted backup. None of that is sent to us, and none of it is about you.
- Support email. If you email us, we see what you send. We keep it only as long as we need it to help you.
- Pictures Nessi makes for you. When you ask Nessi to make or change a picture — in a text or in the Nessi App — the picture and each version of it are stored so you can come back to it, together with a short title and what you asked for. A photo you upload in the app to make a picture from is stored with that picture and nowhere else. Before a photo you send or upload is used or sent to a provider, its hidden location and camera data (EXIF, including GPS) is removed. Pictures are kept until you delete them; in-between versions you replaced go 30 days later, and a picture made in a group chat goes 90 days after its last change. Deleting a picture moves it to Recently deleted for 30 days, where you can bring it back; after that, all its versions, the photo it was made from (if you uploaded one) and our stored copies of it are permanently deleted.
That list is exhaustive — the saved daily summary and, if you turn it on, the package-tracking order details named in it are the only copies of anything we keep beyond what each bullet describes. We don't collect your contacts (other than what you explicitly tell Nessi, or what Nessi looks up in Google or Outlook if you connect one), your physical location, your web-browsing history, or anything else beyond what you put into a message to Nessi.
A note on sensitive topics. Because Nessi can help with more than just shopping — research, advice, decisions, ideas — you may at times share information that feels personal: health questions, financial situations, relationship matters, things you're worried about. Anything you tell Nessi is handled the same way as any other message described above (stored in our database, sent to the AI provider to generate a reply, never sold or used for advertising), but please use your judgment about what you're comfortable sharing over SMS to a third-party service. If you'd rather not have something remembered, tell Nessi to forget it, or delete everything as described in section 7.
3. How AI is used
Every reply Nessi sends is generated by a large language model. We use commercial AI APIs rather than running models ourselves. When you text Nessi, the contents of the conversation (your messages and the assistant's prior replies, plus any email or calendar items from a connected Google or Outlook account that you asked about) are sent to the AI provider so the model can produce the next reply.
The providers Nessi uses are:
- Anthropic (Claude). Generates the conversational replies. When you send a photo, the image is also sent to Anthropic for recognition so Nessi can describe what's in it. When you send a PDF that can't be read from its text layer alone (such as a scan), the document is also sent to Anthropic to be read. We send all of this under Anthropic's commercial API terms, which state that API inputs and outputs are not used to train their models.
- Tavily. Used to search the web for results when Nessi looks something up. Tavily sees the search query Nessi generates (which may paraphrase what you asked for) and returns ranked URLs and snippets. Tavily does not see your phone number or your raw conversation.
- Firecrawl. Used to fetch the contents of specific web pages on your behalf once Tavily has returned the URLs — for example, a product page when you're shopping or a reference article when you're researching. Firecrawl sees the URLs it is asked to fetch. Firecrawl does not see your phone number or your raw conversation.
- Cloudflare Workers AI (speech-to-text). When you send a voice note, the audio is transcribed by Cloudflare's open-source Whisper model running on Cloudflare's Workers AI platform. Cloudflare processes the audio under its own privacy policy and the resulting text is returned to Nessi.
- OpenAI and Google (image making). When you ask Nessi to make or edit an image, the description Nessi writes for it is sent to one of these providers to produce the image, together with any photo or picture it works from: the one you asked it to change (including a photo you upload in the Nessi App to make a picture from), and any you gave it to take a look or a likeness from when making something new — including for an invite or card. The words on an invite or card are sent too, because the image service paints them. (A photo placed as-is on an invite is added by Nessi afterwards and is not sent to them.) Photos are sent without their hidden location and camera data. We send this under their paid API terms, which state that API inputs and outputs are not used to train their models. They do not see your phone number or the rest of your conversation.
- Open-Meteo (weather). When you ask about the weather, the place name you mention (for example "Denver") is sent to Open-Meteo to look up current conditions and the forecast. Open-Meteo sees only that place name — not your phone number or your conversation.
- Google Maps Platform (places). When you ask where somewhere is — a shop, a restaurant, a landmark — the place you described is sent to Google's Places service so Nessi can return the real name, address and coordinates instead of guessing them. Google sees the text of the place you asked about and nothing else: not your phone number, not your conversation, not who you are. Be aware that this text is whatever you wrote, so if you ask Nessi for directions to a friend's house and include their address, that address is what gets sent. Nessi does not keep a copy of what Google returns; it uses the answer to reply to you and looks it up again next time. This is separate from connecting your Google account — it uses Nessi's own key, not your login, and happens whether or not you have connected Google.
- Supadata (video transcripts). When you share a YouTube link and ask Nessi about the video, the video's identifier is sent to Supadata to fetch its transcript so Nessi can respond to what was actually said. Supadata sees the video reference, not your phone number or your conversation.
- Bubl CX (what a shop currently offers). Some businesses publish to Nessi through Bubl CX, our sister service for shops. Nessi asks Bubl CX in two situations, and both send your question rewritten in plain words — for example "a gift for a six-year-old who likes dinosaurs". When you name a business that publishes to Nessi, that business’s identifier goes with the question so it can answer with what it actually stocks right now. When you name no business at all — "somewhere for dinner Friday", "who does alterations", "what comes in the ProLash start kit" — Nessi first asks Bubl CX which businesses offer that kind of thing, naming none, and then asks some of those businesses what they have. Which ones it goes on to ask depends on what you were after. If the answer has to be somewhere you can actually get to, Nessi narrows them to the ones near you — working that out on its own machines, from addresses those businesses published, and never by sending your location anywhere. Your location itself stays with Nessi, but be aware that the shortlist is itself a rough clue to it: Bubl CX can see which of the businesses it suggested were asked about and which were skipped, and on this kind of question that difference is distance, so it narrows down roughly what part of town you are in. If you were asking about a product or a brand, where you are has nothing to do with the answer, so no location is involved at all: none is looked up, none is used, and the businesses are simply the ones Bubl CX ranks highest for the question. Either kind happens without you asking for a particular shop, so it can happen on a message you did not think of as a lookup. Your own words can appear in the question, because a product or brand name is what makes the answer useful — and, as with the places service above, the question is whatever the assistant restates from what you wrote, so if you say "somewhere for dinner in Ponsonby" then the neighbourhood is part of what gets sent. Nothing else about you goes with it: not your phone number, not a hash of it, not your name, not anything you said earlier, and never where you are. Bubl CX does not keep the question. To produce its answer, Bubl CX passes the question to Anthropic, the same AI provider described above and under the same commercial terms. None of this involves a business we wrote the entry for ourselves — those are answered from the stored entry, and nothing is sent anywhere.
- Kernel (browser actions). When a task needs a real website rather than a purpose-built API — filling in a form, completing a purchase, logging into a site you asked Nessi to use — Nessi uses Kernel, our browser-automation partner. Kernel runs isolated, cloud-based browser sessions that carry out those steps on Nessi's behalf, and the sessions are deleted when the work is done. When a site requires a login, that login is handled inside Kernel — Nessi never sees, receives, or stores your passwords, credentials, or login information. There is one exception, and it only happens if you choose it: you can take control of the Kernel browser yourself — for example, to type your own password into a site's sign-in page. While you do, what you type travels from your device to Kernel's browser through our servers, encrypted in transit with TLS. We pass it straight through: it is never stored, never logged, and never reaches Nessi or your conversation. This is the only case in which a password or similar private information you enter passes through us; in every other case we never see it at all. Depending on the task, the data Nessi needs to complete it can reach Kernel: for example the name or email address you gave Nessi to fill in a form, or preferences you've told Nessi (a size, a delivery preference) to pick the right option on a page. Kernel does not see your phone number or the rest of your conversation. Kernel is SOC 2 Type II certified and HIPAA-compliant, and processes this data under its own privacy policy.
- Shipping carriers (package tracking only). If you turn on package tracking, the order and shipping emails it finds are read by our AI provider, which pulls out only the order details listed in section 2. To keep the delivery status current, the tracking number is then sent to that shipment's carrier (for example UPS or DHL) through its tracking service. Carriers receive the tracking number only — not your phone number, your name, your emails or your conversation.
We do not share your data with these providers for advertising or marketing purposes — only for the technical purpose of generating the reply you asked for.
If you have connected Google, we additionally talk to Google's Gmail and Calendar APIs on your behalf — to read messages and events when you ask about them, and to make changes you ask for. Not every change works the same way:
- Nessi asks you first, every time, before sending mail from your account. That means a new email, a reply, or a forward. Nessi shows you who it's going to and the text it wants to send, and nothing leaves your account until you reply to approve it. These are words written in your name to another person, so they never happen on Nessi's own judgment.
- Everything else happens when you ask for it, without a second confirmation step, unless it would email other people — then Nessi asks first. That covers creating, changing, deleting, and RSVPing to Calendar events, and archiving, trashing, or changing the labels on Gmail messages; a calendar change that would send an invitation, update or cancellation to other people is shown to you first. You asked for it once; making you approve it again is just a slower way to get the same result. Nessi does it and then tells you what it did, naming the items it touched — the event, or the subject lines it archived — so you can see exactly what changed and ask Nessi to reverse it if it got something wrong. One honest limit: reversing a deleted calendar event means creating it again, which sends a fresh invitation to anyone who was on it.
Nessi does not tidy your inbox or your calendar on its own initiative: every change traces back to something you asked for, either in the moment or in a routine you set up yourself. Google's handling of your data is governed by their privacy policy; you can review and revoke our access at any time on your Google Account permissions page or by texting STOP GOOGLE.
If you have connected Outlook, the same rules apply to your Outlook mail and calendar, which we reach through Microsoft's APIs on your behalf. Sending, replying and forwarding happen only after you say yes. Archiving, deleting, moving or otherwise organizing mail, and adding, changing, deleting or answering calendar events, happen when you ask, unless it would email other people — then Nessi asks first. Either way, Nessi then tells you what it changed. Microsoft's handling of your data is governed by its privacy statement. You can disconnect Outlook at any time by asking Nessi or in the Nessi App, which deletes the grant we hold; because Microsoft offers no way for an app to withdraw its own access, you remove Nessi from your Microsoft account yourself: at account.microsoft.com/privacy/app-access for a personal account, or at myapps.microsoft.com for a work or school account.
If you connect a third-party app, Nessi uses Composio as its integration provider to handle that connection. Composio is an integration platform that manages the secure login (OAuth) to the apps you choose to connect and runs the actions you ask Nessi to take in them. When you connect an app, Composio brokers the login and stores the resulting access credentials in its own secure vault; when Nessi performs an action you've asked for, it sends Composio a non-identifying user reference (a one-way hash of your phone number — never the number itself), the connection reference, and the details needed for that action, and receives back the result. Composio sees the data involved in those actions but processes it under its own privacy policy, which states it does not use the data for advertising or to train AI or machine-learning models. This applies only to apps you have explicitly chosen to connect, and you can disconnect at any time (see section 7).
4. SMS delivery
Text messages reach Nessi through an SMS provider, which acts as the carrier between your phone and our servers:
- Sendblue. Our SMS / iMessage provider. Sendblue sees your phone number, the contents of every message you send to Nessi, and every reply Nessi sends back — this is unavoidable for any SMS-based service. They process this data under their own privacy policy. Your mobile carrier also sees that messages are being exchanged with our number, the same as any other text.
- Twilio (sign-in codes only). The one-time code you use to sign in to the Nessi App is generated and sent by Twilio's Verify service, not by Nessi's own number — which is why it arrives from an unfamiliar number and does not mention Nessi. Twilio receives your phone number in order to text you that code, and creates the code, checks the one you type, and expires it on their side; we never hold it. Twilio does not see your conversations with Nessi, and this happens only when you ask to sign in to the app. They process your number under their own privacy policy.
Note on attachments: when you send an image, Sendblue temporarily hosts it and gives us a URL to download it. The image is publicly accessible at that URL for the duration of Sendblue's retention window (typically about 30 days) before being deleted on their side.
5. Hosting and storage
Nessi runs on:
- Cloudflare. Hosts our application (Cloudflare Workers), stores conversation history, your profile, your audio transcripts, your encrypted Google and Microsoft OAuth tokens (if you connected Google or Outlook), and your scheduled reminders (Cloudflare D1, a SQLite-compatible database), stores your memory notes and any uploaded image, audio, or document (PDF) bytes plus video transcripts (Cloudflare R2 object storage), holds the short-lived caches that keep Nessi fast — including the saved copy of your daily summary the home-screen widget reads (Cloudflare KV) — routes our AI requests through an AI Gateway, and serves this website (Cloudflare Pages). Cloudflare can technically see what passes through and what's stored, the same way any cloud provider can — they process this data under their own privacy policy and do not use it for advertising.
- Google Ads (advertising measurement — on getnessi.ai only). Our advertising landing page at getnessi.ai loads Google's tag (
gtag.js) so we can tell whether someone who clicked one of our ads went on to text Nessi. Google receives the usual information a website visit sends — IP address, browser and device details, the page you landed on, the ad you came from — and stores identifiers (cookies or their equivalent) in your browser to link the click to the visit. Depending on our Google Ads account settings, Google may also use this to show you our ads again elsewhere. Google processes all of it under its own privacy policy; see also how Google uses information from sites that use its services, and Google's own ad settings to opt out of personalized advertising. This is website measurement only. It runs on that one marketing page, before you have texted anyone. It is not connected to your conversations with Nessi, your phone number, your profile, or anything Nessi remembers — none of that is ever sent to Google. bubl.co carries no analytics, tracking pixels, or advertising tags of any kind.
- Sentry. Our error-monitoring provider (US-based). When something goes wrong inside Nessi, a diagnostic error report — the type of error, a stack trace, the release version, a timestamp, and a non-identifying per-turn reference — is sent to Sentry so we can detect and fix failures. This is scoped to errors only, not a general log of your activity. The content of your messages, your phone number, and your profile and memory are scrubbed before any report is sent and never reach Sentry — only structural, technical error details do. Sentry processes this under its own privacy policy and does not use it for advertising.
6. What we don't do
For clarity, here is a list of things Nessi does not do, that other "free" services sometimes do:
- We do not sell your data to anyone.
- We do not show you ads. We don't have an ad product.
- We do not take undisclosed money from merchants, brands, or anyone else to influence what Nessi recommends or how it answers. If a recommendation ever contains an affiliate link, this page will be updated to say so before any such links go live.
- We do not use your conversations to train AI models. Neither do we, nor do the AI providers we use (under their commercial API terms).
- We do not embed analytics, tracking pixels, advertising SDKs, or cookies on this website (bubl.co), and none inside the signed-in Nessi service. The Nessi App for iPhone contains no analytics and no third-party tracking of any kind — not a reduced amount, none: no measurement identifier exists in the app at all, and an automated check fails the build if one is ever added. On the web version, Google Analytics runs only on the signed-out screens of the production site — never once you are signed in, and never on any screen showing your own information. The one exception, disclosed in full in section 5, is our separate advertising landing page at getnessi.ai, which carries Google's advertising tag so we can measure whether an ad click led to someone texting Nessi. That tag never sees your conversations, your phone number, or anything Nessi remembers.
- We do not send marketing texts, win-back drips, or upsells. The only messages Nessi sends that aren't a direct answer to something you did are the reminders and routines you explicitly asked us to schedule (for example, "every weekday at 7 give me a morning brief"); Nessi saves each one the moment you ask for it and then reads it back to you, so you can see the exact time and wording it stored and correct it if it got them wrong.
7. Your rights and how to use them
Depending on where you live, you may have rights under the General Data Protection Regulation (GDPR, EU/UK), the California Consumer Privacy Act (CCPA/CPRA), or a similar law. These typically include the right to:
- Know what personal information we hold about you;
- Request a copy, correction, or deletion of that information;
- Object to or restrict certain processing;
- Withdraw consent at any time; and
- Lodge a complaint with your local data protection authority.
You can use the following self-serve tools at any time:
- Ask Nessi what it remembers about you. Just text something like "what do you remember about me?" — Nessi will list the facts and notes it has stored.
- Ask Nessi to forget specific things. Text "forget that I'm vegan" or "forget my sister's birthday" — Nessi deletes the matching items from your profile and memory notes straight away, then tells you exactly what it removed, so you can see whether it took too much or too little and say so.
- Disconnect Google. Text
STOP GOOGLE to permanently erase the OAuth credentials we hold and revoke our access to your Gmail and Calendar.
- Disconnect Outlook. Ask Nessi to disconnect your Outlook account, or disconnect it in the Nessi App. This permanently erases the OAuth credentials we hold for it. Microsoft offers no way for an app to withdraw its own access, so you remove Nessi from your Microsoft account yourself: at account.microsoft.com/privacy/app-access for a personal account, or at myapps.microsoft.com for a work or school account.
- Disconnect a third-party app. If you've connected a third-party app through Composio, ask Nessi to disconnect it (or request full deletion below). This removes our local connection record and revokes the connection — including the access credentials Composio holds — at Composio.
- Turn off package tracking. Ask Nessi to stop tracking your orders, or switch it off in the Nessi App. Every order we stored for you is deleted straight away.
- Delete a picture Nessi made. Ask Nessi to delete it, or delete it in the Nessi App. It moves to Recently deleted for 30 days, where you can bring it back (ask Nessi, or use the app); after 30 days all its versions and our stored copies of it are permanently deleted. Pictures already sent in a message stay on the phones that received them, and a print link Nessi sent keeps working while the picture is in Recently deleted. In the app you can delete a picture from a one-to-one chat for good straight away. A picture made in a group chat stays in Recently deleted for up to 30 days — any member of the group can bring it back — and is then gone. A photo you uploaded in the app to make a picture from is kept, moved and deleted with that picture.
- Stop receiving messages. Text
STOP to opt out of any further messages from Nessi. Important: the STOP keyword is an opt-out only — it does not by itself delete your conversation history, your profile, your memory notes, the images or voice notes you sent, your tracked orders, or any other stored data. If you want full erasure, see the next bullet.
- Delete your account yourself, from the app. In the Nessi App, open the You tab and choose Delete my account. You are asked to confirm, because it cannot be undone. It happens immediately and signs you out on every device.
- Or ask us to delete it. Email support@bubl.co from the number or address associated with your account and ask for full deletion. Either route runs the same erasure and reaches the same things: every message and reply; every list, note, reminder and routine; every tracked order; everything Nessi remembers about you, including things it noticed in group chats you were part of; every photo, voice note, PDF and document you sent and every file and picture Nessi made for you — including pictures in Recently deleted, deleted at once — along with the transcripts and analysis of them; your Google connection and every other connected app, switched off at that company as well as here; every Outlook account record (Microsoft offers no way for an app to withdraw its own access, so remove Nessi from your Microsoft account yourself, as section 2 describes); your profile, timezone and saved location; and every device you are signed in on. It is immediate and there is no undo. Two things are deliberately kept, and both are for a reason. The first is a record that a deletion happened, with no content in it — counts only, no messages, no names. It is what lets us show we did what you asked. The second applies only if you used Nessi in a group chat: the group keeps its own shared notes, its member list, and the display name you used in it, because that material belongs to the room and the other people in it, not to any one member — erasing it would tear holes in a conversation they were also part of. What Nessi learned about you from those group chats is deleted along with everything else; what stays is the room's own record that you were there, under the name you used. If you want that removed too, email us and say so. Texting Nessi again afterwards starts a brand-new account with nothing carried over. If you email rather than using the app, write from the number or address associated with your account; we confirm by email when it is done, and we respond within 30 days, usually much sooner.
We do not sell your personal information and we do not share it for cross-context behavioral advertising, as those terms are defined under the CCPA/CPRA.
8. Children
Nessi is for adults 18 and older and is not directed to anyone under 18. We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has provided us information, contact support@bubl.co and we will delete it.
9. Security
Our primary security measure is minimization: by not collecting an account, an email address, a payment method, or any data beyond what you choose to share inside a message, the amount of information an attacker could obtain from us is inherently small.
For the data we do hold: phone numbers are stored as a one-way hash plus an AES-256-GCM encrypted reversible form, with four separate secret keys (one for the hash, one for phone-number encryption, one for Google OAuth-token encryption, one for Microsoft OAuth-token encryption) so that compromise of any single key does not unlock the others; message history, profile, audio transcripts, encrypted Google and Microsoft OAuth tokens, and scheduled reminders are stored in Cloudflare D1; memory notes and any image, audio, or document (PDF) bytes and video transcripts are stored in Cloudflare R2 with access scoped to our application. If you take control of a Kernel browser session to type a password yourself (see section 3), what you type passes through our servers only in transit to Kernel, encrypted with TLS, and is never written to storage or logs. We rely on Cloudflare's security program for the underlying infrastructure. No system is perfectly secure, and we cannot guarantee absolute security of any information.
10. International users
The publisher is based in the United States. The SMS number is a US number. If you text Nessi from outside the United States, the information we hold may be processed in the United States or in other countries where our service providers operate. Where required, we rely on the standard contractual clauses or equivalent transfer mechanisms offered by those providers.
11. Changes to this policy
We may update this policy from time to time. Minor edits (clarifying wording, fixing typos, updating a link) take effect when posted. Any material change — for example, adding a new type of data collection, or weakening one of the core privacy guarantees in the summary above — will be announced on this page at least 30 days before it takes effect, and the effective date below will be updated.
Upcoming change. This version takes effect on December 9, 2026; until then, the version effective October 25, 2026 applies. It adds a short record kept for the Nessi App suggestions (section 2), lists every message Nessi sends without being asked, including at most two suggestions of our free app (section 6), adds Outlook (Microsoft) as an account you can connect (sections 2, 3, 5 and 7), and says what the inbox brief keeps from your mail and for how long (section 2).
For any question about this policy, to exercise a privacy right, or to tell us you think we're doing something wrong, email support@bubl.co.
Effective December 9, 2026. Last updated November 10, 2026.