This document is in English; the English version governs. · Este documento está em inglês; a versão em inglês é a que vale. · Este documento está en inglés; la versión en inglés es la que rige. Questions? support@zaprouteapp.com

ZapRoute Privacy Policy

Effective date: October 21, 2026

ZapRoute ("the App") is operated by Emanuel Pools, Corp., 9956 Brickhill Dr, Boca Raton, FL 33428, United States ("we", "us"). This policy explains what information the App collects, why, and what we do with it.

What we collect

Account information. Your name, email address, preferred language, and role in your company (technician, field supervisor, estimator, office, owner). This is provided by your company when your account is created and is used to sign you in and show you the right screens.

WhatsApp number (optional). If you type it when you sign up, we use it only to help you during your free trial: Fabio, our founder, may write to you there himself — never automated or bulk messages. We never share it. We delete it 30 days after your trial ends, or sooner if you ask at support@zaprouteapp.com.

Service photos. The App requires a photo as proof of each pool service visit. Photos you take are uploaded to our servers and attached to the visit record. Photos are analyzed automatically (including by an AI service) to classify the type of service shown and to detect duplicated or altered images.

Location (optional). With your permission, the App uses your device's precise location to confirm presence at the serviced pool and to measure route mileage and fuel cost. Location is captured only while you use the App to register a visit or run a route. The App works without location permission; visits are then recorded without a presence stamp.

Operational data. Route, visit, and service records you create in the App (service types, times, notes, salt bags, filter cleanings, repair orders), which are the core function of the service.

Your company's customer data. Information your company enters about its own pool customers: their name, service address, e-mail address and phone number, their pools, the service photos taken at their pools, and, for customers who receive text messages, the consent status with its date and source. Your company decides what to enter and is responsible for having the right to do so; we process this information only to run the App for your company.

Customer lists you ask us to import. If you ask ZapRoute to import your customer list, only ZapRoute support opens the file, only to bring it into your account. We delete it 30 days after the import — or 30 days after you send it, if it is never imported, and right away if you cancel the request. We keep the record of your request and of your consent.

Client portal. Your company can create a private link for a customer that opens, without a password, a page with the photos and dates of that customer's recent service visits. Anyone who has the link can open the page until your company revokes it.

Visits to our website. zaprouteapp.com counts its own visits; this counter uses no cookies and no third-party analytics: each page opened adds one to a daily total, kept by page, language and the site that linked to it. To count each visitor only once a day, the IP address the visit comes from, the browser's identification and the date are turned on our server into a one-way code made with a secret key. The IP address is used for this only in memory and is never stored in our database; the codes are erased after two days, and only the daily numbers are kept. We also count, per day, how many visitors start filling in the sign-up form, how many send it, how many get an error and how many create an account. It is only a number: no field values, no name and no email. Like any website, our hosting providers (Google Cloud and Netlify) keep standard request logs, which include the IP address and browser of each request, for a limited time (up to 30 days at Google Cloud), for security and troubleshooting.

Where a sign-up came from. When you create an account from our website, the account keeps where your first visit came from and where your last visit before signing up came from (the last one that arrived through a link or from another site): the campaign tags in the link (utm_source, utm_medium, utm_campaign and utm_content), whether you arrived from a click on a Meta ad (yes or no — we never keep the click ID), the site that linked to us, the page you arrived on and the date. For both visits, we keep only the name of the site that linked to us (such as google.com), never the full address of the page. We use it only to know which channels bring new customers.

Measuring our ads (Meta pixel). The public pages of zaprouteapp.com load the Meta pixel, a small piece of code from Meta Platforms, Inc., so we can see whether our ads on Facebook and Instagram bring visits and sign-ups. When one of these pages opens, your browser sends Meta the address of the page, your IP address and details about your browser, and Meta stores its own cookies (_fbp, and _fbc when you arrive from a Meta ad), which last up to 90 days; Meta may connect this to a Facebook or Instagram account under Meta's own privacy policy. When you create an account on the website, or when your company subscribes, we tell Meta only that it happened — never your name, email, phone or company. The pixel is not used inside the App, in the customer portal or on the pages linked from a pool company's win-back offer, and it does not load when your browser sends the Global Privacy Control signal. To turn it off, turn on Global Privacy Control in your browser or use a tracker blocker; you can also manage the ads you see in your Facebook or Instagram settings. We do not sell your personal information.

