Privacy Policy for Nafis

Nafis tracks prices for gold, silver, currencies and crypto, and adds a personal holdings vault, price alerts, a zakat calculator and news. It has no accounts and no server of ours. Your financial data never leaves your device.

Last updated: 25 July 2026 · Covers app version 1.18.0 and later · Package com.mohamedgado.nafis

1. Who we are and what this covers

Nafis (com.mohamedgado.nafis) is built and operated by one person, Mohamed Gado. This policy covers the Nafis Android app, any future iOS release, and this page itself. The page sets no cookies and loads nothing from another host.

You can open this page from inside the app at any time: Settings, then Privacy Policy.

The core design principle is keyless and serverless. Every data source is a free public API, and there is no Nafis backend that your requests pass through. As a direct consequence, we cannot see your portfolio or balances, because they are never transmitted anywhere.

2. What stays on your device

The following is stored locally only (a SQLite database, an app-private preferences store, and the app's own file directory). None of it is uploaded or synced:

• Vault: pieces, metals, karats, weights, purchase prices, making charges and recorded sales.
• Goals and savings plans: targets, contributions and cadence.
• Alerts: the thresholds you set, vault alerts, and digest schedules.
• Price history: an on-device daily log used to draw charts and compute changes.
• Settings: language, theme, currency, karat, country, home layout and watchlist.
• Item photos: photos you attach to vault pieces are copied into the app's folder on your device.

There is no sign-in, no cloud sync and no automatic backup on our side. You are the only holder of this data.

3. What leaves your device

To show live prices and headlines, the app talks directly to public services. Those requests carry no identity and no vault contents, only what is needed to fetch the information (an asset symbol, a news topic). As with any internet request, the receiving server sees your device IP address and client type. No app can avoid that when fetching data from a network.

4. Location data

Location is optional and requested only while you use the app. When granted, Nafis reads your coordinates once to work out your country, then sends them to BigDataCloud to resolve a country and city name, so it can pick the right currency, karat set and local retail prices.

• Coordinates are not stored on our servers, simply because we run none.
• They are not linked to any identity and are never used for advertising.
• What is saved on your device is the resulting country, city and currency.
• There is no background location tracking and no location history.
• If you decline, you can pick your country manually and use the app fully.

5. Camera and photos

You can attach a photo to a vault piece, from the camera or your gallery. The image is copied into the app's own folder and its path is saved in the local database. Photos are never uploaded, analysed or shared, and the camera or photo permission is requested only at the moment you choose to add one.

6. Notifications and alerts

Every alert (price targets, move alerts, the daily digest, the weekly recap, vault alerts) is evaluated and delivered on your device as a local notification. There are no remote push notifications and no device push token is sent to anyone. Prices are compared locally after each successful refresh and in a periodic background task.

7. Analytics and crash reporting

To improve the app, see which screens are actually used and find what breaks, Nafis sends anonymous usage events to PostHog (EU servers) and to EAS Observe / Expo Insights from Expo.

What is sent

• A random id generated on the device, not tied to your name, email or any account.
• A fixed, predefined set of event names: app opened, screen viewed, language or theme or currency changed, alert created, tool opened, onboarding completed, and similar.
• Low-cardinality properties alongside an event: an asset code, a tool name, a setting key and its value (for example language = ar).
• Technical data: app version, OS, device model, startup and navigation timings.
• Error and crash reports: error type, stack trace and short technical context.

What is never sent

• Any amount, weight, vault content, portfolio value, or profit and loss figure.
• The text you type into search, item names, or item photos.
• Your coordinates, name, email, contacts, or list of installed apps.
• No session replay or screen recording. It is explicitly disabled in the app.

8. Backups and sharing

Nafis can export a full backup (JSON), export the vault as CSV, and share price or calculator images. Each one starts with your action. The file is written to a temporary folder on your device and handed to the system share sheet. It goes only where you send it (Drive, WhatsApp, Files), and we never receive a copy. From that point the receiving app's own privacy policy applies.

9. App updates

Nafis uses Expo updates (EAS Update) to ship fixes without waiting for a store review. The app asks Expo's servers whether an update exists for its version, sending the app version, update channel, OS and device type. No personal or financial data is involved.

10. Android permissions

11. How we secure data

Data that is never collected cannot leak. That is the first security measure in Nafis: no server, no account, no password, and no central user database to breach. Beyond that:

• All network traffic uses HTTPS with certificate validation. The production build does not permit cleartext connections.
• Your vault and settings live in app-private storage, which Android isolates from other apps. Nothing is written to a shared or world-readable folder.
• The app ships no API keys or secrets, because every source is a free public API. There is nothing inside the package worth extracting.
• A backup you export is deliberately unencrypted so it stays readable and restorable. Store it somewhere you trust, since it contains your vault details.
• Device permissions are kept to the minimum, and permissions that libraries added without a real use were removed (section 10).

Nobody, including the developer, can inspect your vault remotely. If you find a security issue, please email us (section 17) before disclosing it.

12. Retention and deletion

• On-device data: kept as long as the app is installed. Uninstalling it, or clearing its data in system settings, removes it permanently. You can also delete any item, alert or goal from inside the app at any time.
• Usage events: held by PostHog and Expo under their own retention policies, attached to an anonymous id that does not identify you. Email us to have them deleted.
• Your backups: under your control, since you chose where to store them.

13. Your rights

If you are in the EU, the UK or California, you have rights of access, correction, deletion and objection to processing. In practice:

• Most of your data lives on your device, under your direct and complete control.
• We do not sell your data or share it for advertising or marketing, and we do not build an ad profile from it.
• The legal basis for usage analytics is legitimate interest in operating, improving and debugging the app, and the data is anonymous.
• To exercise any right or request deletion, email us (section 17).

14. Children's privacy

Nafis is a finance app intended for adults. It is not directed at children under 13 and we do not knowingly collect personal information from them. If you believe a child sent us data, contact us and we will act on it.

15. External links and third parties

When you open an article in your browser or visit a publisher site, that site's own policy applies. Policies of the services named above:

• PostHog
• Expo (EAS Update and Observe)
• BigDataCloud
• Gold-API
• ExchangeRate-API
• CoinGecko
• Open-Meteo
• Microsoft Bing
• Jina AI Reader
• Google Play

16. Changes to this policy

We update this policy when a feature or a data source changes. The date at the top of the page reflects the latest version, and the full change history is public in this page's GitHub repository. Material changes will also be called out in the app's release notes.

17. Contact