Privacy Policy

When you create an account, we collect:

• Email address (email/password sign-in)
• Name (display name, first/last name for reports)
• Phone number (phone sign-in or multi-factor authentication)
• Apple ID token (Sign in with Apple — we receive only the token; Apple may anonymize your email)
• Google account info (Sign in with Google — name, email, profile photo)
• Job title and company information you voluntarily enter (name, address, website, contact info, report title) — used only to populate professional reports you generate

• Floor plan drawings, sketches, CAD files, and annotations you create
• Measurement data (dimensions, labels, tags, notes) you enter
• Photos and videos you capture or import within the App
• Photo markup annotations (drawings, text, stickers)
• Document files you import (PDF, DXF, DWG, SVG, DOCX)

We collect location-related data in the following ways:

• Photo GPS: GPS coordinates are optionally attached to photos you capture within the App. This data is stored in your project files.
• Project addresses & coordinates: When you add a project address, we geocode it to latitude/longitude coordinates for map display. On iOS, this uses Apple's on-device geocoder. On the web dashboard, addresses are sent to the Google Maps Geocoding API. Coordinates and a geohash are stored in Firestore.
• Team member location: If you use the Project Map feature, your current device location may be shared with your team members in real time. Location data is written to Firestore under your team's namespace and is visible to all team members. Location snapshots older than 10 minutes are automatically filtered out of the display.
• Geofence notifications: The iOS app may monitor up to 20 project locations (200-meter radius) to send you local arrival notifications. This processing happens entirely on your device — no geofence data is sent to our servers.
• Weather forecasts: When viewing project locations on a map, we send the project's coordinates to the Open-Meteo weather API to display current weather conditions. No personal information is included in these requests.

Location data is never used for advertising or sold to third parties.

With your consent via Apple's App Tracking Transparency (ATT) prompt, we collect:

• App session events (session start, session end, screen views)
• Feature usage events (which tools you use, export types, layout types)
• Performance timing (load times, sync durations)
• Error and crash breadcrumbs

Subscription status (free, solo, business/team), entitlement identifiers, and renewal dates via RevenueCat. RevenueCat processes payments through Apple's App Store — we never receive or store your payment card information.

If you are part of a team:

• Your assigned role (admin, manager, member, collaborator)
• Team membership, invitation records, and audit log entries
• Project presence indicators (which layout you are currently editing, approximate edit activity)
• Remote cursor position (grid coordinates, shared only within active collaborative sessions and not persisted)
• Real-time device location when using the Project Map feature (shared only with team members, auto-expires after 10 minutes of inactivity)

If you choose to sync your project schedule to Google Calendar, we request access to your Google Calendar via OAuth authorization. This allows us to:

• Create a shared team calendar in your Google account
• Create and update calendar events for project phases and milestones
• Share the team calendar with your team members (using their email addresses stored in your team profile)

If you use Business Tools (available on iOS and the web dashboard), we store:

• Customer records (name, email, phone, company, address) you enter
• Estimates and invoices (line items, amounts, dates, status)
• Recurring invoice schedules (frequency, next run date, auto-send preferences)
• Payment records (amount, method, reference number, date)
• Invoice template settings (logo, colors, footer text, payment terms)

This data is stored in Firebase Firestore under your team's or user's namespace and is accessible only to authorized users based on role permissions (admin and manager for invoices and payments; all members for customers and estimates).

If you connect a Stripe account to collect payments from your clients, the following data is processed:

• Stripe Connect account ID and onboarding status (stored in Firestore)
• Payment capability flags (charges enabled, payouts enabled, ACH enabled)
• Your clients' payment information (card numbers, bank account details) — collected and processed entirely by Stripe; we never see or store this data
• Invoice payment status and Stripe invoice IDs (synced back to Firestore when payments are completed)

If you connect QuickBooks Online, the following data is exchanged:

• OAuth tokens (access and refresh tokens stored in Firestore, used to authenticate API calls)
• QuickBooks company ID and realm ID
• Customer records synced to QuickBooks (name, email, phone, company, address)
• Invoice records synced to QuickBooks (line items, amounts, dates, customer reference)