Em português — o contador de visitas, anúncios (pixel da Meta) e a origem do cadastro. As páginas públicas do zaprouteapp.com carregam o pixel da Meta (Meta Platforms, Inc.) para sabermos se os nossos anúncios no Facebook e no Instagram trazem visitas e cadastros. Quando uma dessas páginas abre, o seu navegador manda à Meta o endereço da página, o seu IP e dados do navegador, e a Meta guarda cookies próprios (_fbp e, se você chegou por um anúncio da Meta, _fbc) por até 90 dias. Quando você cria uma conta pelo site, ou quando a sua empresa assina, contamos à Meta só que isso aconteceu — nunca o seu nome, e-mail, telefone ou empresa. O pixel não roda dentro do app, no portal do cliente nem nas páginas ligadas à oferta de retorno de uma empresa de piscina, e não carrega quando o navegador manda o sinal Global Privacy Control. Para desligar: ligue o Global Privacy Control no navegador ou use um bloqueador de rastreamento. Quando você cria uma conta pelo site, a conta guarda de onde vieram a sua primeira visita e a sua última visita antes do cadastro (as marcas de campanha do link: utm_source, utm_medium, utm_campaign e utm_content; se você chegou por um clique num anúncio da Meta, só sim ou não, sem nunca guardar o identificador do clique; o site que trouxe você — das duas, só o nome do site, como google.com —, a página por onde entrou e a data), só para sabermos quais canais trazem clientes. O site conta as próprias visitas com um contador que não usa cookies nem análise de terceiros: cada página aberta soma um num total do dia, por página, idioma e o site que trouxe você. Para contar cada visitante uma vez só por dia, o IP, a identificação do navegador e a data viram, no nosso servidor, um código de mão única feito com uma chave secreta; o IP não é gravado no nosso banco de dados e os códigos são apagados em dois dias. Como todo site, as nossas hospedagens (Google Cloud e Netlify) guardam por tempo limitado o registro padrão de cada pedido, com o IP e o navegador (até 30 dias no Google Cloud). Também contamos, por dia, quantos visitantes começam a preencher o formulário de cadastro, quantos o enviam, quantos recebem um erro e quantos criam uma conta. É só um número: nenhum valor dos campos, nenhum nome e nenhum e-mail. Não vendemos os seus dados pessoais. Vale a versão em inglês acima.

En español — el contador de visitas, anuncios (píxel de Meta) y el origen del registro. Las páginas públicas de zaprouteapp.com cargan el píxel de Meta (Meta Platforms, Inc.) para saber si nuestros anuncios en Facebook e Instagram traen visitas y registros. Cuando se abre una de estas páginas, tu navegador le envía a Meta la dirección de la página, tu IP y datos del navegador, y Meta guarda sus propias cookies (_fbp y, si llegaste por un anuncio de Meta, _fbc) hasta por 90 días. Cuando creas una cuenta en el sitio, o cuando tu empresa se suscribe, a Meta solo le decimos que ocurrió — nunca tu nombre, correo, teléfono ni empresa. El píxel no se usa dentro de la app, en el portal del cliente ni en las páginas enlazadas desde la oferta de regreso de una empresa de piscinas, y no se carga cuando tu navegador envía la señal Global Privacy Control. Para apagarlo: activa Global Privacy Control en tu navegador o usa un bloqueador de rastreo. Cuando creas una cuenta en el sitio, la cuenta guarda de dónde vinieron tu primera visita y tu última visita antes del registro (las marcas de campaña del enlace: utm_source, utm_medium, utm_campaign y utm_content; si llegaste por un clic en un anuncio de Meta, solo sí o no, sin guardar nunca el identificador del clic; el sitio que te trajo — de las dos, solo el nombre del sitio, como google.com —, la página por la que entraste y la fecha), solo para saber qué canales traen clientes. El sitio cuenta sus propias visitas con un contador que no usa cookies ni analítica de terceros: cada página abierta suma uno a un total del día, por página, idioma y el sitio que te trajo. Para contar a cada visitante una sola vez al día, la IP, la identificación del navegador y la fecha se convierten, en nuestro servidor, en un código de un solo sentido hecho con una clave secreta; la IP no se guarda en nuestra base de datos y los códigos se borran a los dos días. Como cualquier sitio, nuestros proveedores de hospedaje (Google Cloud y Netlify) guardan por un tiempo limitado el registro estándar de cada solicitud, con la IP y el navegador (hasta 30 días en Google Cloud). También contamos, por día, cuántos visitantes empiezan a llenar el formulario de registro, cuántos lo envían, cuántos reciben un error y cuántos crean una cuenta. Es solo un número: ningún valor de los campos, ningún nombre y ningún correo. No vendemos tus datos personales. Rige la versión en inglés de arriba.

