Privacy Policy

Effective date: [Effective date]

Who we are

DeepEnd (“DeepEnd”, “we”, “us”) is run by [DeepEnd legal business name], [Mailing address]. This policy covers godeepend.com, app.godeepend.com, the DeepEnd phone app for iPhone and Android, and the DeepEnd business phone line and AI features. Questions: hello@godeepend.com.

Two kinds of people use DeepEnd. Pool service companies (our customers, and their owners, office staff and techs) sign up and use it. Their own customers (homeowners and businesses with pools) appear in it because the pool company keeps their records there. For that second group, the pool company decides what is collected and why, and DeepEnd handles it on the company’s behalf. If you are a pool company’s customer, please contact that company first; we’ll help them with your request.

What we collect

About pool companies and their staff

• Account details: name, email, phone number, role in the company, and sign-in records (when and from what kind of device).
• Company details: business name, address, time zone, settings, phone lines, price lists and tax rates.
• Subscription billing for DeepEnd: plan, trial dates and payment status. Stripe holds the card; we keep only Stripe’s reference numbers.
• Work done in DeepEnd: routes, stops, readings, notes, photos, to-dos, invoices, estimates, work orders, and who did what and when.

About the pool company’s customers (entered by the pool company)

• Names, service and billing addresses, phone numbers, emails, gate codes, access notes (for example a dog’s name), and tags.
• Pools and equipment, water test readings, chemicals added, photos, service reports and visit history.
• Rates, invoices, estimates, payments and balances. Card and bank details are entered on Stripe’s forms and stay with Stripe.
• Calls and texts with the pool company’s DeepEnd phone line: phone numbers, times, text messages, voicemails, call recordings, transcripts and AI-written call notes. Callers hear a recording notice before a recorded call.

Automatically

• Cookies that keep you signed in. DeepEnd uses only the cookies it needs to work; no advertising or tracking cookies, and no outside analytics.
• Basic server logs (time, page or address requested, errors), used to keep the service running and secure.
• For the phone app: a push notification token so we can send notifications and ring the app for incoming calls.
• For the phone app: the device’s location, only while the app is open and only if you allow it in the phone’s settings. It is used to get the weather where you are (when the company has no address to go by), for “Where I am now” as the start or finish of a route, and to note whether a tech was at the service address when a stop starts (the stop keeps only that yes or no, not the location). DeepEnd doesn’t track your location in the background.

The customer app (“My Pool – DeepEnd”)

If your pool company invites you to the customer app, DeepEnd collects only what the app needs:

• Your name and email address (the pool company already has them), used to send you a sign-in code and show your records.
• The messages you and the pool company send each other in the app.
• A push notification token for your phone and a random install ID, which we keep only as a scrambled (hashed) value, so we can send alerts such as “your technician is on the way” to the right phone. You can turn alerts off in the app or in your phone’s settings.
• Your choices in the app (how you get reports and invoices, which alerts you want) and sign-in records, including a scrambled form of your email used to slow down guessing of sign-in codes.
• Saved cards and bank accounts are held by Stripe, not by us; we keep only Stripe’s reference numbers and the card’s brand and last four digits.

The app shows your service reports, photos, readings, invoices and payments from your pool company’s records. It doesn’t use your location, contacts or photos, and has no advertising or outside analytics. To delete your login, open the app and choose Settings → Delete my login. That removes your phone’s notification token and your sign-in, unless the same login is also used for staff work at a pool company or for DeepEnd. Then the sign-in stays and is only unlinked from your customer records. Your pool company keeps its own records about you (your service history and invoices) as described above; ask the company, or write to us, to have those removed.

How we use it

• To run DeepEnd for the pool company: routes, service reports, invoicing, payments, the phone line, reminders and reports.
• To send the emails and texts the pool company asks DeepEnd to send, such as service reports, invoices and appointment texts.
• To provide DeepEnd’s AI features, described below.
• To bill the pool company for DeepEnd, give support, keep the service secure, and fix problems.
• To meet legal duties (for example tax records or answering a lawful request).

We don’t sell personal information, share it for advertising, or use it to build profiles of people. We don’t use one company’s information for another company.

AI features

DeepEnd uses Claude, an AI model from Anthropic, to write call notes, draft text replies, answer questions in Overseer (DeepEnd’s assistant), and, for companies that connect Google Ads, review ad results and suggest changes. Only the information needed for that task is sent, through Anthropic’s business API. Under Anthropic’s commercial terms, information sent this way isn’t used to train its models. AI never changes a company’s records or sends messages on its own: it proposes an action, and a person approves it unless the company has chosen to let that kind of action run automatically. Money-spending ad changes always need a person’s approval.

Google user data (Google Ads)

A pool company’s owner can choose to connect the company’s Google Ads account to DeepEnd. When they do, Google asks them to allow DeepEnd to “see, edit, create and delete your Google Ads accounts and data” (the Google Ads permission). Here is exactly what DeepEnd does with that access.

