Privacy Policy — FileSnap Docs by Roam
Effective date: 2026-05-02 Last updated: 2026-05-02
This is the privacy policy for FileSnap Docs by Roam ("FileSnap Docs", "we", "us"), an iPhone application published by Roam HPU.
The short version: we do not collect any personal data. FileSnap Docs runs entirely on your device. There is no FileSnap Docs account, no FileSnap Docs server, no analytics SDK, and no advertising network embedded in the app. Document images, OCR transcripts, metadata, and any reminders you create stay on your device.
The rest of this document explains that in detail.
1. Information we do not collect
We do not collect, transmit, store, sell, or share any of the following:
- Personal information (name, email, address, phone, identifiers)
- Account information (because we do not have user accounts)
- Document images, OCR transcripts, issuer names, document types, tags, notes, expiry dates, or any other content you create or capture in the app
- Photos from your photo library beyond the moment you choose to import a document
- Camera frames beyond the moment you capture a document page
- Calendar events beyond the moment you opt in to creating one
- Device identifiers (IDFA, IDFV, advertising IDs)
- Crash reports, analytics events, telemetry, usage statistics
- Diagnostic logs
There is no remote endpoint that FileSnap Docs connects to for any of the above.
2. Information that stays on your device
FileSnap Docs creates and stores the following information on your iPhone, in the application's private storage, and does not transmit it elsewhere:
- Document images and PDFs — saved to the application's storage directory.
- Document metadata — title, issuer, type, date, expiry date, tags, notes, OCR transcript, page count, and file format — saved in the app's local SwiftData store.
- Settings — your filename pattern preference, save location, and other preferences — saved in standard
UserDefaults. - Calendar events (optional) — when you opt in to an expiry reminder, FileSnap Docs creates an event in your iOS Calendar via Apple's EventKit framework. The event lives in your calendar, not on our servers (we don't have any).
If you have iCloud Backup enabled for your iPhone in iOS Settings, this data may be included in your iCloud Backup, which is governed by Apple's iCloud terms and privacy policy. FileSnap Docs itself does not use iCloud, CloudKit, or any other sync service.
3. Permissions we ask for and why
| iOS permission | Why we ask | What we do with it |
|---|---|---|
| Camera | To capture a document when you tap "Scan Document". | We pass each captured page to Apple's on-device Vision framework for OCR, then save the image and extracted text on your device. We do not transmit the image. |
| Photos | To import an existing photo of a document. | We read only the photo you pick. We do not enumerate, scan, or upload your photo library. |
| Calendar (optional) | To create an expiry reminder when you ask for one. | We create a single calendar event at the date and time you choose. We do not read other calendar events, contacts, or invitee data. |
You can revoke any of these permissions in iOS Settings at any time. The app will continue to work with reduced auto-fill convenience.
4. Required reason API declarations
iOS requires apps to declare why they use certain "required-reason" APIs. FileSnap Docs declares:
UserDefaults— to persist your settings on your device. (Reason CA92.1)- File timestamps — to sort and display your documents by date. (Reason C617.1)
Both are local-only uses. The full declarations are in the app's PrivacyInfo.xcprivacy manifest, which is reviewable by Apple at submission.
5. Encrypted export
When you use FileSnap Docs's encrypted ZIP export to bundle documents for sharing:
- The encryption happens on your device.
- The password you choose is not transmitted, stored, or known to us. We never see it. If you forget it, we cannot recover it.
- The resulting
.zip.encbundle contains your encrypted documents and is shared via the iOS share sheet — where it goes (email, Files app, AirDrop, third-party app) is up to you.
6. Third parties
FileSnap Docs does not embed:
- Advertising SDKs
- Analytics SDKs (no Firebase, no Mixpanel, no Amplitude, no nothing)
- Crash reporters (no Sentry, no Crashlytics)
- A/B testing SDKs
- Social network SDKs
FileSnap Docs uses Apple's first-party frameworks (Vision, SwiftUI, SwiftData, PDFKit, EventKit, Foundation) which run on your device. These are governed by Apple's privacy policy, not ours.
7. Children
FileSnap Docs is rated 4+ and is suitable for general audiences. We do not knowingly collect data from children — because we do not collect data from anyone.
8. Your rights
Because no personal data leaves your device, there is no copy of your data we hold to provide, correct, or delete. The data lives on your iPhone and is yours.
To delete all FileSnap Docs data: delete the app from your iPhone. iOS removes the app's storage along with it. Calendar events you created via expiry reminders remain in your iOS Calendar and can be deleted there separately.
To export your data: use FileSnap Docs's built-in share / export action, or restore an iCloud or Finder/iTunes backup to a new device.
If you have a question about your data, email ben.lewis@roamhpu.co.
9. Changes to this policy
If we ever change what FileSnap Docs collects, we will update this page and the effective date at the top, and we will surface the change in-app at next launch. We do not anticipate changing this policy, because the design intent is to keep collecting nothing.
10. Contact
Roam HPU ben.lewis@roamhpu.co
This policy is for the iPhone app "FileSnap Docs by Roam" with bundle identifier com.roamhpu.FileSnapDocs.