Effective August 21, 2026
Privacy Policy
Officer One (formerly PocketCop) is built by bigBespoke LLC for working law-enforcement officers. You extend trust for a living. This page is where we earn it: what we collect, why, what we never do, and the controls you keep.
The whole policy in three sentences. Your drafts, questions, and records belong to you and are used to run the app for you — never sold, never used for ads, never used to train public AI models. Your department can see that you hold a seat, never what you write. Deleting your account deletes your work, immediately, from inside the app, no ticket required.
Contents
1. Who we are
Officer One is published by bigBespoke LLC, a United States company. The product was launched as PocketCop and renamed Officer One in August 2026 — same company, same accounts, same commitments. We operate the website officerone.app and the Officer One apps for iOS and Android. For anything in this policy, bigBespoke LLC is the data controller.
2. What we collect
In plain terms: your account details, the work you create on purpose, a technical trail of taps and versions so we can support you, and billing status. No contact scraping, no background collection, nothing runs while the app is closed.
Account information. Email address, name, and — if you choose to add them — rank, agency, and state. Guest mode works without any of it.
Your work product. What you deliberately create in the app: warrant drafts and their facts, narrative drafts, questions you ask and the answers you receive, FTO trainees and daily observation reports, department forms you upload as templates, and PDFs the app generates for you. This is the most sensitive data we hold and every rule in this policy is written with it in mind.
The usage trail. A first-party event log — which tool you opened, when, on which app version. Details in section 7.
Technical and crash data. If the app crashes, a crash report (stack trace, device model, OS version, app version) goes to our error-monitoring provider so we can fix it. Crash reports are configured to describe the failure, not to carry your drafts.
Billing. Payments run through Stripe. We see your subscription status, plan, and receipt metadata. Your full card number never touches our servers.
Support conversations. What you write to the team, kept as a transcript you can reread any time.
3. What we never do
- We never sell your data, rent it, or share it with data brokers. Not at any price.
- We never run ads and never embed advertising or cross-app tracking SDKs.
- We never use your drafts, questions, or records to train public AI models, and our contracts forbid our AI providers from doing so with content we send them.
- We never give your department, your chain of command, or anyone else access to your individual work product. A department admin sees seats, not substance (section 9).
- We never browse your work. Staff access is limited, logged, and tied to a reason — a support request, a legal obligation, or an abuse investigation.
- We never collect in the background. The app does work when you open it and stops when you close it.
4. AI processing
In plain terms: when you use an AI feature, the text you provided goes from our servers to our AI provider, a result comes back, and that provider is contractually barred from training on it.
The warrant builder, narrative tools, and Ask send the text you supply — and only what the feature needs — from our servers to our AI infrastructure provider (currently xAI) to produce your draft or answer. The exchange is server-to-server and encrypted. Under our agreements, the provider may not use your content to train its models and retains request data only transiently for abuse and reliability monitoring under its enterprise API terms.
You control what goes into a prompt. Enter the facts your case and your agency’s policy allow, the same judgment you apply to any drafting tool. The app’s output is a draft for your review — you remain the author and the affiant, and the AI-assistance disclosure inside the app describes this in the form some states now require.
5. Dictation and your voice
Speech-to-text uses your phone’s built-in recognition (Apple or Google). Depending on your device’s settings and language, the operating system may process audio on the device or on Apple’s or Google’s servers under their terms — that path belongs to your phone, not to us. We receive the text, not the audio. Officer One does not record, store, or transmit voice recordings, and the microphone is live only while you hold or toggle a capture control on screen.
6. Location
Location is optional and used once per request to suggest your state and county for warrants and law lookups. You can deny the permission and type a zip code instead — every feature still works. We store the jurisdiction you confirm (state, county), not coordinates, and we never track movement or maintain location history.
7. The usage trail
In plain terms: the app keeps a first-party log of which tools you used and when — your audit trail and our support record. It deletes with your account.
Officer One records feature events under your account: tool opened, draft created, PDF built, with timestamps and app version. We built this deliberately, for three reasons: it lets support diagnose a problem from evidence instead of guesswork; it gives your usage a factual record; and it tells us which tools earn their place. The trail is first-party — it lives in our database, feeds no advertising ecosystem, and is deleted with your account like everything else.
8. When you write to support
When you open a support thread, the teammate answering sees your message, your account record, and a summary of your usage trail (versions running, features used, work counts) so the first reply can be an informed one. We treat telemetry as context for helping you, never as material to quote back at you. Support transcripts stay in your inbox — closing a thread archives it, and writing again reopens it.
9. Departments and seats
In plain terms: your agency can pay for your seat. It cannot read your work.
When an agency covers its roster with a department plan, the department admin sees membership facts: who holds a seat (name and email), invite status, and the plan’s billing state. The admin does not see — and there is no toggle, tier, or request path that reveals — any member’s drafts, questions, law lookups, FTO records, or usage trail. Your work product stays yours whether you pay or your department does. If a department requires visibility into work product as a condition of coverage, that arrangement happens inside the department’s own systems, not through us.
10. Service providers
We use a short list of processors, each bound by contract to use your data only to provide their service to us:
| Provider | What it does | What it touches |
|---|---|---|
| Google Firebase (Google Cloud) | Authentication, database, file storage, hosting, functions — US region | Account data, work product, usage trail |
| Stripe | Payments and subscriptions | Payment details (card data stays with Stripe), billing status |
| xAI | AI drafting and answers | Text you submit to AI features; barred from training on it |
| Sentry | Crash and error monitoring | Crash reports, device/OS/app version |
| Zoho ZeptoMail | Transactional email (receipts, support notices) | Email address, message content we send you |
| Expo (EAS) | App builds and over-the-air update delivery | App binaries and update bundles — not your account data |
| Apple / Google | App distribution; on-device or OS dictation | Store account per their terms; dictation audio per section 5 |
If this list changes in a way that matters, we update this page and note it in the app’s What changed log.
11. Security
Your data is encrypted in transit (TLS) and at rest on Google Cloud infrastructure. Access rules are enforced at the database layer — your documents are readable by your authenticated account and no other user’s. Administrative access is role-restricted to named individuals, used for support and operations, and logged. Secrets and API keys live in managed secret storage, never in the app you install. Payment credentials are handled entirely by Stripe under PCI DSS. Copies of your recent work are cached on your own phone so the app works without signal; that cache is protected by your device’s security and removed when you delete the app.
No one can honestly promise zero risk. If a breach affects your data, we will notify you without undue delay, tell you what we know as we know it, and say plainly what we are doing about it.
12. Retention and deletion
In plain terms: your data lives while your account does. You → Delete account erases your work on the spot — self-serve, immediate, no ticket, no waiting period.
We keep your data while your account is active so your work is there when you need it. When you delete your account (You → Delete account, or by asking support), our servers immediately and permanently delete your warrants and their audit trails, narratives, chats, FTO records, usage trail, uploaded templates, generated files, profile, and login. This is a hard delete of the live records, not a deactivation; residual copies in operational backups expire on the backup cycle shortly after.
We retain two narrow categories after account deletion: billing and transaction records (tax and accounting law requires it) and support correspondence (kept as ordinary business records, for example to honor a refund dispute). Neither includes your work product.
13. Your rights
We extend the same rights to every user, whatever state you serve in — including rights modeled on the California Consumer Privacy Act and similar state laws:
- Access and portability — ask and we will provide a copy of your data in a portable format.
- Correction — your profile is editable in the app; anything else, ask.
- Deletion — self-serve in the app, as described above.
- No sale, no sharing, no profiling — we do not sell or share personal information as those terms are defined in the CCPA, and we make no automated decisions with legal effect about you, so there is nothing to opt out of.
- No retaliation — exercising any right never degrades your service.
To exercise a right, use You → Support in the app or email support@officerone.app. We verify requests against your signed-in account or email of record, honor authorized agents where the law provides for them, and respond within the time the applicable law sets — usually much faster.
14. Legal demands for your data
You know how this works from the other side, so here is our posture: we require valid legal process before disclosing user data, we read demands narrowly and produce the minimum they lawfully compel, we push back on overbroad requests, and we notify you before disclosure unless the law prohibits it — in which case we notify you when the prohibition lifts. We do not volunteer user data to anyone.
15. Children
Officer One is a professional tool for adults. It is not directed at children, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has created an account, contact us and we will delete it.
16. Changes to this policy
When we change this policy, we change the date at the top, keep the change honest to what the code actually does, and announce material changes in the app’s What changed log before they take effect. We will never use a policy update to quietly start selling data — that commitment is permanent.
17. Contact
bigBespoke LLC · support@officerone.app — or You → Support inside the app, where a person answers.