If you use the payroll management features on the web dashboard, we store:

• Worker records (name, email, phone, classification, hire date, pay rate)
• Tax withholding details (filing status, state, W-4 information)
• Last four digits of Social Security numbers (stored for identification purposes only)
• Timesheet entries (hours worked, project allocation)
• Pay run records (gross pay, tax calculations, deductions, net pay)
• Compliance documents (I-9, W-4, insurance certificates — completion status and dates only, not document contents)

If you use the lead management and marketing features, we process communication data to send messages and place calls on your behalf:

• SMS messages: When you or the auto-response system sends a text message to a lead or customer, we transmit the recipient's phone number and message content to Twilio for delivery. Twilio assigns a unique message SID for tracking delivery status.
• Voice calls: When you place an outbound call to a lead or customer through the App, we use Twilio to connect the call. Your business name is displayed on the recipient's caller ID via Twilio Branded Calling so customers can identify your business. We transmit the recipient's phone number and your registered business name to Twilio to facilitate the call. Call metadata (call duration, timestamp, and completion status) is logged in Firestore under your team or user namespace.
• Email messages: When you or the auto-response system sends an email to a lead or customer, we transmit the recipient's email address, subject line, and message content to Resend for delivery.
• Communication logs: Each sent SMS, voice call, or email is logged as an activity record in Firestore under your team or user namespace, including the communication type, summary, timestamp, and sender identity.
• Auto-response settings: If you enable auto-response, we store your message templates, frequency preferences, and enabled/disabled status on your team or user document in Firestore.

Users on the free plan are shown ads via Google AdMob. AdMob may collect device identifiers and usage data for ad personalization, subject to your ATT consent.

If a team administrator connects your Google Business Profile (Business Tools → Settings → Integrations), we access your business's Google reviews through Google OAuth so you can read and respond to them inside Measure Tech PRO. With your authorization we access:

• Your Google Business Profile account and location information (account and location resource names, location titles and addresses) — used to list your locations and map each to a market
• Reviews on your mapped locations: the reviewer's public display name and profile photo, the star rating, the review text, and review and response timestamps
• Owner responses you write in the app, which we post publicly to Google on your behalf as your business's reply

We use this data solely to display your reviews, let you reply to them, and produce your own reputation reporting across markets. Synced reviews are stored in Firebase Firestore under your team's namespace so the app can display them; a review removed on Google is hidden on your next sync.

If a team administrator connects Facebook (via Facebook Login), we access your Facebook Page's recommendations through the Meta Graph API so they appear alongside your other reviews. With your authorization we access your list of Pages and, for each page you map to a market, the recommendation type (positive or negative), review text, the reviewer's public display name, and timestamps. The Facebook access token is stored server-side in the same encrypted, access-restricted manner described above and is never shared with third parties. We use this data only to display your reviews and for your reputation reporting.

If you enable Yelp and set a market's Yelp business, we retrieve that business's public rating and up to three recent review excerpts through the Yelp Fusion API to display in the app and include in your reputation reporting. Yelp access is read-only — Yelp does not offer a way to reply to reviews through its API. Yelp review content is used only for display and is shown with attribution and a link back to Yelp.

The App integrates the following third-party services, each with their own privacy policies:

Measure Tech PRO's use and transfer of information received from Google APIs — including Google Calendar and the Google Business Profile API — will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically:

• We use Google user data only to provide and improve the features you have enabled — syncing your project schedule to Google Calendar, and syncing and replying to your Google Business Profile reviews — as described in this policy
• We do not use Google user data for advertising, market research, or email campaigns
• We do not sell Google user data, and we do not transfer it to third parties except as necessary to provide these features, to comply with applicable law, or as part of a merger or acquisition in which the successor honors this policy
• We do not allow humans to read your Google user data unless you give explicit consent (for example, to troubleshoot a support request you raise), it is necessary for security purposes, or it is required by law
• We do not use Google user data to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models. The optional "Draft with AI" reply feature sends a single review's text to Google Vertex AI at the time of your request to generate a suggested reply for you; it is not used for model training

