The short version
PayDwell runs almost entirely on your phone. Your facility data, broker information, dwell sessions, and evidence photos are stored locally on your device, not on our servers. We do not have a backend that holds your records.
When you email an invoice to a broker, your phone's own mail app sends it directly. We never see the contents.
We do not sell your data. We do not run ads. We do not track you across other apps or websites. The mobile app uses no analytics tools. The website uses Google Analytics only to understand traffic patterns. If any of this changes, we will update this policy and tell you in the app before the change takes effect.
1. Who we are
PayDwell is built and operated by Trevor Clendenin, an independent developer based in Savannah, Georgia. PayDwell is a mobile application that helps owner-operators and small-fleet truck drivers document detention time and generate broker-grade invoices.
This policy explains what data PayDwell handles, where it lives, and what control you have over it. It applies to the PayDwell mobile app and to the PayDwell website at paydwell.app.
2. What data PayDwell collects
This section is the most important part of the policy. We list every type of data the app or website handles, where it goes, and why.
From the app
| Data type | Why it exists and where it goes |
|---|---|
| Precise location | Your phone's GPS is used to detect when you arrive at and depart from a facility you have set up. The app polls your location while a session is active. Location data stays on your device. We do not transmit it to PayDwell servers. |
| Photos you capture | The Gate Arrival photo and Signed BOL photo are taken by you using the app's camera function. They are stored locally on your device and embedded into the invoice PDF you generate. We do not upload them anywhere. |
| Facility & broker info | Names, addresses, contract terms (rate, free time, grace period), broker email addresses, and similar details that you enter into PayDwell. Stored locally on your device. |
| Session records | Dwell sessions, timestamps, billable durations, calculated amounts, and references to your captured photos. Stored locally on your device. |
| Invoice content | The PDF the app generates contains the data above. When you send it, your phone's native mail composer attaches the PDF and sends it from your email account directly to the broker. We do not see, intercept, or store the email or its contents. |
From the website
| Data type | Why it exists and where it goes |
|---|---|
| Email address | If you sign up for the Android waitlist, we collect your email so we can notify you when the Android build ships. Your email is stored in Mailchimp, our email service provider. |
| Name & carrier (optional) | If you choose to provide them on the waitlist form, your first name, last name, and carrier or company are also stored in Mailchimp. None of these fields are required. |
| Standard server logs | Like most websites, our hosting provider keeps short-term access logs (IP address, request time, user agent). These are used only for debugging and security and are not used to profile you. |
| Google Analytics | The website uses Google Analytics 4 to understand traffic patterns: what pages drivers visit, where they come from, and which devices they use. Google Analytics sets cookies and processes IP address, page views, and session duration. We use this only to improve the website. The mobile app does not use Google Analytics or any analytics tool. |
3. What we do not collect
To be explicit about the things some apps collect and PayDwell does not:
- No analytics or behavior tracking in the app. The PayDwell mobile app does not use Mixpanel, Amplitude, Firebase Analytics, Sentry, Crashlytics, or any similar service. We do not record what screens you visit, what buttons you tap, or how long you spend in the app. The website uses Google Analytics for traffic analysis only, as described in Section 2 above.
- No advertising identifiers. We do not access your device's advertising ID. We do not run ads.
- No social-media tracking. We do not embed Facebook, TikTok, Twitter, or LinkedIn pixels. We do not share your data with social platforms.
- No cross-app tracking. We do not link your activity in PayDwell to your activity in any other app or website.
- No payment data. The Founding 10 beta is free. PayDwell does not currently process payments. If we add subscriptions in the future, payment data will be handled by Apple via in-app purchase or by a payment processor we will name in this policy at that time.
4. Permissions PayDwell asks for
iOS will prompt you to approve these the first time PayDwell needs them:
- Location (While Using the App). Required for the geo-fence trigger and dwell timer to work. PayDwell does not use background location.
- Camera. Required to capture the Gate Arrival and Signed BOL evidence photos.
- Photo Library (optional). Only if you choose to attach an existing photo instead of taking a new one.
- Mail (via system mail composer). Used when you tap the email button to send an invoice. The composer opens, you review the email, you tap send. PayDwell never sends email on your behalf.
You can revoke any of these in iOS Settings at any time. Revoking location will stop the dwell-timer feature from working.
5. Third-party services
PayDwell uses a small number of services to function. Each receives only the data necessary for its specific purpose.
- Apple TestFlight (during beta). The app is distributed through TestFlight while in beta. Apple collects standard TestFlight metrics including crash reports and tester information. See Apple's Privacy Policy.
- Google Maps Platform & Google Analytics. The Google Maps Places API powers facility search in the app — your search query is sent to Google so it can return matching addresses. Google Analytics powers traffic analysis on the website only (not the app). Both are governed by Google's Privacy Policy.
- Apple Maps. Used to display facility locations within the app. Apple's Privacy Policy applies.
- Mailchimp (website only). The Android waitlist form posts to Mailchimp, where your email and any optional details are stored. See Mailchimp's Privacy Policy.
6. How we use the data
The data PayDwell handles is used only for the purposes described above:
- To run the app's dwell-timing, evidence-capture, and invoice-generation features.
- To send you the Android launch announcement if you joined the waitlist.
- To respond to support emails you send us.
We do not use your data for marketing to other people, for selling to data brokers, or for any purpose unrelated to the service.
7. How long we keep it
- App data on your device. Sessions, photos, facilities, and broker records remain on your device until you delete them or uninstall the app. We have no ability to access or delete this data remotely.
- Mailchimp waitlist data. Kept until you unsubscribe or until we close the Android waitlist (at which point we will delete the list). You can unsubscribe at any time using the link at the bottom of any email we send you.
- Server logs. Standard short-term retention by our hosting provider; we do not retain access logs beyond what is needed for debugging and security.
8. Your rights
Because almost all of your PayDwell data lives on your own device, you control it directly:
- Access. Open the app to see all your sessions, facilities, brokers, and photos.
- Delete. Delete individual records inside the app, or uninstall PayDwell to remove all of it from your device at once.
- Revoke permissions. Use iOS Settings to revoke location, camera, or photo access at any time.
- Unsubscribe from the Android waitlist using the link in any email we send, or by emailing us directly.
Depending on where you live, you may have additional rights under laws such as the California Consumer Privacy Act (CCPA) or the EU General Data Protection Regulation (GDPR). To exercise any of those rights, email us at the address below and we will respond within 30 days.
9. Children
PayDwell is intended for licensed commercial drivers and is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has provided us with data, contact us and we will delete it.
10. Security
Because most data lives on your device, the device's own security model (passcode, Face ID, full-disk encryption) is the primary protection. We use HTTPS for all network communication. The Mailchimp account, Google Maps API key, and our hosting account are protected by strong passwords and two-factor authentication.
No system is perfectly secure. If we ever experience a data breach affecting waitlist subscribers, we will notify affected users by email within 72 hours of becoming aware of it.
11. Changes to this policy
If we add features that change how data is handled — for example, adding a backend, introducing analytics, or launching a paid subscription — we will update this policy and post the change date at the top. For material changes, we will display a notice in the app and email Android waitlist subscribers before the new terms take effect.