1. What data the App holds
Information you enter or generate while using the App:
- Pool profile — name (you choose), type, shape, dimensions, depth, surface material, location (only if you opt in), volume estimate, your name for the pool, any photos you attach
- Chemical readings — pH, free chlorine, total chlorine, alkalinity, calcium hardness, cyanuric acid (CYA), salt level, temperature, ORP, TDS, equipment PSI, and any other reading types we add
- Equipment inventory — type, brand, model, install date, last service date, current PSI, notes
- Chat messages — every message you send and every AI response, for as long as you keep the conversation
- Treatment events — chemicals added (what, how much, when), equipment serviced, bather events, observations
- Daily AI briefings — the 1-2 sentence AI summary shown on the Dashboard, cached per pool
- Pool event metadata — structured key-value pairs treatments and observations carry
Information we deliberately do NOT collect in the current version:
- We do not collect your name, email, phone number, mailing address, date of birth, or any other personal identifier.
- We do not collect your device location unless you specifically opt in for location-based features. When you do, the location stays on your device.
- We do not collect your device advertising identifier (IDFA on iOS, AAID on Android).
- We do not maintain user accounts. There is nothing to sign up for. Our server groups your anonymous chat logs by a random per-install UUID that has no link to any personal identifier.
- We do not collect payment information. There are no in-app purchases in the current version.
2. Where data lives
On your device. All pool data (pool profile, chemical readings, equipment inventory, chat message history, treatment events, briefings) is stored locally using Apple's SwiftData framework on iOS or Google's Room persistence library on Android. Both write to a local SQLite database in the App's sandbox.
On our server (Supabase, US region), anonymously. As of August 13, 2026, the App routes AI chat and image-description requests through our own backend (Supabase Edge Functions) instead of calling DeepSeek and OpenAI directly. Our backend forwards the request to the vendor and returns the response; along the way it logs the request and response to a Postgres table so we can improve the App over time. Each log row is tagged with an anonymous per-install identifier — a random UUID your device generates on first launch and keeps in its Keychain / EncryptedSharedPreferences. This UUID is not linked to your name, email, address, phone, Apple ID, or advertising identifier. It rotates automatically if you delete and reinstall the App.
The columns we log per row: the message text you sent, the AI's response text, the model that responded, latency, HTTP status, and a coarse app-version / platform tag. For image-description requests, we log the resulting description text but not the image itself. If you want the raw list of what we log, contact support@zer000.com.
We do not maintain a copy of your pool profile, readings, equipment inventory, or treatment history on our server. Those live on your device only. Deleting the App from your device removes all of that immediately. Anonymous chat / extraction logs on our server persist independently.
If a future version introduces optional cloud sync, accounts, or backup for on-device data, this Privacy Policy will be updated and the in-app acceptance gate will re-prompt before those features become active.
3. When data leaves your device
There are three situations in which data leaves your device:
3.1 AI chat (DeepSeek, via our Supabase proxy)
Each time you send a message in the AI chat, the App transmits to our Supabase backend: your anonymous device UUID; the text of your message; a "pool context" block describing your pool (volume, equipment, latest readings, location if you set it, season inferred from date+location, recent treatments); a summarized version of your recent chat history with this AI; and the app version + platform.
Our backend logs this request (anonymously, by device UUID) and forwards it to DeepSeek's API. DeepSeek processes the request and streams back a response. Our backend passes the response through to your device and also logs the response text alongside the request. DeepSeek's own data retention, training, and policy decisions are theirs, not ours. Review their current policy at deepseek.com before chatting about anything you would not want a third-party AI provider to receive.
3.2 Image description (OpenAI, via our Supabase proxy)
When you upload a photo for AI description, the image is transmitted to our Supabase backend which forwards it to OpenAI's vision API (currently the GPT-4o-mini model). OpenAI processes the image and returns a text description. Our backend logs the text description (not the image bytes) and passes the description through to your device. OpenAI's data retention, training, and policy decisions are theirs, not ours; review them at openai.com/policies before uploading.
3.3 Affiliate clicks
When you tap a product link in the Shop or in an AI chat response, the App opens that link in your device's browser or in the retailer's app. The retailer (Amazon, Impact.com network member, etc.) receives standard click attribution — a referral identifier and the click event. The retailer does not receive your pool profile, readings, equipment list, chat history, or any pool data.
4. What we do NOT do with your data
We do not:
- Sell, rent, lease, or trade your data to any third party
- Use third-party analytics SDKs in the current version
- Use crash reporting SDKs in the current version
- Run advertising in the App
- Track your activity across other apps or websites
- Use your data to train any AI model — ours or anyone else's
- Profile you based on your pool habits
- Share your data with affiliates beyond the standard click attribution described above
If any of this changes in a future version, this Privacy Policy will be updated and the in-app acceptance gate will re-prompt.
5. Children
AIPoolGuy is not intended for and is not directed to children under 13. We do not knowingly collect data from anyone under 13.
If you believe a child under 13 has used the App and you would like data associated with them removed from the device, you can do so by deleting the App or clearing its stored data via your device's Settings. We have no server-side copy to delete.
6. Your rights and choices
Because your data is local to your device, you control it directly:
- Delete a single pool — Edit Pool → Delete Pool. All readings, events, equipment, and chat history attached to that pool are cascade-deleted.
- Delete the entire App and its data — uninstall AIPoolGuy from your device.
- Clear all App data without uninstalling — iOS: Settings → General → iPhone Storage → AIPoolGuy → Offload/Delete App; Android: Settings → Apps → AIPoolGuy → Storage → Clear Data.
We have no copy on our side. There is nothing for us to delete on our end.
Data already transmitted to our backend, DeepSeek (chat), or OpenAI (vision) was sent at the moment you sent the message or upload. Anonymous logs on our backend can be deleted on request (see Section 7). For DeepSeek and OpenAI, refer to those providers' policies for their retention practices and data-subject request procedures.
7. GDPR, CCPA, COPPA, and similar laws
If you are in the European Economic Area, the United Kingdom, California, or another jurisdiction with data-protection laws, you have rights including access, rectification, erasure, data portability, and objection to processing.
Because your pool profile / readings / equipment / chat history live on your device (not on our server), the practical mechanism for most of these rights is direct on-device control. Anonymous chat and extraction logs on our server can be deleted on request — contact support@zer000.com with your device UUID (accessible in a future in-app Settings screen, or via a support request) and we will remove the associated rows.
For purposes of CCPA, we do not "sell" or "share" personal information as those terms are defined under California law.
For purposes of COPPA, the App is not directed to children under 13 and we do not knowingly collect from children under 13.
8. Data security
All transmissions to our Supabase backend and onward to DeepSeek / OpenAI are made over encrypted HTTPS connections. On-device data is protected by your device's built-in encryption, enforced by your device passcode or biometric lock. Our Supabase backend uses PostgreSQL with row-level security policies restricting access to authorized server processes only; the database has no publicly reachable read endpoint.
No method of storage or transmission is perfectly secure. We cannot guarantee absolute security and we are not liable for any security failure outside our reasonable control (Section 10 of the Terms of Service governs).
9. Affiliate disclosures
We participate (or will participate) in affiliate programs including:
- Amazon Associates Program — "As an Amazon Associate, AIPoolGuy earns from qualifying purchases."
- Impact.com (In The Swim, Wholesale Pool Supply, others)
- Leslie's Pool (via FlexOffers or direct)
- Doheny's (via Pepperjam)
- CircuPool and other smaller partners
Affiliate programs receive standard click and purchase attribution. They do not receive your pool data.
10. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. Updates take effect when posted at zer000.com/aipoolguy-privacy. Material changes will re-trigger the in-app acceptance gate; continued use after a material change constitutes your acceptance.
11. Compliance posture
This Privacy Policy is intended to comply with Apple App Store Review Guidelines, Apple's Privacy Manifest requirements (iOS 17+), Google Play developer policies and Data Safety disclosure requirements, GDPR where applicable, CCPA and CPRA where applicable, and COPPA where applicable.
12. Contact
0.0.0 LLC
1309 Coffeen Avenue STE 1200
Sheridan, WY 82801
United States
- support@zer000.com (general and privacy questions)
- legal@zer000.com (formal legal notice)
13. Consent
By using AIPoolGuy, you consent to the data practices described in this Privacy Policy.