The short version
- We collect what you give Fizzlayer: your account details, your sensor readings, and the alerts you set up.
- We use it only to run Fizzlayer. We do not sell your data or show you ads.
- A few trusted services help us run Fizzlayer. They are listed below.
- Email privacy@fizzlayer.com and we will delete your data.
01Who we are
Fizzlayer (fizzlayer.com) connects sensors and devices to AI agents. It is run by Nisarga P, an individual developer, referred to here as “we” or “us”. Fizz is the name of the AI agent and mascot inside Fizzlayer.
This policy covers the Fizzlayer website, app, API, MCP server, and the fizz command-line tool.
02What we collect
When you contact sales
- Your work email, your company name, and any note you write.
When you create an account
- With email: your email address and password. The password is stored only as a secure hash, never the password itself.
- With Google: your Google account ID, email address, name, and profile picture link. We use your email address to suggest your Fizzlayer username.
- With GitHub: your GitHub account ID, username, email address, name, and profile picture link. We use your email address to suggest your Fizzlayer username.
- Passkeys: if you add one, we store only its public key. Your fingerprint, face, or device PIN never leaves your device.
- If you signed up with an invite code before sign-up opened, the code you used.
When you subscribe to a paid plan
- Your plan, its status, and when it renews or ends, along with the Stripe customer and subscription IDs that link your account to Stripe.
- Stripe collects your payment details, such as your card and billing address. We never see or store your full card number.
When you use Fizzlayer
- Sensor data: sensor names and types, and the readings your sensors and devices send.
- Alerts: the rules you create and when they trigger. If you pair a number for calls, we store that US phone number on your workspace. The pairing code is stored only as a hash, expires in about 10 minutes, and works once.
- Connected agents: the name you give each agent and what it is allowed to do. Agent tokens and sensor keys are stored only as hashes.
- Paired devices: the device name and platform shown during pairing.
When you pair a phone as a sensor
A paired phone shares motion and orientation only while its Fizzlayer page is open. It can also share these, but only after you allow each one separately:
- Your location.
- Short audio clips, which we store so you can play them back.
- Voice transcripts.
When you talk to Fizzlayer
- Typed chat: your message and your recent readings go to an AI model so Fizzlayer can answer. We do not save chat history; it stays in your browser and is cleared when you sign out.
- Voice chat: your recording is sent for transcription and the reply from Fizz, our AI agent, is turned into speech. We do not save these recordings.
- Alert calls: the call speaks your alert. We turn off call recording.
Collected automatically
- IP address: used to stop abuse with rate limits. We store it only as a one-way hash, and delete it within about two days.
- Server logs: our hosting provider keeps standard request logs, such as IP address, browser type, and pages requested, for a short time.
- Page views: we count visits with Vercel Web Analytics, which records the page address (without anything after a
?or#), the referring site, your country and region, and your browser, operating system, and device type. It uses no cookies. Visitors are told apart by a hash of the request that is discarded after 24 hours.
We do not use advertising trackers.
03How we use it
- To run Fizzlayer: show your dashboard, check your alerts, place alert calls, and answer your questions.
- To keep Fizzlayer secure and stop abuse.
- To reply to your sales inquiry, and to email you about important changes to Fizzlayer.
- To fix problems and improve Fizzlayer.
We do not sell your personal information, share it for advertising, or use it to train AI models.
04Who helps us run Fizzlayer
These services process data for us, only to provide their part of Fizzlayer:
- Supabase: database and sign-in. Stores your account and sensor data.
- Vercel: hosts the website and API, counts page views with Vercel Web Analytics, and routes chat requests to AI model providers through Vercel AI Gateway.
- AI model providers (such as OpenAI), through Vercel AI Gateway: receive your chat messages and the readings needed to answer.
- ElevenLabs: turns voice recordings into text and Fizzlayer’s replies into speech.
- AgentPhone: places alert calls, and the pairing call that reads your code, to a number you asked us to call. Recording is off.
- Stripe: processes payments for paid plans and stores your payment details.
- Google: handles Google sign-in, and serves the pixel font used on our pages, which shares your IP address with Google.
- GitHub: handles GitHub sign-in, and hosts downloads of the
fizzcommand-line tool.
Each provider handles data under its own privacy policy. We may also share information if the law requires it, to protect people’s safety, or as part of a sale or transfer of Fizzlayer. If that happens, this policy will continue to apply to your data.
AI agents you connect can read your sensor data with the token you gave them. What they do with it is governed by whoever runs that agent. You can revoke a token at any time on the Agents page.
05Google and GitHub sign-in
If you sign in with Google, we receive only your basic profile: your Google account ID, email address, name, and profile picture link. We use it only to sign you in and to name your account. We do not access your Gmail, contacts, files, or any other Google data.
Fizzlayer’s use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
If you sign in with GitHub, we receive only your public profile and email address: your GitHub account ID, username, email address, name, and profile picture link. We use it only to sign you in and to name your account. We do not access your repositories, organizations, or any other GitHub data.
06Cookies
Fizzlayer uses only the cookies it needs to work, and none for analytics:
- fizz_session keeps you signed in for up to 12 hours.
- fizz_oauth protects Google and GitHub sign-in and lasts at most 10 minutes.
- fizz_supabase holds your sign-in for up to 1 hour after you sign in, so you can add a passkey.
A paired phone also saves its device key in the browser’s local storage so it stays connected.
07How long we keep it
- Account, sensors, readings, alerts, audio clips, and transcripts: until you delete them or ask us to delete your account. Removing a sensor deletes its readings, clips, and transcripts.
- Plan and billing status: with your account, until it is deleted. Stripe keeps its own payment records under its privacy policy.
- Sign-in sessions: 12 hours.
- Hashed IP addresses: about 2 days.
- Unused device pairing codes: 1 day.
- Sales inquiries, and emails from the former waitlist: until you ask us to remove them.
08Your choices and rights
- In the app: remove sensors, revoke paired phones and devices, delete alerts, and revoke agent tokens at any time.
- By email: ask for a copy of your data, a correction, or full deletion of your account at privacy@fizzlayer.com. We reply within 30 days.
- On your phone: turn off location, microphone, or motion access for Fizzlayer in your browser settings whenever you like.
Depending on where you live, including California and the European Economic Area, you may have legal rights to access, correct, delete, or move your data, and to object to how we use it. We honor these requests for everyone, wherever you live. We will not treat you differently for using them.
Fizzlayer is run from the United States, so your data is processed there.
09Security
We protect your data with encrypted connections. Passwords, session tokens, sensor keys, and agent tokens are stored only as hashes, and only our servers can reach the database. No system is perfectly secure, though. If a breach affects your data, we will tell you.
10Children
Fizzlayer is not for children under 13, and we do not knowingly collect their data. If you think a child has given us information, email us and we will delete it.
11Changes to this policy
We will update the date at the top when this policy changes. For important changes, we will also tell you by email or in the app before they take effect.
12Contact
Questions or requests: privacy@fizzlayer.com