What we access

• The list of Google Ads accounts the person can reach, and account names, currency and time zone.
• Campaigns, budgets, bid settings, ad schedules, locations, keywords and ad text.
• Performance numbers: cost, impressions, clicks, conversions, calls from ads, and the search terms that showed the ads.

How we use it

• To show the company its ad results on DeepEnd’s Marketing page, next to the calls and customers each ad source brought in.
• To have DeepEnd’s ad manager (the AI feature above) review the results and suggest changes, with a plain reason for each.
• To make a change in the Google Ads account only after a person at the company approves it, and only within the daily and monthly spend limits the owner sets. The one exception is a safety pause: if a month is heading over the owner’s monthly limit, DeepEnd pauses the campaigns and tells the owner. Every change is recorded in a change log the company can see, with who approved it and why.

How we protect and share it

• Google’s access token is encrypted before it is stored, is only readable by DeepEnd’s servers, and is never shown in the app or written to logs.
• Google Ads data is visible only to the owner and office staff of the company that connected it. It is never shown to other companies.
• We share it only with the service providers needed to run these features (hosting and database below, and Anthropic for the ad manager’s review), and only for that purpose.
• We do not sell Google user data, use it for advertising, use it to determine credit-worthiness or for lending, or let people read it except as described here (the company’s own staff, our support staff when the company asks for help, security needs, or the law).
• We do not use Google user data to develop, improve or train generalized AI or machine-learning models.

DeepEnd’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting

The owner can disconnect at any time in DeepEnd under Settings → Ads → Disconnect. That cancels DeepEnd’s access at Google and deletes the stored token. Access can also be removed from your Google Account at myaccount.google.com/permissions. After disconnecting, stored ad results and the change log stay with the company’s records until the company deletes them or closes its DeepEnd account; ask us and we’ll delete them sooner.

Service providers we use

These companies process information for us, only to provide their part of DeepEnd:

• Google Cloud (web hosting, servers and scheduled jobs, in the United States).
• Supabase (database, sign-in and photo storage) and PowerSync (keeps the phone app’s offline copy in sync).
• Twilio (business phone numbers, calls, recordings, transcripts and texts).
• Anthropic (the Claude AI model).
• Stripe (DeepEnd subscription billing, and the pool company’s own card and bank payments from its customers).
• Resend (sending email).
• Apple and Google Firebase (phone app notifications and incoming-call alerts), and Expo (phone app updates, and delivering the customer app’s notifications).
• Address lookups: the U.S. Census Bureau geocoder and OpenStreetMap’s Nominatim (addresses only, to place stops on a map and get the weather); the National Weather Service and U.S. EPA (weather and UV forecasts, by location only).
• Mapbox (driving times between stops for “Optimize route”: the map points of the stops, the company address and, if chosen, “Where I am now”; no names).
• Google Ads, only for companies that connect it (above).

We may also share information if the law requires it, to protect people’s safety or DeepEnd’s rights, or as part of a sale or merger of DeepEnd (the buyer would be bound by this policy).

Keeping companies separate, and our own access

Every company’s records are kept apart by the database itself, so one company can’t see another’s. Inside a company, what each person sees depends on their role (for example, techs don’t see prices or pay). DeepEnd staff can’t browse a company’s customers, messages or recordings. If a company asks for help, a DeepEnd staff member can open a support session for a stated reason; every support session is recorded in a log.

Security

Information is sent over encrypted connections and stored with our providers’ encryption at rest. Sign-in tokens and connection keys are kept out of logs, and DeepEnd staff sign in with two-step verification. No system is perfectly secure; if a breach affects your information, we’ll tell the affected companies (and people, where the law requires) without unreasonable delay.

How long we keep information

• While a company uses DeepEnd, we keep its records so it can see its history.
• When a company closes its account, we delete its records within 90 days, except what we must keep for the law (such as billing records), and backups, which expire on their own schedule.
• A company can delete individual customers, photos and records itself at any time, and can ask us to export its data first.

Your choices and rights

You can ask to see, correct, export or delete your information by writing to hello@godeepend.com. If the information is a pool company’s record about you (you’re its customer), we’ll pass the request to that company and help it respond. California residents have rights under the California Consumer Privacy Act, including to know, delete and correct personal information and not to be discriminated against for using these rights; we don’t sell or share personal information as that law defines it. To stop texts from a pool company’s DeepEnd line, reply STOP.

Children

DeepEnd is a business tool and isn’t meant for children under 16. We don’t knowingly collect their information.

Changes to this policy

If we change this policy we’ll update the date at the top, and for important changes we’ll tell pool companies by email or in the app before they take effect.

Contact

[DeepEnd legal business name], [Mailing address]. Email hello@godeepend.com. See also our Terms of Service.