Legal
Privacy Policy
Effective Last updated
This policy covers Nellie, provided by Anello: the assistant, this website, and the messaging service you can reach it through. It explains what we collect, why, and who does and doesn't get to see it.
1. Who we are
Nellie is provided by Anello, operated by Erik Hope, doing business as Mirabelle Studios ("we", "us"). You can reach us at support@anello.co.
Nellie is a hosted assistant for the adults running a household, reached by message or at your household's own email address. This policy describes that service, including our websites at anello.co and meetnellie.co: the signup form, the number we message you from, and what Nellie remembers for you.
2. Messaging
Opting in
You can start by texting Nellie or chatting with her on our homepage. Your first text opts you in to replies about signup and the help you request. SMS signup uses a private form linked to that number. Homepage chat’s setup links open a fresh text to Nellie. The web preview does not transfer into that text conversation. Previously issued homepage signup links still accept a number you enter yourself with no phone verification code. Opening the website chat or entering a number does not opt that number in to texts. We do not buy, rent, or import phone number lists, and we never send marketing or promotional messages.
Before signup, a limited AI assistant responds to your messages and offers the signup link. We save a bounded transcript of your messages and the replies sent to you, not a model-written summary. Older content may be trimmed when the limit is reached. When you complete SMS signup, the saved SMS transcript is passed to your household’s Nellie so she can continue the conversation by text. If you use a previously issued homepage signup link, that saved web transcript is passed along instead, and Nellie waits until you text her. The browser chat uses temporary tab storage for its private conversation link, retry identifiers and unsent message. Keep the signup link private: it carries access to the conversation. The link expires after seven days.
How the messages reach you
We send through a messaging provider that delivers over Apple's iMessage where your device supports it, and falls back to a standard text message where it doesn't. You don't choose or configure this; it's decided by the phone at the other end. Either way it arrives in the ordinary Messages app, and either way the parts below apply.
What we send, and how often
We send replies to what you send Nellie, plus alerts and reminders you set up yourself or that Nellie creates from Gmail context you authorize. These might be a price you're watching or a deadline to remember. How often varies entirely with how you use it. Nellie answers when you message it and sends relevant alerts and reminders. There is no fixed messaging schedule and no broadcast.
Cost
We never charge you for messages. Messages delivered over iMessage use your data connection. Where a message falls back to a standard text, message and data rates may apply. That's between you and your mobile carrier, so check your plan. Neither we nor any carrier can guarantee a message arrives on time, or at all.
Stopping messages, and getting help
Reply STOP at any time to stop all messages. We will send one confirmation and then nothing further. Reply START to resume, or HELP for support information. You can also email support@anello.co, which reaches us the same way.
Your mobile number is not shared
We do not share your mobile number, or the fact that you consented to messages, with any third party for marketing or promotional purposes. Not with advertisers, not with data brokers, not with affiliates, and not with anyone else. We do not sell it and we do not rent it.
The only parties that ever touch your number are the providers who have to handle it to deliver a message to your phone, and they act for us under contract and may not use it for anything else. They're listed in Who we share it with.
3. What we collect
Nellie receives what you send it and, if you choose to link Gmail, reads email with your authorization. Linking is optional; forwarding emails is another way to share context. Gmail access is read-only: it does not let Nellie send email from your account or change your connected calendars.
- Signup details
- Your name, email address, the household name you pick, and the invite code you arrived with: the fields on the signup form. The form also creates a random request identifier so retrying it cannot create a second signup. We use the household name to identify your Nellie, and the email to reach you about your account when a message isn't the right channel.
- Mobile number
- The number you register or message us from, plus the date, time, and method of your opt-in and any later opt-out. We keep the consent record because we have to be able to show that you agreed.
- Household membership details
- The email addresses, mobile numbers, names, and household roles added in Nellie's household settings. We use them to identify who may contact a household and keep a current operational record of that roster.
- Message content
- What you send Nellie and what it sends back, by message or by email at your household's address. This is the substance of your request, so Nellie needs it to answer.
- Linked Gmail data
- If you authorize Gmail linking, Nellie can read message headers (such as sender, subject and date) and message bodies to find relevant context. This supports searches you request and a bounded daily review of the previous day's email for useful plans and reminders, not continuous or exhaustive inbox monitoring. Selected facts can become notes, reminders and household context, which may be visible to other household members. We also keep connection identifiers, status and operational records to manage access and disconnection.
- Message metadata
- Timestamps, delivery status, and any error returned by the messaging provider or, where a message goes as a standard text, the carrier.
- What you ask Nellie to remember
- Notes, reminders, watch requests, and project documents you create by asking for them. Nellie is built to keep these across conversations; that is the feature, and it means the content persists until you delete it.
- Your agreement
- That you ticked the terms box, when, and which version of the terms was in force at the time. We keep it because "you agreed" is worth little without a record of what you agreed to.
- Technical details of the request
- When you submit either form we store the IP address it came from and your browser's user-agent string, alongside the submission. It's there to investigate abuse and to work out what happened when something goes wrong, and nothing else reads it.
- Website analytics and advertising measurement
- Cookie-free aggregate pageview and welcome-page outcome counts, plus cookieless Google Ads measurement of homepage SMS-link clicks. Google receives a public homepage address, event information, IP address and browser request information, not your mobile number or message content. See This website.
We do not collect your contacts, your location or your photo library. You do not give Nellie your Gmail password; authorization credentials are managed through Nango, as described below. A photo or document you choose to send Nellie is message content, described above, and Nellie has the ones you sent it and no others.
4. How we use it
We use what we collect only to:
- Answer you, and send alerts and reminders you request or Nellie creates from Gmail context you authorize.
- Keep the notes and documents you asked Nellie to keep, and use authorized Gmail content for relevant context, notes and reminders.
- Prove your consent to receive messages, and honor opt-outs.
- Diagnose delivery failures and keep the service running.
- Prevent abuse of the number, and comply with law.
- Measure homepage SMS-link clicks and estimate advertising results, not whether a message was sent or signup completed.
We do not use your messages or your number to advertise to you, and we do not sell your information. We do not use your message content to train AI models.
5. Who we share it with
We share information with a small set of providers who process it on our behalf, only to the extent they need it to make the service work, and only under agreements that bar them from using it for their own purposes, except for Cloudflare's use of Turnstile security signals to improve its bot detection and Google's processing of cookieless advertising measurement under its own terms, as described in §9. The providers that deliver your messages and email are listed first.
- Messaging provider
- A message cannot reach your phone without one. Our messaging provider receives your number and the content of the message in order to deliver it, over iMessage or as a standard text. It does not only pass them through: like any messaging service it keeps its own delivery records, so your number and the text of your messages are stored on its systems as well as ours, for as long as its own retention policy says. Where a message goes out as a text, the mobile networks carry it the last stretch, the same as any message you send yourself.
- Email provider
- Mail is the same story. Anything Nellie emails you, and anything you send to your household's address, passes through an email provider, which receives your email address and the contents of that mail in order to deliver it, and likewise keeps its own copy in its delivery records. That includes the invite and welcome mails we send when you sign up.
- Gmail connection provider (Nango)
- When you link Gmail, Nango manages the connection, OAuth authorization credentials and token refresh. Our Gmail read requests are proxied through Nango, so Nango handles the requests and email data returned by Google, not just credentials. Our server also briefly accesses an authorization token to revoke Google's access grant when you disconnect. See Nango's security information and Nango's Privacy Policy.
- AI model provider
- Nellie sends the content of your request to the AI model that generates the reply. Your phone number is not sent with it. Model providers we use are under terms that prohibit training on the content we send, and the models we use are hosted in the United States, so the content of your requests is not processed abroad. Relevant content read from linked Gmail is also sent to AI providers for filtering and to help with replies, context, notes and reminders.
- Bot protection
- Cloudflare Turnstile helps protect our public pre-signup website chat and forms from automated abuse. Cloudflare also uses Turnstile security signals to improve its bot detection, as described in This website. We do not send chat messages or form contents to Turnstile.
- Google Ads (cookieless website measurement)
- Google processes cookieless event and browser request information for conversion measurement under Google’s Privacy Policy and Google Ads Data Processing Terms. This is separate from linked Gmail. We disable advertising personalization and enhanced conversions and do not send mobile numbers, message content or signup information.
- Infrastructure
- Our hosting provider runs this website, the code behind the two forms, and the database those submissions are stored in, along with the servers Nellie itself runs on. There is no third-party form service in the middle: the forms post to our own code, on our own domain, and what you type goes straight into our own database. The hosting provider holds it at rest on our behalf and may not use it for anything else.
- Legal
- If we are legally compelled by valid process, or where disclosure is necessary to protect someone's safety or our rights.
To restate the point in §2, because it is the one that matters most: your mobile number and your consent to messages are never shared with any third party for marketing or promotional purposes. The providers above handle them only to run the service, and only under contract.
We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are used in US state privacy laws.
6. How long we keep it
If you do not complete signup, your pre-signup session and saved transcript are scheduled for deletion after 30 days of inactivity. If you complete signup, the frozen signup transcript is retained with your signup record and household context until you ask us to delete it. We retain a message-free usage counter associated with a hashed phone identifier to enforce the total SMS pre-signup conversation limit even after an inactive transcript is deleted. Browser chat working history and retry records are deleted after 30 days of inactivity, including after signup; the frozen signup transcript is kept as described above. Delivery and consent records follow the rules below.
Message content, including retained content read from linked Gmail, and the notes and context Nellie keeps stay until you delete them or ask us to. Disconnecting Gmail does not delete previously retained content, notes or reminders. Delivery metadata is kept for up to 12 months for troubleshooting. Records of your opt-in and opt-out are kept for as long as we operate the messaging service, and for at least four years after, because messaging regulations require us to be able to evidence consent. If you opt out, we retain your number on a suppression list; that is what guarantees we don't message you again.
Copies our providers hold
The times above are ours. The providers in Who we share it with keep their own processing or delivery records, and those run on their retention schedules, not this one. In practice that means a message or an email can still exist in a provider's logs for a while after we have deleted our copy of it. Each of them is under contract to use what they hold only to run the service for us, and never for their own purposes, except for Cloudflare's use of Turnstile security signals to improve its bot detection and Google's cookieless advertising measurement processing described in §9. We ask providers to delete on request where their systems allow it. We would rather write that down than let "deleted" sound more absolute than it is.
Our Google Ads integration does not store advertising cookies or a saved advertising preference in your browser. Google retains measurement records under its own policies, not our message-retention schedule. Blocking future measurement does not delete records already received by Google.
Closing your account
Ask us to close your account and everything Nellie holds for you is deleted from our servers: your messages, the notes and documents it kept, your lists, and your mobile number. That is the substance of it, and it does not come back. Copies sitting in a provider's delivery logs age out on their own schedules, as described just above.
Three narrow things outlive the account, and we would rather say so than imply otherwise:
- Your household name. Names are claimed permanently, as the terms describe, so the name is not released to anyone else. We keep the name itself for that reason, with nothing attached to it.
- The consent record. That you opted in, when, and how, which messaging regulations require us to be able to evidence for at least four years.
- The suppression entry. If you asked us to stop messaging you, the record of that is the thing that keeps the promise.
None of the three is used to contact you or to build any profile of you, and none of them contains your message content.
7. Your choices
- Advertising measurement. Enable Global Privacy Control (GPC) in a supporting browser to prevent our Google Ads tag from loading. Browser tracking blockers can also block it. Texting and signup work without measurement. You can also use Google’s advertising controls.
- Stop messages. Text STOP. It takes effect immediately.
- Disconnect Gmail. Use the connected-account controls in Nellie Home Settings. Nellie disables further reads when disconnection starts. A confirmed disconnect revokes the connected app's Google authorization and deletes the Nango connection; an unfinished disconnect may need a retry or support. Google may take time to apply revocation everywhere. You can also review or revoke app access in your Google account settings. Previously retained content follows our retention rules.
- See what we have. Email us and we'll send you a copy.
- Delete it. Email us and we'll delete your data. See Closing your account for the three narrow records that outlive an account, and why.
- Correct it. Tell us what's wrong and we'll fix it.
Depending on where you live, you may have these rights under law, including under the California Consumer Privacy Act or the GDPR. We extend them to everyone regardless. We will not discriminate against you for exercising them. Write to support@anello.co and we'll respond within 30 days.
8. Security
Your data is encrypted in transit and at rest. Everything we hold on our own servers is encrypted on disk: the database with your signup details, your mobile number and the record of your consent, and the storage behind the messages, lists and notes Nellie keeps for you. Access to the systems holding message content is limited to those who need it to operate the service. Nellie's own runtime is deliberately constrained: it runs in a container, confined to its own workspace, and by default cannot read the credentials it runs under. No system is perfectly secure, and a message that falls back to a standard text is not an encrypted channel: treat those as you would a postcard, and don't send Nellie anything you would not want a carrier to hold.
9. This website
We use Cloudflare Turnstile to protect our public pre-signup website chat and forms. These checks can run in the background without a visible widget. Turnstile processes your IP address, browser information and details of the site you visit to detect and block bots on our website. Cloudflare also processes these security signals independently to improve its bot detection. See Cloudflare's Turnstile Privacy Addendum for details.
Our websites at anello.co and meetnellie.co use PostHog, hosted in the United States, to count pageviews and whether the welcome page shows the texting button or reaches its one-minute setup timeout. Our integration sets no cookies and sends a fresh random identifier for each page load, without linking visits. It sends only the event type, page name and site address, not URL query strings, invite codes, form values, phone numbers, or referring pages. We do not enable session replay or automatic interaction tracking, and we disable IP-based geolocation enrichment. Fonts are served by Google Fonts. Turnstile runs the bot-protection checks described above. Each of these services, including PostHog, receives your IP address as part of the request, as any server does. Our forms post to our own code on this domain rather than to a third-party form service.
The public homepage uses Google Ads to measure SMS-link clicks without advertising cookies. Google’s advertising and analytics storage settings remain denied; we do not enable them later. We disable enhanced conversions, personalized advertising and URL passthrough, and enable Google’s ad-click identifier redaction. We do not save an advertising choice or identifier in browser storage. No cookie-consent banner is shown for this integration. This does not mean no data reaches Google: its tag can send cookieless configuration and measurement requests on page load, and a conversion event when you activate an SMS link. The event has a fixed value of USD 1; it does not establish that you sent a message or completed signup.
Google receives event and storage-setting information, a public homepage address, IP address, browser request information and temporary page-load identifiers. Measurement can be less complete and may contribute to modeled advertising results. We configure a canonical homepage URL without query parameters and redact ad-click identifiers. To avoid sensitive browser metadata, we do not load the tag when the landing URL contains parameters other than validated Google click IDs, an unknown fragment, or a referrer with a non-root path, query or fragment. The fixed public section anchors (main, privacy and signup) are allowed. Empty or HTTPS origin-only referrers are allowed; Google may receive that origin. We also configure the referrer field as the public homepage address. Private signup, welcome and chat pages do not load this tag, and GPC prevents it from loading. Native SMS links work when measurement is blocked or unavailable. No mobile number, SMS destination, draft body, conversation, form value or private signup URL is sent. Google may process data outside your country under its published terms. See Google’s advertising technologies and Google advertising controls.
Do Not Track. Some browsers send a "Do Not Track" signal. There is no industry agreement on what a site should do with it, so we don't respond to it specifically. Separately, Global Privacy Control prevents our Google Ads measurement tag from loading. Cookieless measurement still sends information to Google as described above; we do not enable personalized advertising or use household data for ad targeting.
10. Children
Nellie is not directed at children under 13, and we do not knowingly collect their information. If you believe a child has given us information, email us and we will delete it.
11. Changes
If we change this policy we'll update the date at the top. For changes that materially affect how we handle your information, we'll notify you by text or email before they take effect.
12. Contact
Erik Hope, d/b/a Mirabelle Studios
support@anello.co
For questions about the messaging specifically (opt-outs, frequency, or anything in §2), the same address reaches us, or text HELP to our number.