Privacy Policy

Solum is built around a simple principle: your data belongs to you. This policy explains what we collect (very little), what we don't collect (almost everything), and how your data is handled.

Data we do not collect

• No personal information — no name, email, or identity of any kind is required to use Solum.
• No dose data — all vial configurations, administrations, schedules, and observations are stored on your device. We never receive them. The one way any of it leaves your phone is the optional AI assistant, which you must switch on yourself and which sends it to a provider you choose, not to us. See AI assistant below.
• No usage analytics — we do not track how you use the app, which screens you visit, or how often you open it.
• No crash reporting that transmits personal data — if we implement crash reporting in future, it will be aggregated and stripped of any identifying information before transmission.

Data stored on your device

Solum stores all data in a local SQLite database on your device. This includes:

• Vial templates and instances
• Administration logs
• Schedules and reminders
• Observations
• App settings

This data never leaves your device unless you explicitly send it somewhere: exporting it, moving it with Cloud Transfer, or asking the optional AI assistant a question about it. Each of those is an action you take deliberately.

Subscriptions

Subscription purchases are processed by Apple via the App Store or by Google via Google Play. Solum does not handle payment information directly — at no point do we see your card, address, or Apple/Google account details. Receipts are validated through RevenueCat, which processes anonymized subscription events on our behalf. RevenueCat's own privacy policy applies to the data they handle.

Referral attribution

During onboarding, new users may optionally enter a referral code. If a code is entered, Solum transmits a small amount of data to our server to credit the referrer. This section explains exactly what is sent, why, and what happens to it afterward.

What is sent:

• Referral code — the code you typed in, sent in plain text so the server can look up the referrer.
• Device identifier hash — a one-way SHA-256 hash of your device's vendor identifier (IDFV on iOS, Android ID on Android). This hash cannot be reversed to recover the original identifier. It is used solely to prevent the same device from being counted more than once.
• Pseudonymous user ID — a random UUID generated on your device at first launch. It contains no personal information and cannot be linked to your name, email, Apple ID, or Google account. It is used to verify that you later became a subscriber (via RevenueCat), so the referrer can be credited.
• Platform — whether you are on iOS or Android, so the server knows which deduplication method was used.

What is not sent:

• No name, email, phone number, or any other personal identifier.
• No dose data, vial configurations, schedules, observations, or any health-related information.
• No IP-based geolocation is stored. While our server necessarily receives your IP address during the request, it is not logged or retained.
• No device fingerprinting beyond the single hashed identifier described above.

How the data is used:

• The device identifier hash is compared against existing records to prevent duplicate attributions. Once the referral is processed and any applicable payout has been made, the hash is permanently deleted from our database.
• The pseudonymous user ID is used to query RevenueCat's API to confirm that the referred user holds an active subscription. This check happens server-side during a periodic batch process — no additional data is sent from your device.
• The referral code links the attribution to the referrer's account in our internal dashboard. This is a business-to-business relationship; end users do not receive monetary rewards.

Data retention:

• The device identifier hash is deleted once the referral conversion is marked as paid. It exists only for the duration of the refund window (typically 30 days) plus processing time.
• The pseudonymous user ID may be retained on the conversion record for recurring commission tracking. It remains pseudonymous — we have no way to associate it with your real-world identity.
• If you never enter a referral code, none of the above data is ever transmitted.

Your control:

• Entering a referral code is entirely optional. You can skip the screen with no effect on app functionality.
• If you enter a code, the privacy implications are disclosed on-screen before you proceed.
• If you have questions about a specific referral attribution, contact privacy@getsolum.app with your pseudonymous user ID (visible in Settings) and we will delete the associated conversion record on request.

AI assistant (optional)

Solum includes an optional assistant, in the Ask tab, that can answer questions about your own logbook. It is important to be precise about what this is, because it is the only part of the app that can send your log off the device.

We do not operate it. Solum provides no AI service, hosts no model, and runs no server in this path. The feature is bring-your-own-key: you supply an API key for a provider you already have an account with, such as Anthropic, OpenAI, OpenRouter, or any OpenAI-compatible endpoint you choose, including one on your own network. Your phone talks to that provider directly.

It is off until you turn it on. A fresh install has no provider, no key, and sends nothing. To enable it you must open the Ask tab, read a disclaimer to the end, choose a provider, and paste a key that passes a live connection test. Skipping this costs you nothing else in the app; every other feature works exactly as before.

What is sent, and to whom:

• Your message, and the earlier messages in that conversation.
• A fixed description of how the app's data model works. It contains nothing about you.
• The results of any lookups the model requests while answering, which may include your medications, schedules, protocols, upcoming and logged doses, compliance figures, and observations. The app shows you each lookup as a chip you can tap to see exactly what was sent.

All of this goes from your device to your chosen provider over HTTPS, authenticated with your key. It does not pass through our servers. We operate no proxy and keep no copy, and we have no technical means of reading this traffic.

Your provider becomes the data controller for what you send them. Their privacy policy and terms govern it, including how long they retain API traffic and whether they use it to train models. We have no control over, and accept no responsibility for, their handling of your data. Read their policy before you connect, and choose a provider whose terms you are comfortable with.

Your key. It is stored in the iOS Keychain or the Android Keystore, never in the app's database. It is excluded from data exports, from device backups made by the app, and from both Local and Cloud Transfer. We never receive it. If you move to a new phone, you re-enter it there.

What you control:

• Whether to connect at all. The feature does nothing until you do.
• Which provider and model. Including a self-hosted or local one, if you would rather nothing left your own network.
• What it may look at. Settings → Assistant has three independent switches: reading your logbook, using the calculator, and drafting schedules, protocols and vials. A capability you switch off is not offered to the model at all, so the data behind it is never gathered or sent.
• Whether it can change anything. It cannot. The assistant can only propose; drafts appear as cards that do nothing until you tap Apply.
• Disconnecting. Settings → Assistant → Disconnect deletes your key and every stored conversation from the device.

Retention. Conversations are stored only in the local database on your phone, alongside the rest of your data. You can delete any conversation individually, or all of them at once by disconnecting. We hold none of them, so there is nothing on our side to request deletion of. Whatever your provider retains is governed by their policy, and you would need to approach them about it.

Not advice, and not ours. Answers come from a third-party model, not from Solum. We do not write, review, endorse, or take responsibility for what it says. It can be wrong. Nothing it produces is medical advice.

Cloud Transfer

If you use the optional Cloud Transfer feature to move your data from one device to another, your data is end-to-end encrypted on your device before leaving it. Our server stores only an opaque encrypted blob it cannot read, and deletes it immediately after the new device downloads it (or after 24 hours if unclaimed). See our Cloud Transfer Privacy page for details.

Device backup

By default, your device may include the Solum database in a cloud or local backup (iCloud on iOS, Google backup on Android). This is covered by Apple's or Google's respective privacy practices. You can disable this in your device settings, or within Solum's Settings.

Your rights

Because we don't collect your data, there is nothing for us to delete, correct, or export on your behalf. All your data already lives locally on your device and is under your control. If you connected an AI assistant, anything you sent it is held by that provider under their policy, and a request about it goes to them rather than to us.

To delete your Solum data entirely, uninstall the app from your device.

Children

Solum is not directed at children under 13 and we do not knowingly collect information from children.

Changes to this policy

If we make material changes to this policy, we will update the date at the top of this page and, where appropriate, notify you within the app.

Contact

Questions or concerns? Email us at privacy@getsolum.app.