SnipInvoiceSnipInvoice Privacy Policy
Effective 25 August 2026. Version 2026-08-25. (Supersedes 2026-08-16. This version names the company, adds the contact address, corrects the sign-in methods, and states the no-selling commitment as its own section.)
SnipInvoice is operated by Alphatek Solutions LLC, a limited liability company registered in Texas, United States.
Questions about anything on this page: <support@snipinvoice.com>. A person answers.
SnipInvoice turns what a contractor says at a job site into an invoice. Doing that means a recording is made. We do not keep it — it becomes text within seconds and the audio is discarded. 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 the audio is never kept, 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 Google Firebase | To sign you in |
| Your name, if you sign in with Google and Google releases it | To address you in the app |
| 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 |
Sign-in is by Google, or by email and password. Those are the two methods that exist today. If you use Google, we receive the email address and name that Google releases and nothing else — no access to your Google account, contacts, or anything in it.
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 |
| Scanned pages and the invoice PDFs we generate | Until you delete them, or on account deletion |
| A device identifier we generate — a random value stored on your phone, not a hardware serial | For as long as the app is installed |
| 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 do not keep the audio. When you record a description of a job, that recording goes to our server, straight on to OpenAI to be turned into text, and is then discarded. It is never written to storage, a backup, or a cache. The only thing kept is the written text.
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.
Recording happens only while you hold the button. Never in the background, never continuously, never started by us.
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. Their published documentation states that data sent through their API is not used to train their models, and that their transcription service keeps no abuse-monitoring logs under standard settings. We state that because it is what they document; we cannot describe what happens inside their systems beyond what they publish.
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
Card payments are handled entirely by Stripe. When your client pays an invoice by card, they enter their details on a page hosted by Stripe. The card number never passes through SnipInvoice, is never stored by us, and is never visible to us. There is no code in this product that could receive one.
What we receive back from Stripe is whether a payment succeeded, how much, and when — enough to mark your invoice paid, and nothing more.
The money goes to you, not to us. Payments settle into your own Stripe account. We are not in the payment path and we never hold your money.
If you record a cash or cheque 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 and scanned pages into text and invoice details. This is the only provider that receives audio, and it is not stored by us or, per their documentation, retained by them | United States |
| Google Firebase | Signs you in and holds your account identity. It is how "log in with Google" and email-and-password log-in work | United States |
| Stripe | Card payments from your clients, and paying that money out to you. They hold the card details; we never do | United States |
| Railway | Runs the application server and the database — where your invoices and clients are stored | United States |
| Cloudflare R2 | Stores your logo, your scans and the invoice PDFs we generate. No audio, 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. Settings → Delete account. 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 <support@snipinvoice.com> 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
Settings → Delete account. It takes effect immediately; there is no waiting period and nobody to email.
What is destroyed:
- Your log-in is revoked and your authentication record is deleted. You can no longer sign in, and neither can anybody else.
- Your personal details are erased or irreversibly scrambled — your name, email and phone on your profile.
- Your clients' personal details are erased or scrambled too. They never agreed to be in our database, so they do not stay in it.
- There is no stored audio to delete, because none was ever kept.
What survives, and why it is not our convenience:
Invoice, line-item and payment records are kept. 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.
What remains afterwards is a financial record that no longer identifies you or your clients personally.
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 <support@snipinvoice.com>
Privacy questions are answered by a person, not a form.
Version 2026-08-25. Superseded versions are archived and remain available — if you agreed to an earlier one, that is the one that governed you at the time.