Smithworks
Privacy policy
This policy explains how Ecommerce Maven LLC handles information when businesses and their customers use Smithworks.
Scope and responsibilities
This policy applies to the Smithworks Android app, smithworks.app, and related support services. A business that uses Smithworks decides what customer and job information to enter and is responsible for using it lawfully. Ecommerce Maven LLC operates Smithworks and processes that information to provide the service. Smithworks is a Maven Productivity app; Maven Productivity is a trade name of Ecommerce Maven LLC, and it is the name shown on Smithworks checkout pages and billing receipts.
Information we process
| Category | Examples and source |
|---|---|
| Account and business | Email address, business name, phone, service area, address, hours, services, prices, and document settings supplied by the account user. |
| Customers and jobs | Names, phone numbers, email addresses, service addresses, vehicle details and VINs, notes, quotes, appointments, invoices, and payment records entered by a business or customer. |
| Optional device data | Foreground location when a user requests nearby addresses or a current driving-time check. Smithworks does not request background location. The camera reads a VIN barcode on the device; that image is not uploaded or stored. Job photos a user takes or chooses are uploaded and stored with the job. When a user adds a customer from the phone’s contacts, Android shares only the one name and number the user picks; Smithworks does not request contacts permission or read the contact list. Notification tokens let Smithworks alert the account user about new booking requests. |
| Sign in with Google | The Google account’s name, email address, and account identifier when a user chooses to sign in with Google. |
| Connected services | Google Calendar free/busy intervals, dedicated Smithworks calendar events, and encrypted connection credentials when a user chooses to connect Calendar. |
| Card payments (optional) | When a business connects a Square account: the Square merchant and location identifiers and encrypted connection credentials, and for each card payment the amount, tip, card brand, last four digits, and Square’s payment reference, kept with the invoice. Card details entered on a Square Reader, through Tap to Pay on Android, or on Square’s payment page go directly to Square; Smithworks never receives or stores full card numbers. During an in-person card payment, Square’s software on the phone uses precise location, Bluetooth (to reach a card reader), and device information for payment security. |
| Accounting sync (optional) | When a business connects QuickBooks Online: the QuickBooks company identifier and name, encrypted connection credentials, and the QuickBooks identifiers of the customers, products, invoices, and payments Smithworks sent, with their sync status. If the business imports customers, the names, phone numbers, email addresses, addresses, and notes of their QuickBooks customers are copied into Smithworks. |
| Zapier automation (optional) | When a business creates a Zapier key in Settings: a one-way hash of the key (the key itself is shown once and never stored), the Zaps connected with it and the events each one asked for, and a short-lived queue of the event records waiting to be delivered. Customers, booking requests, and job notes that a Zap adds are stored like any other record. |
| Plan and billing | The business’s trial and plan status, price, number of people (seats), billing dates, and Stripe’s customer and subscription identifiers. To set up billing, Smithworks gives Stripe the owner’s email address and business name. Card details and the billing address are entered on Stripe’s checkout page and go directly to Stripe; Smithworks never receives or stores full card numbers. |
| Operations and security | Authentication events, network requests, synchronization and delivery state, error details, IP address, timestamps, and provider quota usage generated while operating the service. |
| Waitlist signups | Name, business name, email address, an optional mobile number, how the business invoices today, phone type, and an optional note about what you want next, entered on the smithworks.app waitlist form. Cloudflare Turnstile checks the form for bots using browser and connection signals. |
| Website visits | On the smithworks.app marketing, help, and policy pages: the pages you view, the site that sent you, clicks, scrolling and mouse movement, browser and device type, and approximate location from your IP address, collected with cookies and similar technology by Google Analytics and Microsoft Clarity. Clarity masks what you type into forms. These tools do not run in the Smithworks app, on online booking pages, or on request links. |
How we use information
- Authenticate users and administer accounts.
- Save, synchronize, and recover authorized business records.
- Schedule jobs and provide address, route, and Calendar features.
- Create and deliver requested invoices, receipts, and reminders.
- Run free trials and Smithworks plans: take payment, keep the seat count in step with the people on the account, and decide which features are available.
- Prevent abuse, enforce quotas, troubleshoot, and secure the service.
- Respond to support, privacy, and account-deletion requests.
- Email waitlist signups about their spot and Smithworks news. A waitlist mobile number is used only to reach you about your spot, never for marketing texts.
- Understand how visitors find and use smithworks.app, and improve the website.
Card payments are processed by Square under the business’s own Square account and Square’s terms and privacy policy. Smithworks records cash, checks, and other payments the business enters, and the result of card payments taken through Square. We do not use a business's customer records to market unrelated services to those customers.
When a business connects QuickBooks Online, Smithworks sends that business’s issued invoices and recorded payments, with the customer and line-item details on them, to the business’s own QuickBooks company so they don’t enter them twice. It reads only what it needs to match existing customers and products, and the customer list when the business chooses to import it.
When a business connects Zapier, Smithworks sends only the events that business’s own Zaps subscribe to (new customers, booking requests, quotes, scheduled, completed, or cancelled jobs, issued invoices, and payments, with the customer and line-item details on them) to Zapier, which passes them to the apps the business chose. Zaps can also look up or add customers, add booking requests, and add notes to jobs. Events go only to Zapier’s own servers, and Zapier handles them under its own terms and privacy policy.
Service providers and integrations
We disclose only the information needed for providers to perform these functions. They may process operational metadata under their own terms and privacy commitments.
| Provider | Purpose |
|---|---|
| Supabase | Authentication, database hosting, synchronization, and server functions. |
| Google Maps Platform | Address search, geocoding, and requested route estimates. |
| Google Calendar | Optional free/busy checks and Smithworks appointment publishing. |
| Resend | Account, invoice, receipt, confirmation, reminder, and review request email, and the waitlist email list. |
| Cloudflare | Hosting smithworks.app and the waitlist form, and Turnstile bot checks on that form. |
| Google Analytics | Visit statistics for the smithworks.app website. |
| Microsoft Clarity | Heatmaps and session recordings of smithworks.app website visits, with form entries masked. |
| Expo | Mobile app builds, delivery of compatible app updates, and push notification delivery. |
| Google Firebase Cloud Messaging | Delivering push notifications to Android devices. |
| Google Sign-In | Optional sign-in with a Google account. |
| Intuit (QuickBooks Online) | Optional accounting sync: sending issued invoices and payments to the business’s own QuickBooks Online company, and importing its customer list. |
| Square | Optional card payments: Tap to Pay on Android, Square Reader, QR code and payment links, and tips, under the business’s own Square account. |
| Stripe | Smithworks plan billing: checkout, payment processing, invoices and receipts, and the billing portal where owners update payment details or cancel. |
| Zapier | Optional automation: delivering the events the business’s own Zaps subscribe to, and receiving the customers, booking requests, and job notes those Zaps add. |
When Google Calendar is connected, Smithworks reads free/busy time without displaying meeting titles and creates or updates a dedicated Smithworks calendar. OAuth credentials are stored encrypted. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
We do not sell personal information, share it for cross-context behavioral advertising, or use third-party advertising or analytics SDKs in the current app. Google Analytics and Microsoft Clarity run only on the smithworks.app website pages described above, with Google signals and ad personalization turned off. We may disclose information when required by law or reasonably necessary to protect users, the service, or others.
Storage, security, retention, and deletion
Data is encrypted in transit and protected by authentication, business-access controls, and restricted administrative access. Authorized operators and infrastructure providers can access readable records when necessary to operate, secure, or support Smithworks. The service does not provide end-to-end encryption that prevents operator access.
Customer codes and PINs that you choose to store are kept apart from job records and encrypted with a dedicated key. The app shows one only to a team member the owner has allowed, after a one-time code sent to that member's sign-in email, and it records who revealed which code and when. Operators can still access these records when necessary to operate, secure, or support Smithworks.
We keep active account and business data while the account is in use. In-app deletion removes the active account and associated Smithworks data when the request succeeds. Verified requests submitted through the web are generally completed within 30 days. Limited backups and security or provider logs may remain until overwritten under normal retention schedules, isolated from ordinary product use. We may retain information longer when required for security, fraud prevention, legal compliance, or resolving a dispute.
When a free trial or plan ends, the business’s records are kept and can still be viewed, but not changed, until a plan starts again. Job photos are the exception: they are deleted 90 days after the trial or plan ends unless a plan is started before then. Deleting the account deletes its billing customer at Stripe, which also cancels any active plan; Stripe keeps the payment and invoice records it is required to keep under its own privacy policy.
Events already published to Google Calendar remain in the user's Google account until removed there. Invoices, payments, and customers already sent to QuickBooks Online remain in the user's QuickBooks company until removed there. Events already delivered to Zapier remain in the user's Zapier account and the apps their Zaps sent them to until removed there. See the account deletion page for the exact process and deletion scope.
Waitlist details are kept in our email list with Resend and in our inbox. To leave the waitlist and have your details removed, reply “unsubscribe” to any waitlist email or write to [email protected].
Your choices and controls
- Edit business, customer, job, and document information in the app.
- Disconnect Google Calendar from Settings.
- Revoke Smithworks’ access from your Square account at any time.
- Update payment details, see receipts, or cancel a plan under Plan & billing → Manage billing on the Smithworks website.
- Disconnect QuickBooks Online from Settings, or remove Smithworks from the connected apps in your QuickBooks company.
- Delete a Zapier key from Settings, which turns off every Zap connected with it.
- Deny optional foreground-location, camera, photo, or notification permission.
- Block or clear cookies in your browser, or install the Google Analytics opt-out add-on, to stop website analytics.
- Delete the account in Settings or request deletion on the web.
- Ask to access, correct, or delete personal information by emailing [email protected]. We may verify identity before acting on a request.
Children and geographic processing
Smithworks is a business tool for adults and is not directed to children under 13. We do not knowingly create accounts for children. Smithworks is operated in the United States, and providers may process information in the United States or other locations where they operate.
Policy changes
We may update this policy as Smithworks changes. We will update the date above and provide additional notice when a change materially affects how personal information is handled.
Contact us
Privacy questions and requests can be sent to Ecommerce Maven LLC at [email protected].