Número de WhatsApp (opcional). Se você digitar no cadastro, usamos só para ajudar você durante o teste grátis: o Fabio, nosso fundador, pode escrever para você por lá, ele mesmo — nunca mensagem automática ou em massa. Nunca o passamos a ninguém. Apagamos 30 dias depois do fim do seu teste, ou antes, se você pedir em support@zaprouteapp.com.

Número de WhatsApp (opcional). Si lo escribes al registrarte, lo usamos solo para ayudarte durante tu prueba gratis: Fabio, nuestro fundador, puede escribirte por ahí, él mismo — nunca mensajes automáticos ni masivos. Nunca lo compartimos. Lo borramos 30 días después de que termine tu prueba, o antes si lo pides en support@zaprouteapp.com.

Listas de clientes que você pede para importarmos. Se você pedir ao ZapRoute para importar a sua lista de clientes, só o suporte do ZapRoute abre o arquivo, e só para trazê-lo para a sua conta. Apagamos o arquivo 30 dias depois da importação — ou 30 dias depois do envio, se ele nunca for importado, e na hora, se você cancelar o pedido. Guardamos o registro do pedido e da sua autorização.

Listas de clientes que nos pides importar. Si le pides a ZapRoute importar tu lista de clientes, solo el soporte de ZapRoute abre el archivo, y solo para traerlo a tu cuenta. Lo borramos 30 días después de la importación — o 30 días después de que lo envíes, si nunca se importa, y en el momento, si cancelas el pedido. Guardamos el registro de tu pedido y de tu autorización.

In the App, we do not collect advertising identifiers, we do not use advertising or third-party analytics SDKs, and we do not track you across other companies' apps or websites. The Meta pixel on the public pages of our website, described above, is the only advertising tool we use.

How we use it

We use the information above solely to operate the service: showing daily routes, storing proof of service, generating reports for your company, sending operational emails (for example, password reset or service notices), sending a pool company's win-back offers by email to its own former customers, only when that company's owner chooses to (see "Win-back offers from your pool company" below), sending company account owners occasional ZapRoute news (new features and changes in the App) and, during the free trial, a few short emails to help them get started (bringing in their customer list, adding a technician, when the trial ends), and keeping accounts secure. Every ZapRoute news email and every free-trial email has a link to stop getting them — one stop covers both — and stopping them never stops the emails about your account: sign-in, password, receipts, billing notices, and changes to prices or the Terms. We do not sell or rent personal information, and apart from measuring our own ads (with the Meta pixel on our website and with the sign-up forms on Facebook and Instagram, both described in this policy) and the win-back offers a pool company chooses to send to its own former customers, we do not use it for advertising. ZapRoute never sends its own marketing to a pool company's customers or former customers, and never sells their details. The emails and pages a pool company sends through ZapRoute carry a small "Sent with ZapRoute" line with a link to zaprouteapp.com.

Service providers

