Effective date: November 8, 2026
This policy covers Inscape for Android, published by Velocity Craft (“we”).
Inscape is a journal. Before describing what we protect, here is what we do not claim:
Inscape requires no account and Velocity Craft runs no server that stores journal content. Entry text, titles, tags, moods, photos, audio notes, and which entries you revisit stay on your device unless you choose to move them (see "Where encryption applies" below), and none of them is passed to the advertising, analytics, or crash-reporting services described next.
Retrospect features ("On This Day") are computed entirely on your device. No entry is uploaded to select or summarize anything.
There is no sign-in for users. The app contains a hidden developer panel with Google sign-in, used for internal testing. Signing in there sends nothing to us or to Google's analytics. Only when one of our own designated test accounts signs in is a one-way hash of its email address attached to analytics and crash reports from that device.
This is a separate matter from your journal, and we keep the two descriptions apart on purpose. None of the following contains your entries. Inscape shows advertising through Google AdMob and uses Google Firebase for usage analytics (Firebase Analytics), crash reports (Firebase Crashlytics), notifications (Firebase Cloud Messaging) and remote feature settings (Firebase Remote Config). Together they collect:
| Category | Collected by | What and why |
|---|---|---|
| IP address | Google AdMob, Google Firebase | Unavoidably included in every network request these services make |
| User product interactions | Google AdMob, Firebase Analytics | Ad impressions and clicks; which screen of the app was opened (screen names such as "settings" or "editor", never entry content); a one-time "first entry created" event; list-style changes; and counts from each sync round (how many items were sent and received) |
| Diagnostic information | Firebase Crashlytics | Crash reports and non-fatal error reports: device model, OS version, app version, the error's stack trace, and app state such as your tier (Free or Lifetime) |
| Device and Account identifiers | Google AdMob, Google Firebase | Advertising ID and app set ID; the Firebase installation ID; and the push-notification token |
| Purchase history | Firebase Analytics | When you buy Inscape Lifetime: the product ID, currency and price. Google Play handles the payment; we never see your payment details |
Analytics events also carry the app version, build type, your tier (Free or Lifetime) and a device performance class (low/mid/high), so that reports can be grouped.
Google Analytics also records some information automatically: device model, Android version, language setting, and session and engagement data such as first open and time in app, together with a random app-instance identifier. Firebase keeps crash reports for 90 days; analytics event data is kept for no more than 14 months.
The following are not collected and never leave your device through us: messages or entry text, photos and videos, health and fitness data (including mood), personal info, files and documents, precise location, audio, contacts, and calendar. Google may estimate an approximate, city-level region from the IP address for ad delivery and analytics reports; in Google Play's Data safety section this is declared as "Approximate location". Inscape does not request location permission and never reads your device's location. If a photo you attach already contains location data, it stays with the entry on this device (and in your backups or encrypted sync); it is never sent to us or to the advertising and analytics services.
If you buy Inscape Lifetime, or while a Plus Pass you unlocked by watching a rewarded ad is active, ads are not shown. The advertising SDK may still start on your device so that the consent setting and ad-free state can be checked. Analytics and crash reporting work the same on every tier.
Any statement about encryption is only true under specific conditions. Here are all the paths your journal can take off this device:
| Path | Encrypted? |
|---|---|
| Journal database on this device | No. Protected by Android app sandboxing, and by the app lock if you enable it. |
| Dropbox backup file | Only if you turn on backup encryption. With it off, the backup is readable by anyone with access to that Dropbox account. Backup encryption is available on every tier, including free. |
| Dropbox sync | Always. Entries, attachments and the sync index are encrypted on this device with AES-256-GCM before upload, using a key derived from a sync passphrase you choose (at least 12 characters). See "Dropbox sync" below for what Dropbox can still see. |
| Full backup file you save (ZIP) | Only if you turn on backup encryption. Otherwise it is a plain file. |
| Share to another app | No. The entry text or file goes, as is, to the app you choose, under that app's policy. |
| Export to Markdown, text, or PDF | No. Exports are plain files, by design — they exist to be opened elsewhere. |
| Android OS device backup (Auto Backup / device transfer) | Excluded. The journal database, photos, audio, video, documents, local backup files, photo location data, hidden retrospect dates and recent searches are all removed from OS-level backup, because that path lies outside our encryption contract. Display settings such as theme do move to a new device. |
If you lose a backup or sync passphrase, we cannot recover the data it protects. Keep it somewhere you will still have it after losing the phone.
Both are optional and available to every user. If you connect Dropbox, authorization happens with Dropbox, and the connection tokens are kept on this device in Android Keystore-protected storage. Inscape talks directly to Dropbox; Velocity Craft runs no server that receives your journal or its keys.
Your sync passphrase never leaves this device. It is stored in Android Keystore-protected storage so sync can run in the background, and it is excluded from OS backup. On a new device you enter it again.
Dropbox stores the backup files and encrypted sync objects under your account and can observe service metadata that is not covered by content encryption: object paths (which contain hashes), sizes, revisions, request times, your network address, and, for each backup, a small unencrypted summary file with the app version, backup time, and the number of entries and photos. Dropbox's handling is governed by Dropbox's privacy policy.
Uninstalling Inscape or disconnecting Dropbox does not delete files already in Dropbox. Sync does not delete earlier encrypted objects. To remove them, delete Inscape's folder in your Dropbox and, if you wish, revoke the app in your Dropbox account settings.
Where required, Inscape presents a Google-certified consent form before any advertising. You can change your choice at any time from Settings. Depending on your choice, ads are shown in non-personalized form or not loaded at all. This form governs advertising only. Firebase Analytics and Crashlytics are not controlled by it and run on every device; Analytics can read the advertising ID, which you can reset or delete in Android settings.
You have the right to access, correct, and delete your data. Journal content is held only on your device and in storage you control, so you exercise those rights directly: delete entries in the app, uninstall to remove everything on this device, and delete Inscape's folder in Dropbox if you used backup or sync. Analytics, crash and advertising data are held by Google and are not linked to your name or email (except our own designated test accounts, described above); for that data, use Google's tools or contact us and we will help where we can.
Inscape is not directed to children under 13, and we do not knowingly collect data from them.
Material changes to this policy will be announced in the app or on this page before taking effect.
velocitycraft.app+inscape@gmail.com
If you email us, including through Send feedback in the app (which pre-fills your app version, device model, Android version, screen size, memory and language, all of which you can edit), we receive your email address and message and use them only to reply.