Privacy policy

Effective October 29, 2026.

This policy covers Fennoc Phone, the Android app, and the Fennoc server that the app talks to. It says what Fennoc collects, why, who else receives it, and how you can delete it.

The short version

Your phone turns your speech into text. Your voice recordings never leave your phone.
Your contacts, your list of apps and your exact location stay on your phone.
When you are signed out, your reminders and lists stay on your phone. When you sign in, Fennoc's server keeps a copy of them for your account.
When the phone cannot handle a request by itself, it sends the text of your request to Fennoc's server. The server uses AI model providers to write the answer.
Fennoc has no ads. We do not sell your data. We do not let our AI providers train on it.
One person runs Fennoc. That person can see what is stored on the server. "Who can see your data" says when we look.

Who we are

Fennoc is made by Fennoc LLC, a Texas limited liability company ("Fennoc", "we", "us"). You can reach us at privacy@fennoc.com.

Fennoc is offered in the United States only, to people 18 and older.

What we collect

When you sign in

Your email address and your Google account ID, from Sign in with Google. We do not receive your name, photo or contacts from Google. Fennoc does not ask Google for access to your Gmail, Google Calendar or Google Tasks. Fennoc can read the calendar on your phone, if you allow it. See "What stays on your phone".
Your phone's time zone, once, at your first sign-in. Fennoc uses it to read times and dates on your clock, for example for reminders.
A waiting list entry, if we have not let you in yet: your email address, the time, and how many times you tried.

When you use Fennoc

What you say or type to Fennoc, when the phone sends it to the server, and Fennoc's replies. The server keeps your recent conversation so Fennoc can follow along.
Your city and the time, with each request that goes to the server. The city is a name such as "Austin, TX". It helps the fox answer questions about places near you, such as store hours. The phone works out the city from your location, or you type it in Settings. The phone never sends your coordinates. The server uses the city to answer that request and does not store it. The city goes to our AI providers as part of the request.
Your reminders and lists, when you are signed in. The phone copies each reminder to the server and keeps the two copies the same: its title, day, time, repeat, whether it is a must-do, whether it is done, and the name of its list. When you are signed out, your reminders and lists stay only on your phone.
Your routines, when you are signed in and you turn routines on. The phone copies your routines, their steps and what you log to the server.
Your tasks, plans and notes, and anything you ask Fennoc to remember.
Web pages you ask about. In Fennoc's browser, when you ask the fox about a page, the phone sends the page's address and title. It removes the part of the address after "?" first. When you ask Fennoc to guide you through a page, the phone also sends the page's headings, buttons, link text and form labels. It sends what you typed into plain text fields. It never sends what is in password, one-time code, card number or similar fields.
The results of actions. After a call, a text or another action, the phone tells the server whether it worked. This can include a contact's name, for example "The text to Sam did not go out." It never includes the phone number.
How many requests you make, so we can apply your plan's limit.

To keep Fennoc working

Turn reports. The time, whether the phone or the server answered, a result code such as "timeout", and how long it took. A turn report holds no words.
Crash reports. The app version, the Android version, your phone model, the type of error and where in Fennoc's code it happened. A crash report holds no message text, names or web addresses. The phone keeps an unsent report for up to 7 days.
Server logs. Your IP address and the time of each request. Some log lines also hold short pieces of text, for example the first 60 characters of a task title.
A sign-in token. The server keeps only a scrambled form of it (a hash). The phone keeps it encrypted.
Whether Fennoc is your home screen. Once a day, a signed-in phone tells the server whether Fennoc is your home screen and your assistant, with the date, the app version and the build. It holds no words and no app names. We use it to learn whether Fennoc is useful enough to keep.

What stays on your phone

These never go to Fennoc's server:

Voice audio. Fennoc uses only your phone's on-device speech recognizer, which Android provides. If your phone has no on-device recognizer, voice input does not start.
Your contacts. Fennoc reads names and numbers on your phone to find the person you mean. Your contact list and phone numbers are never sent. The name you say is part of your request, like the rest of your words.
Your apps. The list of apps on your phone, the apps you open, and the apps and sites you block or limit.
Your recent requests list.
Your calendar. If you allow calendar access, Fennoc reads today's events on your phone to show your next event on the home screen. The calendar on your phone can include events from your Google Calendar. Fennoc does not send your events to its server.
Your exact location. The phone uses your location only to work out the name of your city. Your coordinates never leave your phone. Only the city name is sent, as "Your city and the time" says.

Your reminders and lists stay only on your phone while you are signed out. When you sign in, the server keeps a copy, as "Your reminders and lists" says.

If Android backup is on, Android can copy some of Fennoc's data on your phone, such as your recent requests, to your Google account. Google runs that backup, not Fennoc.

Why Fennoc asks for each permission

Fennoc asks for a permission when you reach a step that needs it. You can say no and still use the rest of the app.