We rely on a small number of infrastructure providers to run the App, acting on our instructions: Supabase (database, authentication, and photo storage), Google Cloud (application hosting, maps and routing, and the nightly safety copies of photos and of the database), Anthropic (the AI features described in the next section), Resend (the App's e-mails, including ZapRoute news, the free-trial emails to account owners and the win-back offers a pool company sends to its former customers), Twilio (text messages to your pool customers, which means their phone number and the text of the message), Stripe (your company's subscription payment, including the billing details you enter on Stripe's own page — we never see or store your card), and Zapier (which passes to us the sign-up forms filled in on Facebook and Instagram — see "Sign-up forms on Facebook and Instagram" below). Each receives only the data needed to perform its function. If your company connects QuickBooks Online, Intuit is also a party to that data; the section below explains exactly what is exchanged.

What the AI does

Some features of the App send data to Anthropic, whose AI models (Claude) process it on our behalf. Each feature sends only what it needs:

Service photos. Each service photo is sent to the AI to classify what it shows (for example, a clean pool, a chemistry test or a filter) and to read the date and time printed on it. These results, together with automatic checks that do not use AI (such as spotting a photo identical to one already on file), are used to flag repeated or suspicious photos for review by a person in your company.

Chemistry test strips. When your company has turned this feature on, the photo of a test strip is sent to the AI, which reads the values from the strip. The readings are recorded on the visit and marked as read by the AI, and your office can review and correct them.

Equipment nameplates. When a user taps the button to read an equipment nameplate, that photo is sent to the AI to read the brand, model and serial number. The result is only a suggestion: nothing is saved until the user confirms it.

Draft messages to your pool customers. The AI writes drafts of past-due payment reminders, using your company's name, the customer's name, the amount past due, the number of days late and, if there is one, the payment link. It also drafts suggested replies to text messages from a customer, using your company's name and the recent text conversation with that customer. A person in your company reviews and can edit every draft, and nothing is sent until that person presses send.

Win-back offer translations. When a company owner writes a win-back offer in English, the offer text is sent to the AI to draft its Spanish and Portuguese versions. Only the text the owner wrote is sent, with placeholders where each customer's first name and city and the company's name and phone go — never a customer's name, email address or price. The owner checks each version before any offer is sent.

Ask ZapRoute. Questions you type into the in-app assistant, together with the earlier messages of the same conversation, are sent to the AI, which answers based on the App's user manual. The assistant has no access to your company's records. The conversation is kept in your account.

We do not use your photos or your company's data to train AI models.

QuickBooks Online (optional)

Your company can connect its QuickBooks Online account so that the App shows what each pool customer owes, using QuickBooks as the source of truth for money. Connecting is optional and the App works fully without it. Only the company owner can connect or disconnect, from Billing settings.

What we read. Invoices, payments, credit memos, your customer list, your company's name, your products and services (items), your sales settings (invoice numbering, default terms and whether sales tax is on) and your payment terms. For Revenue history, the App also reads sales receipts and refund receipts, only to add up each year's totals, and the Profit and Loss report of each closed year, only to check its totals. We do not read employees, payroll, bank accounts, card numbers, tax records, the chart of accounts, vendors, bills, journal entries or any other report. The App reads from QuickBooks. It creates invoices in your books only if the company owner turns on ZapRoute creates them in QuickBooks and confirms each send; it never changes, emails or deletes an invoice.

What we store. From invoices, payments and credit memos we keep the date, the amount, the document number, the due date, the balance, whether the transaction was voided, the private note, and the invoice lines (item, description, quantity, unit price, amount). From a payment we also keep the name of the payment method as it is written in QuickBooks — for example "Check", "Zelle" or "Cash". From your customer list we store the QuickBooks ID of each customer, so we can match it to the client record you already have in the App; the customer names, e-mail addresses and balances shown on the matching screen are held in the server's memory while that screen is in use and are not written to our database. Revenue history also stores the name of each customer that appears in it, and Former clients stores a few contact details of former customers — both explained below. When the owner turns on invoice creation, we also store the QuickBooks item chosen for each service (its ID, name and description) and, for each invoice the App creates, the lines it sent and the invoice number, total and tax that QuickBooks returned. We also keep the sales settings read when the owner turns this on (invoice numbering, the name of the default terms and whether sales tax is on). For the invoices the App creates, customer e-mail addresses and each customer’s payment terms are read at the moment of sending and are not stored.

Two of the fields we store — the private note and the invoice line description — are free text that you or your bookkeeper typed into QuickBooks. We copy them as they are, so whatever you put in them comes across.

How far back. The first sync reads thirteen months of transactions, plus every invoice that still has an open balance, whatever its date. After that we only ask QuickBooks what changed since the last sync, about once an hour. The matching screen reads your active customers so it can propose pairs; the pairing itself is proposed from the name and the e-mail address, and nothing is saved until the owner confirms it.

Revenue history (owner only). When the owner starts it (or reads it again), the App reads the invoices and credit memos of every earlier year. From each one it keeps the date, the amount, the document number, the customer's QuickBooks ID and how the amount splits by month of service and kind of charge, and, from your customer list, the name of each customer that appears in it (the QuickBooks display name) and whether that customer is active in QuickBooks. The text of the invoice lines is kept only while the owner or the office checks the import, and is deleted when the history is published.

Former clients (owner only). In Messages › Former clients the owner sees the customers the company used to bill and who stopped. When the owner taps Import from QuickBooks, we read those former customers' details from QuickBooks and store, for each one, only their email address, their first name, and the city, state and ZIP code of their service address (or, if it has none, of their billing address) — never the street address or the phone number. Only the company owner can see them, and they are used only in that list: to sort and filter it and to send the win-back offers the owner chooses. We delete these contact details when the owner disconnects QuickBooks or connects a different QuickBooks company, when the connection ends on QuickBooks' side (for example, when ZapRoute is removed on the "Apps" page inside QuickBooks) as soon as our next sync finds it, when Revenue history is read again and published, and when the company account is deleted. If the owner marks a former customer Exclude from offers…, we keep that mark — with a one-way hash of their email address and the reason, if the owner typed one — so that customer never gets an offer; the mark stays after QuickBooks is disconnected, and the office sees it on the record of a client who is also in ZapRoute.

How the connection is protected. The access and refresh tokens Intuit issues are encrypted before being stored, using AES-256-GCM, and the encryption key is kept outside the database. The tokens are never returned by the App's own interfaces, never sent to the mobile app, and never written to our logs.

Disconnecting. The owner can disconnect at any time. We ask Intuit to revoke our access and we delete the tokens on our side; if Intuit declines the revocation we still delete them, and you can also remove ZapRoute from the "Apps" page inside QuickBooks, which is the authoritative way to end the connection. Accounting data already synced, including Revenue history, stays in the App after you disconnect, so your screens do not suddenly lose their history; it is removed when the company account is deleted. The former customers' contact details are the exception: they are deleted when you disconnect, and also when the connection ends on QuickBooks' side.

Deleting your account. From the moment you ask us to delete your company we stop reading your QuickBooks: the hourly sync skips any company with a deletion pending, so nothing is read during the thirty days you have to change your mind. When the deletion runs, we ask Intuit to revoke our access and the synced QuickBooks data is deleted along with everything else. If Intuit declines that request we still delete our copy, and you can remove ZapRoute from the "Apps" page inside QuickBooks yourself.

One thing to know about payment reminders. If your company sets the App to follow QuickBooks balances, a payment reminder e-mail sent to one of your pool customers includes the QuickBooks invoice number and the description of its first line. That e-mail is delivered through our e-mail provider.

Win-back offers from your pool company

A pool service company that uses ZapRoute can email its own former customers an offer to come back. This section is for the people who get one.

Who sends it. The offer comes from your former pool company: its owner chose to send it to you and set your price, and ZapRoute delivers it. You get it because you were that company's customer. Offers go by email only.

What is used. Your email address, your first name, your city, the price the company chose for you, the price after the offer and the language of the email. Replies go straight to the company's own email address; ZapRoute does not read them.

What we record. For the company, we keep a record of each offer it sent: the email address it went to and a masked form of it (like j•••@example.com), your name as the company has it, your first name and city, the prices, the dates, whether the email bounced, and — approximately — whether it was opened (our email provider reports this with a tiny image in the email; some email apps load it by themselves, others block it). The company can also mark that you replied or came back. When the company disconnects QuickBooks from ZapRoute, the email address and its masked form, the name, the first name and the city of someone who is only in its QuickBooks are removed from this record; a one-way hash of the address, the prices and the dates stay. The whole record is deleted with the company's account.

Stopping offers. Every offer has a link to stop getting offers from that company. One tap on Stop offers stops them right away and for good, with no sign-in, and only offers stop: if you are still a customer, the emails about your pool service do not change. You can also ask the company by replying; the company then records your request in ZapRoute, with the same effect. An address whose offer bounced or was reported as spam joins the same list. So that company never sends you an offer again, we keep a fingerprint of your email address — a one-way hash, not the address itself — for as long as that company's account exists. We never share or sell it, not even with other companies that use ZapRoute.

The pages linked from the offer. The example pool page (zaprouteapp.com/pool-page) and the stop-offers page do not load the Meta pixel. The example page counts its visits like the rest of our website (see "Visits to our website" above).

Em português — ex-clientes e ofertas de retorno. Quando o dono inicia (ou relê) o Histórico de receita (só o dono), o ZapRoute lê as faturas e notas de crédito de todos os anos anteriores e guarda de cada uma a data, o valor, o número, o ID do cliente no QuickBooks e como o valor se divide por mês de serviço e tipo de cobrança, mais o nome de cada cliente que aparece nele (o nome de exibição do QuickBooks) e se ele está ativo lá; o texto das linhas das faturas só fica enquanto a importação é conferida. Em Mensagens › Ex-clientes, quando o dono toca em Trazer do QuickBooks, guardamos de cada ex-cliente só o e-mail, o primeiro nome e a cidade, o estado e o ZIP do endereço de serviço (ou, se não houver, do de cobrança) — nunca a rua nem o telefone. Só o dono vê, e só para ordenar e filtrar essa lista e mandar as ofertas que ele escolher. Apagamos esses contatos quando o dono desconecta o QuickBooks ou conecta outra empresa do QuickBooks, quando a conexão acaba pelo lado do QuickBooks (por exemplo, quando o ZapRoute é tirado na página "Apps" do QuickBooks) assim que a nossa próxima sincronização percebe, quando o Histórico de receita é lido de novo e publicado, e quando a conta da empresa é apagada. Se o dono marca um ex-cliente como Não quero de volta, guardamos a marca — com um código de mão única do e-mail e o motivo, se ele escreveu um — para ele nunca receber oferta, mesmo depois de desconectar o QuickBooks; o escritório vê a marca na ficha de quem também é cliente no ZapRoute. A oferta de retorno é da empresa de piscina: o dono escolhe quem recebe e o preço de cada um, e o ZapRoute entrega, só por e-mail. Usamos o e-mail, o primeiro nome, a cidade, o preço escolhido, o preço depois da oferta e o idioma; as respostas vão direto para o e-mail da empresa. Guardamos para a empresa o registro de cada oferta (o e-mail usado e uma forma mascarada dele, como j•••@example.com, o nome como a empresa tem, o primeiro nome e a cidade, os preços, as datas, se o e-mail voltou e, de forma aproximada, se foi aberto, por uma imagem minúscula no e-mail); ao desconectar o QuickBooks do ZapRoute, saem dele o e-mail (e a forma mascarada), o nome, o primeiro nome e a cidade de quem só está no QuickBooks da empresa (ficam um código de mão única do e-mail, os preços e as datas), e ele todo é apagado com a conta da empresa. Toda oferta tem um link para parar de receber ofertas daquela empresa: um toque em Parar de receber ofertas, na hora e para sempre, sem entrar em conta nenhuma; se você ainda é cliente, os e-mails do serviço da sua piscina continuam. Você também pode pedir respondendo o e-mail, e a empresa registra o pedido no ZapRoute, com o mesmo efeito. O e-mail que voltou ou foi marcado como spam entra na mesma lista. Para aquela empresa nunca mais mandar oferta, guardamos uma impressão digital do e-mail — um código de mão única, não o endereço — enquanto a conta dela existir; nunca a passamos nem vendemos a ninguém. O ZapRoute nunca manda o próprio marketing aos clientes ou ex-clientes de uma empresa de piscina e nunca vende os dados deles. Os e-mails e as páginas que a empresa manda pelo ZapRoute levam uma linha pequena "Enviado com o ZapRoute", com um link para o zaprouteapp.com. O pixel da Meta não roda na página de exemplo (zaprouteapp.com/pool-page) nem na página de parar de receber ofertas. Quando o dono escreve a oferta em inglês, só o texto que ele escreveu vai à IA para rascunhar o espanhol e o português — com marcas no lugar do primeiro nome e da cidade do cliente e do nome e do telefone da empresa, nunca o nome, o e-mail ou o preço de um cliente — e o dono confere cada versão antes do envio. Vale a versão em inglês acima.

En español — exclientes y ofertas de regreso. Cuando el dueño inicia (o vuelve a leer) el Historial de ingresos (solo el dueño), ZapRoute lee las facturas y notas de crédito de todos los años anteriores y guarda de cada una la fecha, el monto, el número, el ID del cliente en QuickBooks y cómo se divide el monto por mes de servicio y tipo de cargo, además del nombre de cada cliente que aparece en él (el nombre para mostrar de QuickBooks) y si está activo allí; el texto de las líneas de las facturas solo queda mientras se revisa la importación. En Mensajes › Exclientes, cuando el dueño toca Traer de QuickBooks, guardamos de cada excliente solo el correo, el nombre y la ciudad, el estado y el ZIP de la dirección de servicio (o, si no la hay, de la de facturación) — nunca la calle ni el teléfono. Solo el dueño lo ve, y solo para ordenar y filtrar esa lista y enviar las ofertas que elija. Borramos esos contactos cuando el dueño desconecta QuickBooks o conecta otra empresa de QuickBooks, cuando la conexión termina del lado de QuickBooks (por ejemplo, cuando se quita ZapRoute en la página "Apps" de QuickBooks) en cuanto nuestra próxima sincronización lo detecta, cuando el Historial de ingresos se vuelve a leer y se publica, y cuando se borra la cuenta de la empresa. Si el dueño marca a un excliente con Excluir de las ofertas, guardamos la marca — con un código de un solo sentido del correo y el motivo, si escribió uno — para que nunca reciba una oferta, incluso después de desconectar QuickBooks; la oficina ve la marca en la ficha de quien también es cliente en ZapRoute. La oferta de regreso es de la empresa de piscinas: el dueño elige quién la recibe y el precio de cada uno, y ZapRoute la entrega, solo por correo. Usamos el correo, el nombre, la ciudad, el precio elegido, el precio después de la oferta y el idioma; las respuestas van directo al correo de la empresa. Guardamos para la empresa el registro de cada oferta (el correo usado y una forma enmascarada de él, como j•••@example.com, el nombre como lo tiene la empresa, el nombre de pila y la ciudad, los precios, las fechas, si el correo rebotó y, de forma aproximada, si se abrió, por una imagen diminuta en el correo); al desconectar QuickBooks de ZapRoute, salen de él el correo (y la forma enmascarada), el nombre, el nombre de pila y la ciudad de quien solo está en el QuickBooks de la empresa (quedan un código de un solo sentido del correo, los precios y las fechas), y todo se borra con la cuenta de la empresa. Cada oferta tiene un enlace para dejar de recibir ofertas de esa empresa: un toque en Dejar de recibir ofertas, al momento y para siempre, sin entrar a ninguna cuenta; si todavía eres cliente, los correos del servicio de tu piscina siguen. También puedes pedirlo respondiendo el correo, y la empresa registra el pedido en ZapRoute, con el mismo efecto. El correo que rebotó o se marcó como spam entra en la misma lista. Para que esa empresa nunca más te envíe una oferta, guardamos una huella del correo — un código de un solo sentido, no la dirección — mientras exista su cuenta; nunca la compartimos ni la vendemos. ZapRoute nunca envía su propio marketing a los clientes o exclientes de una empresa de piscinas y nunca vende sus datos. Los correos y las páginas que la empresa envía con ZapRoute llevan una línea pequeña "Enviado con ZapRoute", con un enlace a zaprouteapp.com. El píxel de Meta no se carga en la página de ejemplo (zaprouteapp.com/pool-page) ni en la página para dejar de recibir ofertas. Cuando el dueño escribe la oferta en inglés, solo el texto que escribió va a la IA para preparar el español y el portugués — con marcas en lugar del nombre y la ciudad del cliente y del nombre y el teléfono de la empresa, nunca el nombre, el correo o el precio de un cliente — y el dueño revisa cada versión antes del envío. Rige la versión en inglés de arriba.

Sign-up forms on Facebook and Instagram

Some of our ads on Facebook and Instagram carry a sign-up form (a Meta "instant form") where you can ask for a ZapRoute free trial without leaving Facebook or Instagram.

What we receive. What you send in the form: your name, email address and company name, your answers (such as how many pools you service), and which ad, ad set, campaign and form you used (on Facebook or Instagram), with the date and Meta's reference number for your filled-in form.

Why. You asked in the form for a trial account. We use this to create it, to send you the sign-in link and the free-trial emails, and to learn which of our ads bring customers. We do not use a phone number for marketing text messages (SMS), and we never send this data back to Meta.

Who handles it. Meta Platforms, Inc., where you filled in the form (Meta's own privacy policy applies there), and Zapier, Inc., which passes the form from Meta to us.

How long we keep it. If you never open the account, we delete the account and the form data after 90 days. If no account was created (for example, because you told us you own a pool and are not a pool service business), we delete the form data after 90 days. To have it deleted sooner, write to support@zaprouteapp.com.

Em português — formulários de cadastro no Facebook e no Instagram. Se você pedir um teste grátis do ZapRoute num formulário nosso no Facebook ou no Instagram, recebemos o que você preencheu: nome, e-mail, nome da empresa, as suas respostas (como quantas piscinas você atende) e qual anúncio, conjunto de anúncios, campanha e formulário você usou (no Facebook ou no Instagram), com a data e o número de referência da Meta para o formulário que você preencheu. Usamos isso para criar a conta que você pediu, mandar o link de entrada e os e-mails do teste e saber quais dos nossos anúncios trazem clientes. Não usamos telefone para SMS de marketing e nunca mandamos esses dados de volta para a Meta. Quem lida com eles: a Meta (onde você preencheu o formulário) e o Zapier, que passa o formulário da Meta para nós. Se você nunca abrir a conta, apagamos a conta e os dados do formulário depois de 90 dias (se nenhuma conta foi criada, só os dados do formulário). Para apagar antes, escreva para support@zaprouteapp.com. Vale a versão em inglês acima.

En español — formularios de registro en Facebook e Instagram. Si pides una prueba gratis de ZapRoute en uno de nuestros formularios en Facebook o Instagram, recibimos lo que llenaste: nombre, correo, nombre de la empresa, tus respuestas (como cuántas piscinas atiendes) y qué anuncio, conjunto de anuncios, campaña y formulario usaste (en Facebook o Instagram), con la fecha y el número de referencia de Meta para el formulario que llenaste. Lo usamos para crear la cuenta que pediste, enviarte el enlace para entrar y los correos de la prueba, y saber cuáles de nuestros anuncios traen clientes. No usamos un teléfono para SMS de marketing y nunca le devolvemos estos datos a Meta. Quién los maneja: Meta (donde llenaste el formulario) y Zapier, que nos pasa el formulario desde Meta. Si nunca abres la cuenta, borramos la cuenta y los datos del formulario a los 90 días (si no se creó ninguna cuenta, solo los datos del formulario). Para borrarlos antes, escribe a support@zaprouteapp.com. Rige la versión en inglés de arriba.

Sharing within your company

The App is a business tool. Your visits, photos, and route data are visible to authorized members of your company (such as office staff and the owner) according to their role. Revenue and billing values are never shown to technician or field-supervisor roles.

Data retention and deletion

Service records and photos are retained while your company's account is active, as they form your company's service history. Ending a subscription does not delete anything.

An account created on our website or in the app whose email is never confirmed, and that has no pools, visits or customers, is deleted after 7 days. We send two reminders before that.

Uma conta criada pelo site ou pelo app cujo e-mail nunca é confirmado, e que não tem piscinas, visitas nem clientes, é apagada depois de 7 dias. Antes disso mandamos dois lembretes.

Una cuenta creada en el sitio o en la app cuyo correo nunca se confirma, y que no tiene piscinas, visitas ni clientes, se borra a los 7 días. Antes de eso enviamos dos recordatorios.

Notes between the office and technicians, with the photo attached to a reply, are deleted 7 days after they're closed. Like anything we erase, a deleted note can stay in the nightly safety copies of the database until those copies expire (we keep 7) and, at our providers, for up to 7 more days.

Deleting is done inside the app. An owner can delete the whole company account (Company › Delete account); any other team member can delete their own access. The account switches off right away and the data is permanently erased 30 days later — until that date you can cancel and get everything back. Photos are erased from both places they live: our main storage and the safety copy at Google Cloud. The nightly safety copy of the database holds all accounts together, so your records leave it as the daily copies expire: we keep 7 of them. Our providers keep what we erase recoverable for up to 7 more days as protection against an error on our side. After up to 14 further days, it is all gone.

After deletion we keep only what United States tax law requires: subscription and payment records (amount, date, tax, and which version of the Terms was accepted) for 7 years. No photos, no addresses, no client names, no pool data. Nobody can sign in to it.

The one exception: if you asked to stop getting ZapRoute news or the free-trial emails, we also keep a fingerprint of that email address — a one-way hash, not the address itself — so we never write to it again.

Security

Data is encrypted in transit (HTTPS/TLS). Access to production data is restricted by role-based rules at the database level (row-level security), and passwords are handled by our authentication provider — we never see or store them in plain text.

Children

The App is a professional tool for pool service businesses and is not directed at children under 13. We do not knowingly collect information from children.

Changes

If we make material changes to this policy, we will update this page and the effective date above.

Contact

Questions or requests: support@zaprouteapp.com
Emanuel Pools, Corp. (doing business as ZapRoute) — 9956 Brickhill Dr, Boca Raton, FL 33428, USA