InvoiceSnap · Privacy
Privacy Policy
Effective date: September 28, 2026
This policy explains how InvoiceSnap handles information when you use the InvoiceSnap app and the invoicesnap.work website. The app is published under the 731labs brand; the App Store seller is Kazakov Invent Corp.
Information you enter or create
Depending on the features you use, the app can process account identifiers and email; business and customer names, addresses, phone numbers, email addresses and tax identifiers; invoice, estimate and credit-note details, line items, amounts, notes, payment instructions and payment records; time and expense details; and logos, signatures, receipt images or other media you add. Free-text fields and images may contain information beyond these examples.
If you choose to import a contact, InvoiceSnap can request Contacts permission to read contact details you select and use them to fill a client record. The app also processes information you provide in support conversations and, when you use website forms or other site features, information submitted there.
Where information is stored
On your device
Core records are stored in the app’s local database so local invoicing can work without an account or network connection. Some preferences, queued changes and files are also stored locally.
Cloud services
When you sign in and use connected features, account and business records are synchronized with Supabase, which provides authentication, database and file storage. The records involved can include business profiles, clients, invoices and their line items, payments, saved items, recurring schedules, time entries and expenses. Logos and other media may be uploaded for sync or document rendering. Some uploaded logo files are stored in a publicly addressable storage bucket; do not upload a logo that must remain confidential. Shared invoice or estimate links and PDFs expose the document information you choose to share to their recipients. Recipients can retain or forward a copy outside InvoiceSnap.
InvoiceSnap is not end-to-end encrypted: cloud service processing is needed to provide cloud features.
Optional features and service providers
These providers receive information when the related feature is used or enabled. Their processing is governed by their own service terms and privacy practices.
- AI estimates: the job description and any photo you submit are sent from InvoiceSnap’s server to Google Gemini to generate estimate suggestions.
- AI logos: the business name and the prompt details you choose, such as industry and colors, are sent through OpenRouter to a Google image model to generate a logo.
- Client information assistance: if you use the website-based client enrichment feature, the website address you provide is retrieved through Firecrawl and content used to generate extracted client details is processed through OpenRouter.
- Support chat: conversation text, session identifier, language and page context are stored through Supabase. Automated replies and related retrieval may be processed by OpenRouter and Google. When an operator is notified or takes over, configured support notifications may send the message and conversation context through Telegram.
- Analytics and diagnostics: PostHog receives product events and identifiers, including a generated identifier that may be linked to a verified account identifier after sign-in. Sentry receives crash, error and performance diagnostics; the app applies a client-side filter to diagnostic payloads. EAS Observe receives selected performance measurements and limited product events.
- Advertising attribution: AppsFlyer and Meta SDKs support attribution measurement. On iOS, their setup follows the App Tracking Transparency prompt, and permission-dependent advertising identifiers and event linking are gated by the result. Denying permission does not disable every analytics or diagnostic feature or prove that no SDK network request occurs.
- Purchases and billing: Apple processes App Store purchases. RevenueCat processes subscription and entitlement information. If you use web billing or a hosted invoice payment feature, Stripe processes the related billing, invoice and payment information.
- Reminders and notifications: if you enable invoice reminders, the recipient and reminder details are sent through Resend for email delivery. If you enable push notifications, a device push token is registered with the notification infrastructure.
- Website analytics: the marketing website uses Google Analytics 4 to measure website visits. Browser and device information and analytics identifiers may be processed by Google according to the site configuration and your browser settings.
How information is used
Information is processed to create and manage business documents; synchronize records and files; provide the optional AI, support, link-sharing, reminder, purchase and billing features you choose; operate and secure the app; diagnose failures and measure product performance; and measure marketing attribution where enabled. Information in a document or support message can be visible to the recipients or service providers needed for the feature you request.
Choices and account deletion
- You can use local invoicing without creating an account. You can choose whether to sign in and whether to use optional connected features.
- You can change the iOS tracking permission in device Settings. That permission controls permission-dependent attribution behavior; it does not turn off PostHog product analytics, crash diagnostics, or other features.
- You can manage app permissions through your device settings and choose which documents, photos or contact details to add or share.
- The app includes a Delete Account flow at More → Delete Account in the Account section. It clears app-owned local data and files and attempts to remove account-owned cloud storage and account data. Errors can be surfaced for retry. This does not promise immediate or total deletion from third-party billing systems, support conversations, provider backups, exported files or copies held by document recipients. Some security and usage-control records can be retained independently of sign-out.
Retention
There is no single retention period for every data type. Local records remain on the device until removed through app or device controls. Cloud and feature data are retained according to the feature, account state and provider processes. Account deletion initiates the app’s local and account-owned cloud cleanup described above; it does not establish a fixed deletion deadline for every provider, backup, transcript or recipient copy.
Security
The app uses account-scoped access controls for cloud records and filters diagnostic events before sending them. These are technical safeguards, not a guarantee that every transmission, provider record or copy is private or inaccessible.
Privacy requests and contact
For a privacy question or account request, open InvoiceSnap and go to More → Help & support → Contact support. The app’s support conversation is the currently verified contact channel. We do not publish a support email address or street address on this page.
Policy updates
We may update this policy as the app and its data flows change. The effective date at the top identifies the current version.
Related pages: Terms of Service · Support.