Dayworth AI · Last updated 29 October 2026
Dayworth AI is a field-sales planning app. It holds the list of businesses you visit, what you did on each visit, where you drove, and, if you use the assistant, the questions you ask it. This page says what we collect, where it goes, and what we will and will not do with it.
Dayworth AI is operated by Dayworth LLC ("Dayworth AI", "we"), a Texas limited liability company. For privacy questions, contact privacy@dayworth.ai.
| What | Why |
|---|---|
| Email address and password | To create and secure your account. Passwords are hashed by our sign-in provider; we never see the plaintext. |
| Two-step sign-in (only if you turn it on) | To ask for a code from your authenticator app when you sign in with your password. The authenticator secret is created and stored by Google Identity Platform, our sign-in provider, which checks each code; it is not stored on Dayworth's servers. |
| Google or Apple account name and email (if you sign in with Google or Apple) | To identify your account. We do not receive your Google or Apple password. With Apple you can choose to share your email or a private relay address. |
| Your accounts and prospects: business names, addresses, phone numbers, websites, industry, tier, notes | This is the core of the product: the list of places you visit. |
| Contacts at those businesses: names, job roles, phone numbers, email addresses, notes | So the app can tell you who to ask for. See §4 on other people's data. |
| Visit records: dates, what you logged, next steps, quotes, photos you attach | Visit history and reporting. |
| Setup answers: what you sell, what you are optimising for | To tune which accounts the app ranks highest. |
| What | Why |
|---|---|
| Location: your device's coordinates, only while the app is open on screen, with the two exceptions in §3a | To sort accounts by distance, plan routes from where you are, and record mileage. Only with your permission, which your phone asks for and you can revoke at any time. |
| Trip and mileage records | Mileage logs and deduction reports. |
| Assistant usage: number of questions, tokens consumed, resulting cost | To enforce plan limits and bill correctly. We record the size of each request; the content is covered in §5. |
| A daily usage count: tallies of what was done in the app, the number of accounts and lists you hold, which optional features are on, and the app version and platform | To see how the app is used and whether a release broke something. Numbers only: never which accounts, never names, notes or locations. See §3. |
| Basic technical data: IP address, browser and device type, error logs | Security, abuse prevention, and fixing crashes. |
We do not use advertising trackers, third-party analytics, or cross-site cookies. We do not sell personal information, and we do not share it for cross-context behavioural advertising.
Used from a browser, Dayworth AI reads your location only while the app is open and on screen. Lock your phone or switch apps and the browser suspends the page; location reading stops. Distance sorting and route planning read your position when you ask for them. Arrival detection, if you switch it on, reads positions while the app is open to notice when you reach an account, and keeps the screen awake to do so. Nothing is read when the app is closed.
The installed app reads your location on the same terms as the browser, with two exceptions you choose: automatic mileage, if you turn it on, and turn-by-turn navigation while a route is running. Outside of those two it does not track you in the background. It asks for "Always" location only when you turn on one of them.
On the Mileage tab you can turn on automatic mileage. The iPhone then notices each drive by itself, including while the app is closed, so your mileage log fills itself in. This needs "Always" location, which iOS asks you for. While parked it uses only the phone's low-power location signals; during a drive it reads GPS until you have been stopped for a few minutes. For each drive it keeps when it started and ended, the distance, and the two end points, held on your phone only until the app next opens; the app then names the drive after the nearest of your own accounts at each end and discards the end points. The path you drove is never stored and never uploaded. The finished trip (date, times, distance, the account names at each end and the category you give it) goes into your encrypted backup like every other trip, if you sync. Turn it off on the Mileage tab, or set location to Never or While Using in Settings, and it stops at once.
The installed app can drive your route itself, with spoken directions. This is the only other feature that uses background location, and only while a route is actually running. It asks for "Always" only when you start a route, not at sign-up and not at first launch; decline it and navigation still works while the app is on screen. It stops the moment the last stop is reached or you tap End Route, and iOS shows its location indicator throughout. No trail is kept: positions are used to work out your next turn and then discarded. Apple receives the route you are driving: to calculate directions we send your current position and the stop you are driving to, and for an account whose pin is only approximate its street address, so Apple can place it. We do not send account names, notes, visit history or contacts. Apple handles what it receives under Apple's privacy policy.
Your position and trip history are stored on your device, and if you sync, inside the encrypted backup described in §3. Coordinates of route stops, not names and not notes, are sent to our routing provider to calculate driving times. When arrival detection sees you leave one stop on your planned route and arrive at the next, it keeps a small record of that drive (when you left, how long it took, how long the app expected, and the pins of the two stops; the latest 200 only) with your accounts and visits. Not the path you drove.
Revoke the location permission in your phone's settings and distance sorting, arrival detection and drive recording stop; nothing else does, and you can still log trips by hand. Trips already recorded stay yours. Export or delete them at any time (§8).
Your data is held in two forms.
The synced backup. Your device encrypts this copy with AES-256-GCM under a per-account data key before uploading it. What reaches our servers is ciphertext. The data key is also held by your account, so that signing in on a new device restores your territory, and so that a forgotten password does not cost you your data. A person with administrative access to our database could retrieve that key and decrypt that backup; we restrict such access to the personnel who operate the service and we do not use it to read customer data.
Account and visit records created through the app. These (business names, addresses, contacts, notes and visit outcomes) are stored in readable form on our servers, because the team dashboard, manager visibility, CRM synchronisation and the assistant operate on them. They are protected by transport encryption, encryption at rest, and per-account database rules that prevent any other customer from reading them.
The copy on your own device is not encrypted unless you turn on the Face ID lock (Account › Security), so keep a passcode on the phone. With the lock on, that copy is encrypted under a key your biometric check releases; signing in to your account can release it too, so a failed biometric never locks you out.
What this means in practice. Personnel with administrative access to our production systems are technically capable of reading your account names, addresses, contacts, notes and visit history. We commit that we do not do so, except where you ask us to in order to provide support, or where we are compelled by valid legal process, in which case we will give you notice unless the law prohibits it. If our systems were breached, an attacker with sufficient access could obtain readable customer data; access control and the breach-notification commitment in §9 are the operative protections.
If you turn on notifications, we store, readable on our servers, only what is needed to send them: your device's push subscription (an opaque delivery address, not your identity), your timezone, and which reminders you have switched on. Two reminders depend on what is in your book, so your device works them out and tells us only yes or no: "an account has gone cold" and "you have mileage that isn't logged" are each sent as a single on/off flag. The flag carries no account name, no note, and no count.
If you use the in-app feedback form, we receive what you type, your email address, and technical context about the moment you sent it: the app build, which screen you were on, how many stops were in your route (the count, not which ones), your browser and screen size, whether you were online, and the last few error messages the app recorded. We read these; that is their purpose. Treat the box like an email to us: describe the problem rather than pasting a customer's name, address or notes into it. To have one deleted, email privacy@dayworth.ai.
We access and process your data for three purposes:
Nothing else. We will not, and will not permit anyone else to: sell, rent, license, trade or transfer your data; include it in any dataset, index, benchmark or aggregate product, whether identified or anonymised; use it to train, fine-tune, evaluate or ground any AI model; mine it for market intelligence or lead lists; use it to build or improve a product that competes with you; or use it for advertising, profiling or scoring. That list is contractual: it is §4 of the Terms of Service, it does not depend on your plan, and it survives a change of ownership.
Your data is held on cloud infrastructure in the United States, encrypted in transit and at rest, and locked to your account by database security rules. A copy also lives on your own device so the app works with no signal.
What we can see: your email address, the name you choose to set, when you created your account and when you last signed in, how many accounts and visits you hold (the counts, not what is in them), how many of them still need an exact location, how many are pinned at the door, only roughly, or not at all (the counts, not where), and when you last logged one, when you last synced and from which device, how many assistant questions you asked and on which days, which features they came from and what they cost, how many times your routes were ordered and addresses looked up and what that cost (the counts, not the addresses), and which service answered each (our own servers or an outside provider), which optional features you use (CRM sync, push notifications, route planning), the timezone your device reports if you turn on notifications (so a morning reminder arrives in your morning and not ours), and errors the app recorded, including which account they came from, plus basic technical logs. We need these to run and bill the service. None of them reveal who your customers are.
A daily count of what was done. While you are signed in, each device you use sends us, at most once an hour, a count for the day of what was done in the app: how many visits were logged and how each one ended (as a count per outcome, such as meeting held or no answer), routes planned, minutes spent navigating in the app, imports finished and accounts they added, follow-ups marked done or snoozed, how many stops were planned for the day and how many of those were visited, the business miles recorded that day, and similar tallies. It also says how many accounts and lists your book holds and how many of those accounts are pinned at the door, only roughly, or not at all, which optional features are on (such as notifications, the Face ID lock, two-step sign-in, a coverage cadence, a connected Tesla and automatic mileage), and the app version and platform it came from. These are numbers and yes or no answers only. They never say which accounts, and never carry names, notes, addresses or locations. Signed out, nothing is sent.
Much of what you put into Dayworth AI is information about other people: the buyer at a distribution company, the manager at a plant. You decide what to collect about them and why; Dayworth AI processes it on your instructions. You are responsible for having a legitimate business reason to hold those details and for honouring requests from those individuals about their data. We will help you locate, export, correct or delete anything in your account so you can meet those obligations. If you are subject to GDPR or similar law, ask us for a data processing agreement.
Please do not store special categories of data in Dayworth AI, such as health information, government identifiers, payment card numbers, or anything about a person's race, religion, politics or sexuality.
The assistant sends only the part of your data needed to answer the question you asked, only when you ask it, and only for as long as the answer takes. Your question and the relevant slice of your accounts are decrypted on your device and sent to our AI provider, which operates the model that answers it. We pass it through; we do not store it. A single lookup carries at most 50 accounts, and a contact's phone number and email address are included only when the question is about one particular account. If your question requires research, the provider performs a web search; search queries may include terms drawn from your question, such as a company name or a town. We record how many questions you asked and what they cost, not the text of your conversations.
About our AI providers. We use two. Neither trains on what we send them, and neither may use it for their own purposes; they act on our instructions. Both keep a copy for up to 30 days for abuse monitoring, after which it is deleted. We pin a setting on every request (store: false) that stops the provider retaining the conversation for its own features; it does not switch off that 30-day abuse-monitoring copy.
Nothing else in your book is sent anywhere in readable form. The assistant can be wrong: verify an address, phone number or business detail before acting on it.
You can dictate instead of typing a visit note, a question to the assistant, or a voice note on the Apple Watch. Speech recognition is done by your phone's platform (Apple on iPhone and Safari, Google on Chrome and Android), which receives the audio under its own privacy policy; Dayworth AI never receives your audio, only the text handed back. Recording happens only while you hold the button, there is no wake word, and you see the text before anything is sent or saved. A dictated visit note goes to the AI only if you tap to ask for a better reading; a dictated question goes to the assistant, as a typed one would. On the Apple Watch the watch records and your iPhone transcribes; the phone deletes the clip once there is text, and the text is kept with the stop you were at, encrypted like everything else once a visit is logged. Your iPhone tells the watch the stop you are on (its name, address, the next stop's name, and the names and job titles of saved contacts) and nothing else; that passes between your own two devices only. If you would rather not, type instead, or revoke the microphone permission in Settings.
In the iPhone app, the card is read on your phone and the photograph does not leave it. The app uses Apple's document scanner and text recognition, which run on the phone, to find the card and read the printed words. Only those words, not the picture, are sent to our AI provider to be sorted into a name, a title, a phone number and so on. The picture is not saved and it is not uploaded. If the AI cannot be reached, the app sorts the words itself on the phone and nothing is sent. On the web, the photograph is sent to our AI provider to be read, with storage switched off, and we do not store the image. On either route, what the provider receives may be kept for up to 30 days for abuse monitoring and then deleted (§5). Only six things can be read off a card: a name, a job title, a company, a phone number, an email address and a website. The reading is shown to you as a proposed contact and becomes part of an account only when you tap to add it. The camera opens only when you tap Scan a card; there is no background scanning and no reading of your camera roll.
If you use the Request access form at dayworth.ai/beta, we receive your name, your email address, what you would use the app on, what you sell, and, if you fill them in, your company and who told you about us. We use them only to decide whether to invite you and to email you about the beta; a copy goes to our own team mailbox and nowhere else. Sending the form does not create an account. Each request is kept until the beta ends, or until you ask us to delete it. To stop the form being abused, we briefly count requests per network address as a one-way scrambled code, deleted within a day.
If you write to support@dayworth.ai or hello@dayworth.ai, a person reads your message and a person sends the reply. To prepare that reply faster, the text of your message is sent to our AI provider, which writes a draft for us to review. The draft is saved, not sent: nothing reaches you until a person has read it. The drafting tool sees only the email; it cannot open your account, your accounts list, your visits or your backup. The provider handles the text on the same terms as the assistant in §5. Mail to privacy@dayworth.ai and security@dayworth.ai is never processed this way.
We use a small number of sub-processors, each of which receives only what it needs and acts only on our instructions. A list of current providers by name is available on request from privacy@dayworth.ai.
| Service | What it receives |
|---|---|
| Hosting, sign-in and database (a major cloud provider in the United States) | Account details and app data, as described in §3. |
| AI providers: the assistant, AI features, and drafting replies to support email (§5b) | Your questions and the relevant account data, the words read off a business card, or the text of an email you send us. Neither trains on it; each keeps a copy for up to 30 days for abuse monitoring (§5). |
| Payments (Stripe) | Email and billing details. Card numbers go to Stripe directly and never reach our servers. |
| Address lookup (geocoding providers, reached only from our server) | The address text itself, a business name and street address, and a position you ask to turn into an address; never your notes, contacts or visit history. |
| Routing and driving times (our own routing server and an outside routing provider) | Coordinates of your stops, not names or notes. |
| Finding nearby businesses, checking an account's name against the map, and gas stations near a route (reached only from our server; map data from OpenStreetMap) | The area you are searching in, and account names with their map positions. |
| Map tiles (our own tile store and a fallback tile provider) | The map areas you view. |
| Salesforce, only if you connect it | Whatever you choose to sync. |
| Tesla, only if you connect a car | The name and location of the stop you send, and your car's location while connected. |
| Bot detection on the website and app attestation on iPhone (§9) | Signals from your browser and device and your IP address. Not your accounts, contacts, notes or visits. |
Depending on where you live, you may have rights to access, correct, delete or port your data, to object to processing, and not to be discriminated against for exercising them. Email privacy@dayworth.ai and we will respond within 30 days. We will not charge you or degrade your service for asking.
Encryption in transit and at rest; per-account isolation enforced in the database; secrets held in a dedicated key manager and never in our source code; a content security policy in the browser; and an optional Face ID lock that encrypts the copy on your own device (§3). To tell the real app from automated traffic, the website uses a bot-detection service that looks at signals from your browser and device, and the iPhone app uses Apple's App Attest. Neither receives your accounts, contacts, notes or visits.
No system is perfectly secure. If personal data is breached, we will notify affected users without undue delay and within 72 hours where the law requires it, telling you what happened, what was affected, and what to do.
Dayworth AI is a business tool and is not directed at anyone under 18. We do not knowingly collect data from children.
Data is processed in the United States. If you use Dayworth AI from outside the US, you are sending your data to the US, where privacy law differs from your own. For transfers of personal data out of the EEA or UK, we rely on Standard Contractual Clauses with our sub-processors.
Canada. We handle personal information in line with PIPEDA and, for Quebec residents, the Act respecting the protection of personal information in the private sector (Law 25). You may ask what we hold about you, have it corrected, or withdraw your consent, as described in §8. If you are not satisfied with our answer, you may complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.
Mexico. Dayworth LLC is the responsible party (responsable) for your personal data under the Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP). You have the rights of access, rectification, cancellation and opposition (ARCO) described in §8; write to privacy@dayworth.ai to exercise them. This policy is our privacy notice (aviso de privacidad) for that purpose.
We may update this policy. The date at the top always reflects the current version, and the previous version is available on request. Where a change materially affects how we handle your data, we will show a notice in the app. We do not undertake to email you, and we do not commit to any period of notice before a change applies. If a change is not acceptable to you, you can export everything and close your account at any time (§8).