SnipInvoice Privacy Policy
Effective 3 October 2026. Version 2026-10-03. (Supersedes 2026-08-25. This version names Railway as the host, including Postgres and object storage, names RevenueCat and Apple and Google for in-app subscriptions, describes the device identifier the app sends, and states that the app signs in with email and password. The website also offers Google sign-in.)
DRAFT — NOT YET REVIEWED BY A LAWYER. Every factual statement below was written against the code and checked against it again on this date. What has not happened is a qualified review of whether it says everything it must, in the form it must. Publish only after somebody qualified has read it.
SnipInvoice is operated by Alphatek Solutions LLC, a limited liability company registered in Texas, United States.
Questions about anything on this page: [email protected]. A person answers.
SnipInvoice turns what a contractor says at a job site into an invoice. Doing that means a recording is made. We don't store your voice recordings. Audio is sent to our AI provider to turn it into text, and we don't keep it afterwards. That provider is OpenAI. OpenAI may keep API inputs for up to 30 days for abuse monitoring by default; we have no zero-retention agreement. What we keep is the text.
This policy is written to be read, not to be defensible. Where a plain sentence and a precise one differ, both are here.
1. We do not sell your data. Ever.
This is the section people skip to, so it comes first.
- We do not sell your data. Not to anyone, at any price.
- We do not rent, trade or license it.
- We do not share it with advertisers, ad networks or data brokers.
- We do not use it to build a profile of you, or to target you with anything.
- There is no advertising in SnipInvoice, so there is nothing to target.
This is not a policy we could quietly change — it is how the product is built. There is no advertising code in the app, no analytics profile of an individual contractor, no data-sharing agreement with anybody outside the table in §7, and no feature that would let us do any of it.
We make money one way: contractors pay us a subscription. That is the whole business model. If a company's revenue does not come from its users, it usually comes from selling something about them; ours comes from users, which is why this commitment costs us nothing to keep.
The only time data leaves this company is to the service providers in §7 who run parts of the product for us, or when we are legally compelled — and then only as far as we are compelled.
2. Who this is about, and the part that is unusual
There are two kinds of people in our database and only one of them signed up.
You, the contractor, are our customer. You created an account, agreed to these terms, and can export or delete everything at any time.
Your client is not our customer. They never installed anything, never agreed to anything, and their name, address, phone number and the amounts they were billed are in our systems because you put them there.
We treat that as the more serious obligation, not the lesser one. It is why we don't store your voice recordings, why the public quote page shows only what that person was already sent, why invoice PDFs carry no private notes, and why §1 exists.
3. Your clients' details are yours, not ours
The invoices, estimates, client records and amounts you create belong to you. We hold them to run the service for you and for nothing else.
Concretely, that means we do not:
- sell or share them (§1),
- use them to market to your clients — we never contact your clients at all,
- mine them to build a picture of your business for anybody else,
- or use them to train anyone's AI models (§5).
We never send anything to your clients. When you send an invoice it goes out through your own phone — your messages app, your email, your WhatsApp — from your number and your address. There is no server that emails your clients on your behalf, which is also why we never need their email address unless you choose to store it.
You can take it all with you at any time. One tap in Settings exports every invoice, estimate, client and line item as a single file (§8).
4. What we collect
Things you give us
| What | Why we have it |
|---|---|
| Your email address, and an account identifier from Firebase Authentication | To sign you in |
| Business details — company name, address, phone, tax ID, licence number, logo | These are printed on your invoices. A copy is frozen onto each document when it is created, so a document you already sent never silently changes when you move offices |
| Client records — name, email, phone, address | So repeat customers do not have to be re-entered |
| Invoices, estimates, line items, tax rates and payments | The product |
| Private notes on a client | Never printed on any document and never shown to anyone but you |
The SnipInvoice app signs you in with email and password, through Firebase Authentication. The website also offers Continue with Google. That button uses Firebase's Google sign-in. Google shares with Firebase the name, the email address, the Google account id, and the profile photo URL on that Google account. We store the Firebase user id that Firebase creates for the sign-in, the email address, and a phone number if the sign-in token includes one. We do not keep a separate name, and we do not store the profile photo.
Things created by using the app
| What | How long we keep it |
|---|---|
| Audio recordings of what you said | Not kept at all — see §5 |
| The transcript of that audio, and the invoice details pulled out of it | Until you delete the invoice or your account |
| Invoice PDFs we generate | Kept with the invoice record. Deleting the account does not remove them. The product has no separate expiry for those files |
A device identifier. On Android the app reads ANDROID_ID. On iOS it reads identifierForVendor. If the phone cannot read that value, the app uses a random id. The website uses an id generated in the browser. We store it on your user record when the account is created at signup, and when accepting an invitation creates a new user. A later sign-in does not replace it by itself. If the app registers the device for the current session, that registration replaces the stored value. It is a licensing record. It is not used to allow or refuse a request, and it is not used to count free-plan invoices. It is not an advertising identifier |
Until that login is deleted, which clears it |
| Crash reports, if the app fails | Only if crash reporting is switched on for the build you are using |
What we never collect
No location. No contacts — the contact picker runs inside your phone's operating system and hands back only the one person you chose; we are never granted access to your address book. No advertising identifiers. No browsing or cross-app tracking. No card numbers — see §6.
5. Recording, and what happens to it
This is the section that matters most, so it is stated plainly.
We don't store your voice recordings. Audio is sent to our AI provider to
turn it into text, and we don't keep it afterwards. When you record
a description of a job, that recording goes to our server, straight on to
OpenAI to be turned into text. It is never written to our storage, a backup,
or a cache. OpenAI may keep API inputs for up to 30 days for abuse monitoring
by default, and we have no zero-retention agreement, so the audio is not gone
from every system the moment we finish with it. The only thing we keep is the
written text. The transcription model is OpenAI Whisper (whisper-1). GPT-4o
turns that transcript into invoice details. We store the transcript. We do
not store the audio.
That is enforced by the code, not by a promise. An automated test fails the build if any code path tries to save a recording, and it reads the source rather than watching one request — because the change to guard against is the one somebody adds later in good faith to debug a bad transcription.
You tap the microphone to start, and tap it again to stop. Recording does not happen in the background, continuously, or because we started it.
What we will not claim
A microphone records whatever is audible, and we will not pretend otherwise. If somebody is standing beside you and speaking while you record, they may be on the audio that goes to OpenAI. No code we write can change that, so we do not claim it does.
We could have written a comfortable sentence here. It would not have been true, and a privacy policy that is not true about the thing it is most tempting to lie about is worth nothing.
What we do instead is shape what gets said. The record screen asks you to say who it's for, what you did, and what it costs — a description of work, spoken to your own phone, not a conversation. That is a real reduction in what ends up on the recording, and it is honest about being an instruction rather than a guarantee.
Recording lawfully is your responsibility. In some US states, recording a conversation requires the other person's consent. SnipInvoice is built for one person dictating a description of work; the person holding the phone is the person who has to comply with the law where they are standing.
Recording is optional. Every invoice can be typed instead, and the app is fully usable without ever recording anything. If you never record, you are never asked to consent to recording.
Who else hears it
OpenAI, a service provider in the United States, converts the recording to text. We don't store the recording after that handoff. OpenAI may keep API inputs for up to 30 days for abuse monitoring by default, and we have no zero-retention agreement. Re-check that retention against OpenAI's current documentation before this draft is treated as final.
What we keep instead is the transcript — the written text — with the invoice it produced. That is what lets the app show you exactly what it heard, and what tells us when it is mishearing trade vocabulary. It is never sold, never shared, and never used to identify anyone.
6. Payments — we never see a card
SnipInvoice plan fees on the website. If you choose a paid plan on snipinvoice.com, Stripe hosts the payment page. You confirm the price there before you are billed. Until Stripe is connected, the account page says card billing is not connected and nothing is charged. The card number never passes through SnipInvoice. We store whether the plan is active, past due, cancelled, or refunded. The iPhone and Android apps do not sell SnipInvoice plans through Stripe. When the stores are connected, those plans use Apple and Google in-app purchase.
In-app subscriptions. On the iPhone app, Apple processes the payment for a SnipInvoice subscription. On the Android app, Google does. RevenueCat tells us whether that subscription is active. We do not receive the card number from Apple, Google, or RevenueCat.
Your customers do not pay invoices by card unless that switch is on. You record payments you have already received (cash, check, bank transfer, or a card taken outside the app). A customer payment link stays switched off until online payments are turned on. When that switch is on, the customer pays on a page Stripe hosts, into your own Stripe account. We never hold that money. What we receive back is whether the payment succeeded, failed, or was refunded, how much, and when.
There is no code in this product that receives a card number.
If you record a cash or check payment yourself, that is just a number you typed into your own records.
7. Who else touches the data
We use these companies to run the service. Each receives only what it needs to do its job, and none of them may use it for anything else.
| Provider | What it handles, and why | Where |
|---|---|---|
| OpenAI | Turns your recordings into text with Whisper (whisper-1) and drafts invoice details with GPT-4o. This is the only provider that receives audio. We do not store the audio. We store the transcript. OpenAI may keep API inputs for up to 30 days for abuse monitoring by default; we have no zero-retention agreement |
United States |
| Google Firebase | The app signs you in with email and password (Firebase Authentication) and holds your account identity. The website also offers Continue with Google. Google shares with Firebase the name, the email address, the Google account id, and the profile photo URL. We store the Firebase user id, the email, and a phone number if the token includes one. We do not store the name or the profile photo | United States |
| RevenueCat | Tells us whether an in-app subscription from Apple or Google is active. The app user id is the Firebase account id | United States |
| Apple | Processes payment for an iPhone in-app subscription | United States |
| Processes payment for an Android in-app subscription | United States | |
| Stripe | Plan fees on the website, when Stripe is connected. Customer invoice payments only when that switch is on. Stripe holds the card details; we never do | United States |
| Railway | Runs the application, the Postgres database that stores your invoices and clients, and the object storage that stores your logo and the invoice PDFs we generate. No audio is stored there, because we keep none | United States |
That is the complete list of companies that receive your data. If we add one, this table changes and §11 says how you will hear about it.
Not on this list, deliberately: any advertiser, any analytics company that profiles individuals, any data broker. See §1.
If you are outside the United States
The service runs in the United States, so your data is processed there. If you are in the UK or EU, that transfer happens under the standard contractual clauses each provider above operates.
8. Your rights, and how to use them
Export everything. Settings → Export. You get every invoice, estimate, client, line item, transcript and extraction as a single file. No request form, no waiting, no asking us.
Delete your account and your data. In the app, open More, then Delete account. The same screen is under More, then Settings, then Delete account. Type DELETE to confirm. The owner closing the account closes the business. An invited team member using that same Delete account screen deletes only their own login. The business stays. Without the app, an account owner signs in at snipinvoice.com/account, opens Business, then Profile, and chooses Delete account, then types the business name. Anyone can also email [email protected] from the email address on the account and ask us to delete it. The public page at snipinvoice.com/delete-account says the same thing. What happens is set out in §9 in full, because "delete" is a word people use loosely and we would rather be exact.
Correct anything. Business details, clients and drafts are editable in the app at any time.
If you are a contractor's client and want to know what is held about you, or want it removed — contact the contractor who billed you. They collected it and they control it. Where the law gives you a right directly against us, we will honour it: write to [email protected] and we will act on it, working with the contractor whose records you appear in.
Depending on where you live you may also have the right to object to processing, restrict it, withdraw consent, or complain to a data-protection authority. Withdrawing consent to recording is done by not recording — the app works without it.
9. What deleting your account actually does
In the app, open More, then Delete account. The same screen is under More, then Settings, then Delete account. Type DELETE to confirm. What that does depends on who you are.
The owner closes the business. On the website the owner signs in, opens Business, then Profile, chooses Delete account, and types the business name. It takes effect when you confirm. There is no waiting period on that path.
An invited team member uses the same Delete account screen to delete only their own login. The business, its clients, invoices, estimates, voice transcripts, logo, subscription, and every other person stay as they are. If this is their only SnipInvoice business, their sign-in is revoked and that Firebase Authentication user is deleted, and the email, phone, and stored device identifier on that user record are cleared. If they also belong to another SnipInvoice business, they lose this membership and keep that other sign-in. The website Delete account control is the owner's. A member who cannot use the app emails us instead.
If you cannot use the app or the website, email [email protected] from the email address on the account and ask for deletion.
What is destroyed when the owner closes the business:
- The owner's log-in is revoked and that Firebase Authentication record is deleted. Someone who also belongs to another SnipInvoice business keeps their own sign-in and loses access only to the business that was closed. People who belonged only to the closed business are anonymized.
- Email, phone, and the stored device identifier are cleared on the people whose account belonged only to this business. The business name, address, phone, email, tax ID, and licence number on the business profile are cleared.
- Your clients' personal details on the customer list are erased or scrambled too. They never agreed to be in our database, so they do not stay on that list. A document you already sent keeps the details that were printed on it.
- Voice transcripts are deleted.
- There is no audio in our storage to delete. We don't store your voice recordings. OpenAI may still hold API inputs for up to 30 days for abuse monitoring; we have no zero-retention agreement. If a recording file is still in storage, we try to remove it. A logo file is removed the same way, unless a document we keep still shows that logo. A failed storage delete is logged and the account still closes.
What survives, and why it is not our convenience:
Invoice, estimate, line-item and payment records are kept as they were sent, including the customer and business details printed on them. The invoice PDFs stored with those records are kept too. Deleting the account does not remove them, and the product has no separate expiry for those files. They are the record of real financial transactions between you and the people who paid you. Tax authorities require them to exist — and so, potentially, does a client who paid an invoice and later needs proof of it. Deleting them at one party's request would destroy the other party's evidence of a transaction they were part of.
The deletion audit row keeps the email of the person who confirmed. Older audit rows are kept as well. Each one keeps the name and email that were recorded when that action happened. Consent records are kept. A consent row records who accepted, which document and version, how they accepted, when, and the IP address if one was stored. Those rows are not deleted when an account closes, and they are not deleted when a member deletes their login. A member who deletes only their login leaves the business records, including invoices, PDFs, clients, and transcripts, exactly as they were. The audit row for that deletion keeps that member's email.
If you want a copy of everything first, export it before you delete — the export is instant and the deletion is not reversible.
10. Security, and its limits
Data is encrypted in transit, and encrypted at rest by our database and storage providers.
Each contractor's data is walled off inside the database itself, not by application code remembering to filter. A request for another contractor's invoice is indistinguishable from a request for one that does not exist. That separation is enforced by the database and checked by automated tests that deliberately try to break it.
Access to production systems is restricted to people who need it.
No system is perfectly secure, and a policy claiming otherwise is not being straight with you. If a breach affects personal data we will tell affected contractors, and any regulator we are required to tell, without undue delay.
11. Children, changes, and contact
Children. SnipInvoice is a tool for running a business. It is not directed at anyone under 18, and we do not knowingly collect data from children.
Changes. If this policy changes in a way that matters — especially anything about recording, what we keep, or who receives your data — we will say so in the app, before the change takes effect, rather than quietly reposting this page with a new date. Every version is archived.
Contact.
Alphatek Solutions LLC Texas, United States [email protected]
Privacy questions are answered by a person, not a form.
Version 2026-10-03. Superseded versions are archived and remain available — if you agreed to an earlier one, that is the one that governed you at the time.