Permission	What Fennoc does with it
Microphone	Lets your phone turn your speech into text. Fennoc listens only when you tap the fox, when you hold the power button (if Fennoc is your phone's assistant), or right after the fox asks you a question. Also lets a website in Fennoc's browser use the microphone, if you allow that site.
Contacts	Finds the person you name, on your phone, for a call or a text.
Phone and SMS	Starts a call or sends a text when you ask. The words of a text come from your request, so they can reach the server and our AI providers.
See all apps	A home screen must show and open your apps. The list stays on your phone.
Location	Works out the name of your city, during setup or when you tap "Your city" in Settings. Only the city name is sent; your coordinates stay on your phone. Also lets a website in Fennoc's browser use your location, if you allow that site. That site receives your location. Fennoc does not.
Camera	Only for websites in Fennoc's browser, after you allow that site. The site receives the photo or video. Fennoc does not.
Calendar	Optional. Shows your next event on the home screen. Your events stay on your phone.
Notifications	Shows the reminders you set.
Alarms	Sets the alarms and timers you ask for.
Home, assistant and browser roles	Lets Fennoc be your home screen, your voice assistant and your web browser.

We do not use any of these to build an advertising profile. We do not sell or share the list of your apps.

Fennoc's browser

Pages load straight from the website to your phone. Websites can see your IP address and set cookies, under their own privacy policies. Fennoc keeps cookies on your phone so you stay signed in to sites. Files you download go to your phone's Downloads folder.

Fennoc sends a page to its server only when you ask about it, as described in "Web pages you ask about".

Who else receives your data

We use these service providers to run Fennoc. They process data for us. We do not sell data to them.

Provider	What it receives	Why
Fireworks AI	The text of your request, your recent conversation, the tasks, notes and memories that matter for that request, and any page you asked about	Writes Fennoc's answers
OpenRouter	The text of each request that reaches the server. When it writes an answer, it receives the same data as Fireworks.	Decides how to handle each request, and writes the answer when Fireworks cannot
Jina AI	Your search words, or the address of a page you asked Fennoc to read	Web search and page reading, only when a request needs it
Hostinger	Everything stored on Fennoc's server	Hosts the server, and keeps a weekly backup of it
Backblaze	An encrypted copy of Fennoc's databases. Only we hold the key, so Backblaze cannot read it.	Keeps a nightly backup away from the server
Google	Your sign-in	Sign in with Google

Neither AI provider keeps your text after it answers. Fireworks does not store prompts or answers for the open models Fennoc uses. It can hold part of a request in memory for a few minutes to answer faster. On OpenRouter, we turn on zero data retention, so it sends your text only to models that keep nothing. Because they keep nothing, they cannot train AI models on it.

We may also disclose data when the law requires it, or to protect a person's safety.

If Fennoc moves to a company that we own, or if Fennoc is sold, your data moves with it. This policy keeps applying to it, and we tell you before anything changes.

Who can see your data

Each person's data is kept in a separate database on the server. Other Fennoc users cannot reach it.

The person who runs Fennoc has full access to the server. That person can read your requests, replies and tasks. Your data is not encrypted in a way that stops this. We look at your content only:

to answer a support request that you send us;
to fix a problem that you report, with your permission;
to protect Fennoc and its users from abuse or a security attack; or
when the law requires it.

Day to day, we look at counts and times that hold no words, such as turn reports and crash reports. Fennoc has few users today, so these counts can still show what one person did.

How we protect your data

The app talks to the server over an encrypted connection (HTTPS). The server keeps sign-in tokens only as hashes. Only the person who runs Fennoc can sign in to the server.

No system is perfectly secure. If a breach exposes your data, we will tell you as the law requires.

How long we keep your data

Your account and your content: until you delete your account.
A waiting list entry: until we let you in, or until you ask us to delete it.
Server logs: up to 30 days.
Backups: we keep an encrypted nightly backup at Backblaze and a weekly backup of the whole server at Hostinger. A deleted item can stay in a backup for up to 15 days, until that backup is replaced. We use backups only to recover from a fault.

How to delete your account

Email privacy@fennoc.com from the address you signed in with, or follow the steps at fennoc.com/delete-account. We delete your account and its data within 30 days and tell you when it is done.

Signing out does not delete your data. Uninstalling the app removes Fennoc's data from your phone, but not from the server.

Your choices and rights

You can ask us to tell you what we hold about you, to give you a copy, to correct it, or to delete it. Email privacy@fennoc.com. We answer within 45 days. We do not treat you worse for asking.

If we say no to a request, you can appeal by replying to our answer. If you live in Texas and you disagree with the result of your appeal, you can contact the Texas Attorney General.

Children

Fennoc is not for anyone under 18. We do not knowingly collect data from children. If we learn that someone under 18 has an account, we delete it. If you think a child has given us data, email privacy@fennoc.com.

Changes to this policy

When this policy changes, we change the date at the top. Before an important change applies, we also tell you in the app or by email.

Contact

Fennoc LLC
5900 Balcones Dr STE 100, Austin, TX 78731
privacy@fennoc.com