Privacy, with care.
How Junta handles your finds, your account and the things you choose to share.
- Operator
- Ali Almahari
- Contact
- support@almahari.com
- Website
- https://junta.almahari.xyz
- Effective date
- 2026-10-31
1. Your local little home
Junta stores saved URLs, collection names and structure, notes, tags, favorites, ordering and reminder settings in a local SQLite database on your device. Basic local use does not require an account. Links can include query parameters and fragments; consider whether a URL contains private information before saving or sharing it.
Collection cover photos are selected through your device’s photo picker and copied into app storage. Photo covers remain on that device, scoped to the local account; they are not uploaded in the current cloud sync or collection-sharing payloads. Cached preview images are also stored locally.
2. Optional accounts and cloud sync
If you choose to create an account in a Firebase-enabled build, Firebase Authentication processes your email address, password and account identifier to sign you in. The app does not need an account for local use. Signing out changes the visible local account partition; it does not erase the account’s records.
Cloud sync and collection sharing require verified paid access. Personal collection and post records, including links, notes, tags, favorites and ordering, are sent to Firebase Cloud Functions and stored in Cloud Firestore under your account. Account identifiers, entitlement state, revisions, deletion markers and recovered conflicts support access control and synchronization. Guest records can move into the first account with verified paid access.
The current backend uses the europe-west1 region in Belgium. Firebase service processing and operational logs may involve Google infrastructure elsewhere; this is not a promise that every piece of data stays in that region. See Firebase’s privacy and security information for the provider’s practices. These providers may process information in countries other than where you live.
3. When you share a collection
Sharing makes the collection subtree and its saved links and notes available to authorized, paid, signed-in members. View-only members can read it; editors can add or edit posts and notes. Owners manage access and can revoke links. A shared link or QR code alone does not grant access. Optional share passwords are hashed by the backend, and failed joins are rate limited.
Shared collections are online-only in the current app. Revoking access cannot recall screenshots or content someone has already copied. Avoid sharing sensitive personal information.
4. External previews and original websites
To find titles and thumbnails, Junta requests public pages, platform preview endpoints and image hosts. Those services receive the requested URL or identifier and normal network information such as an IP address. This can happen without cloud sync or an account. Opening a saved link also connects to the original website, whose own privacy practices apply.
Available previews are cached on the device. Login walls, deleted posts and some sites prevent previews. Automatic website preview requests use HTTPS and skip local or private network targets; saving an HTTP link is still supported. A preview is never guaranteed.
5. Device permissions and security
The optional biometric app lock uses your device’s authentication system. Junta uses its authentication result; it does not receive your fingerprint or face template. This gate protects app presentation, while the OS sandbox and device lock protect local storage. The implementation does not provide end-to-end encrypted sync or an encrypted multi-user local database.
Android reminders use local notifications with permission. Delivery can depend on battery settings, operating system scheduling and device state. Reminders are not available on iOS. Collection cover selection uses photo-picker access. Junta requests notification and photo-picker access when the corresponding feature is used.
Android release builds use Firebase App Check with Google Play Integrity to help prevent abuse. These services process app information, device integrity and attestation material, and security tokens. Integrity checks can run even when you are not signed in. Firebase Authentication and Cloud Functions also process network information such as IP addresses and user-agent strings; backend request and service logs may contain technical diagnostics. Security-related identifiers and diagnostics are used for app operation and fraud prevention, not advertising. Provider retention and deletion practices apply; see Firebase privacy information and Play Integrity data safety information.
Configured Android release builds also use Firebase Crashlytics for automatic crash and app-not-responding diagnostics. Reports can include stack traces, error categories, app version, operating system and device information, timestamps, and Crashlytics installation identifiers. We do not attach your account ID, email, saved links or notes as custom crash-report fields. The Flutter error handler sends error types and stack traces instead of raw error values or widget diagnostics; native SDK crash messages may still contain error details. Crash reporting is not enabled in debug builds or builds using local Firebase emulators. We have not added the Google Analytics SDK or advertising tracking. Firebase states that Crashlytics keeps crash stack traces and associated installation identifiers for 90 days before beginning removal from live and backup systems; see Firebase privacy information for its current retention practices.
6. Purchases and retention
The intended annual plan is USD 3.99. Public store release and production purchase setup are not yet complete; purchasing is unavailable. Purchase verification involves the platform store, purchase identifiers or tokens and account-linked entitlements. Raw receipts are not written to logs. If purchases become available, the store will show the applicable price and billing terms before you buy.
After subscription expiry, cloud data is retained until account deletion. Inactive paid access suspends cloud and shared authorization; it does not automatically erase your finds. Deletion markers and recovered edits support synchronization while the account exists.
After account deletion, a minimal billing ledger retains one-way account hashes and purchase identifiers to prevent receipt reuse. Direct account identifiers and purchase tokens are removed from those ledger entries. This retained fraud-prevention record does not include your saved links or notes. Provider-managed backups and operational logs may outlast deletion of active records. This notice does not promise immediate removal from provider backups or a fixed retention period for those systems. Contact us for questions about a specific deletion request.
7. Your choices and deletion
You can use local mode, choose what to save, edit or remove saved posts, delete collections and their contents, and manage sharing access. Cloud-enabled deletions use synchronization markers and are not a promise of immediate erasure from all storage or backups. Removing the app can remove its local data, but does not delete Firebase account or cloud records and may be affected by device backups.
To delete your account, sign in, open Settings and the account screen, choose Delete account and confirm your password. The flow deletes your Firebase account, personal cloud records, owned shares and associated access records, and this account’s local data on the device completing deletion. Other local accounts remain saved. Server cleanup retries if interrupted, and local cleanup can resume at the next launch.
Account deletion requires connectivity and password verification, not an active subscription. It cannot instantly erase copies on other offline devices, backups or content someone else has captured. A minimal anti-reuse billing ledger remains as described above. See the account deletion page for instructions or email support@almahari.com for assistance. This website does not itself execute deletion.
8. This website and changes
This website offers product information, this privacy notice and account-deletion instructions. It has no account, purchase or signup form and includes no analytics or advertising scripts. Its styles and illustrations load locally. The web server or hosting provider may process request information and access/error logs; the site is hosted on DigitalOcean infrastructure managed through Ploi. Its information pages do not set application session cookies. Hosting providers may retain operational records under their own policies.
We update this page when our data handling changes and revise the effective date above. Please review it before using newly introduced account, cloud or purchase features.
9. Parents, guardians and privacy requests
Junta is intended for people aged 13 and older. It is not directed to children under 13.
A parent or guardian who believes a child has provided personal information can contact support@almahari.com to ask about access, correction or deletion. We may need to verify the requester's authority and account ownership before acting. Never send a child's password, payment details or biometric information. This notice does not claim that parental-consent or age-verification controls are implemented in the app.
10. Contact
Junta is operated by Ali Almahari. For privacy questions, correction requests or help with deletion, email support@almahari.com.