• Local storage: Project files, drawings, and preferences are stored on your device in the app's sandboxed container and optionally synced via iCloud.
• Cloud storage: If you use team features, project data and photos are stored in Google Firebase (Firestore and Firebase Storage), hosted in the United States.
• Per-user isolation: Each user's data is stored in a namespace keyed to their unique user ID. Other users, including team members below admin level, cannot access your personal account data.
• Security measures: Data in transit is encrypted via TLS. Firebase Security Rules restrict read/write access to authenticated users and enforce role-based permissions. Multi-factor authentication (MFA) is available for additional account security.
• Retention: Your project data and account information are retained until you delete your account. Deleted account data is purged from Firebase within 30 days.

You can permanently delete your account and all associated data from within the App: Account → Delete Account. This removes your Firebase Auth credentials, Firestore user document, team membership records, and queued uploads.

Your project files are stored locally on your device and can be exported at any time via the App's export features (PDF, PNG, DXF). You may contact us at the address below to request a copy of your account data held in Firebase.

You can opt out of analytics at any time: Account → Privacy → Analytics. This immediately stops all analytics event collection. Previously collected anonymized events are not retroactively deleted from aggregate reports.

If you have connected Google Calendar, you can revoke access at any time by visiting Google Account → Third-party apps and removing Measure Tech PRO. Previously synced calendar events will remain in your Google Calendar but no new events will be created or updated.

If you have connected a Stripe account, you can disconnect it from the web dashboard settings. This removes the Stripe account link from your team record. Existing invoices and payment history remain in Firestore for your records. To fully close the Stripe Express account, visit your Stripe Dashboard.

If you have connected QuickBooks Online, you can disconnect it from the web dashboard settings. This revokes the stored OAuth tokens and stops all future syncs. Previously synced data in QuickBooks is not affected. You can also revoke access from Intuit Account → App connections.

You can disconnect any connected review platform from Business Tools → Settings → Integrations. Disconnecting revokes and deletes the stored access token for that platform and stops all further review syncing. For Google, you can additionally revoke access from your Google Account permissions; for Facebook, from your Facebook Business Integrations settings. Reviews previously synced for display remain in your team records until you delete your account.

Recipients of SMS messages sent through Measure Tech PRO can opt out at any time by replying STOP to any message. Twilio automatically processes opt-out requests and prevents further messages from being delivered to that number. You can also disable auto-response and follow-up messages from your account settings. Message frequency varies based on your communication preferences. Standard message and data rates may apply.

Recipients of voice calls can request not to be called at any time. Business users can mark any contact as "do not contact" in the CRM, which prevents future calls and messages to that number. All outbound calls display the business name via Twilio Branded Calling so recipients can identify who is calling. Calls are placed only to customers with an existing business relationship or leads who have voluntarily submitted their phone number.

Adjust your ATT preference via Settings → Privacy & Security → Tracking on your device. Upgrading to a paid plan removes all advertising from the App entirely.

If you are a California resident, you have the right to:

• Know what personal information we collect and how it is used
• Request deletion of your personal information
• Opt out of the "sale" of personal information (we do not sell personal data)
• Non-discrimination for exercising your privacy rights

To exercise these rights, contact us at the address in Section 8.

If you are located in the European Economic Area, you have the right to access, rectify, erase, restrict processing, and port your personal data. Our legal basis for processing is:

• Contract performance — account creation and app functionality
• Legitimate interest — security, fraud prevention
• Consent — analytics, advertising (withdrawable at any time)

To exercise GDPR rights, contact: privacy@measuretechpro.com

Measure Tech PRO is not directed to children under 13 (or under 16 in the EEA). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it promptly.

We may update this Privacy Policy from time to time. We will notify you of material changes by updating the "Last Updated" date at the top of this page and, where appropriate, displaying an in-app notice. Continued use of the App after changes are posted constitutes your acceptance of the updated policy.

If you have questions, concerns, or requests regarding this Privacy Policy: