Skip to main content
Parallax app icon

Parallax / Legal

Parallax

Privacy Policy

Last updated:

This policy explains how Parallax for Android (“Parallax”, “the app”) handles information. Parallax is developed by Sam Russell and published by Creative Spark Pty Ltd under the Sam Russell Tech name in Australia (“I”, “me”, “my”). It applies to the app and these Parallax web pages, not to the Matrix homeserver you sign in to or other services you choose to open.

1. Scope and website

This policy covers Parallax’s sign-in, room list, Spaces, timeline, media, notifications, app lock, search and settings. It does not replace the privacy policy of the Matrix homeserver you sign in to, your UnifiedPush distributor, your email provider, Google Play, or any other service you choose to open. Your homeserver operator controls the server-side copy of your messages and its own retention rules.

This website uses no advertising, analytics or tracking cookies. If you switch between light and dark mode, your browser saves only that site-theme preference locally on your device. As with most websites, hosting and network providers process standard connection details such as IP address, request time and requested URL to deliver the page.

2. Information Parallax processes on your phone

Parallax keeps its working data in the Android app sandbox. “On-device” below describes what the Parallax code does; it does not override a destination you choose for an export, or your homeserver’s own copy of your messages.

InformationWhy Parallax uses itHow Parallax stores it
Matrix session, timeline and encryption stateSign-in, message history, room state, device keys and end-to-end encryption.A SQLite database inside Android’s app sandbox. Device storage encryption and sandbox access controls apply; the database does not have an additional SQLCipher layer.
Drafts and outboxUnsent messages survive restarts, and failed sends stay visible for retry or discard.OS-backed secure storage with no plaintext storage fallback.
Appearance preferencesTheme, text size, compact layout, chat row styles, per-chat pictures and app logos.Local preferences. Room background images are private app files, not secure-storage entries.
Thumbnails and avatarsDisplay media in chats and the gallery, including the optional thumbnail sync.The app’s private cache folder, up to 1 GB with the oldest files removed first. Each file holds what the homeserver served for that media ID, so media from encrypted rooms stays encrypted at rest and is decrypted when shown. File names are hashes, not media IDs. The cache is per session and deleted on sign-out.
Link preview cachePage titles and images for links shared in rooms.A per-account file holding the newest 300 successful previews, kept beside the thumbnail cache and deleted on sign-out. Previews are fetched by your homeserver, not your phone.
Message search indexOn-device search of encrypted history.An FTS5 index in app storage, deleted on sign-out. Unencrypted rooms are searched on the homeserver instead.
Notification dataRecent notification lines, notification settings and quick replies waiting to be sent.The private app support directory, excluded from backup, scoped to one account and device, pruned after three days and deleted on sign-out.
App lockGate the app with a PIN or biometrics, including incoming verification prompts.The lock preference is stored locally. Biometric matching is performed by Android; Parallax does not receive your biometric data.
Recovery and room key exportsLet you restore encrypted history on a new device.Created only when you choose to export. You pick the destination, and the file is outside Parallax’s storage afterwards. Treat it as a password.

3. When Parallax connects to external services

3.1 Your Matrix homeserver

Parallax is a Matrix client. Messages, media, reactions, receipts and room changes go to the homeserver you sign in to, whether that is matrix.org or a server you or your organisation runs. That operator’s privacy policy and terms govern the server-side copy, and its location and retention rules are its own.

In encrypted rooms, Parallax encrypts message content on your phone before upload, using vodozemac and Olm. Encryption does not conceal everything: a Matrix homeserver can still observe connections, room memberships, encrypted traffic, event sizes and timing. This is true of every Matrix client, not a Parallax-specific gap.

Homeserver URLs must use HTTPS, without embedded credentials. Parallax does not fall back to plaintext HTTP, and encrypted sends keep recipient-trust checks and a final send guard: losing encryption or session ownership is an error, not permission to send in the clear.

3.2 Link previews

Link previews are fetched by your homeserver, not your phone. They are on by default in ordinary rooms, where the server can already read the link. They stay off in encrypted rooms unless you opt in under Settings → Media → Link previews, and rooms whose encryption state is unknown are treated as encrypted. The linked website sees the homeserver’s request, not your device’s address.

3.3 Notifications and push

Parallax offers three delivery paths. You choose under Settings → Notifications.

Notifications show the sender, message text and media previews. That content is fetched from your homeserver and decrypted on this device after a push arrives; if fetching or decryption fails or takes too long, a generic “New message” alert is shown instead. You can turn message content and media previews off separately. Notifications use Android’s private lock-screen visibility, so a secure lock screen hides their content when you choose to hide sensitive notifications in system settings.

3.4 Location sharing and map tiles

Parallax requests location permission only when you choose to share a static or live location. The location is sent to the room through your homeserver like any other message. Displaying a map requests tiles from OpenStreetMap tile servers, which receive the usual technical connection information such as your IP address and the requested tile coordinates. Map data is © OpenStreetMap contributors.

3.5 Support email

Suggestions and requests opens your chosen email app with a draft to samrusselltech.dev@gmail.com. The draft includes the app version, Android version and device model to make bug reports easier to understand. You can edit or remove those details before sending. Parallax does not transmit the message itself; your email provider sends it only when you choose to send it.

4. Permissions and special access

Android’s permission labels can be broad. Here is how Parallax uses each one:

Permission or accessPurpose and boundary
Internet (INTERNET)Homeserver sync, media upload and download, push delivery and map tiles. All homeserver traffic uses HTTPS.
CameraPhoto and video capture you start from the composer. Parallax does not access the camera in the background.
MicrophoneVoice recording you start. Recording and preview are local operations; sending is a separate action.
Precise and coarse locationRequested only when you share a static or live location. Parallax does not use location for anything else.
NotificationsRich notifications with sender, text and media previews, plus quick reply. On Android 13 and later this is a runtime permission you grant.
Biometrics and PINApp lock. Android performs biometric matching; Parallax stores the lock preference locally.
Foreground service, boot and battery-optimisation exemptionKeep the built-in connection alive: a specialUse foreground service, a boot receiver that restarts it after a reboot or update, and a one-time battery-optimisation exemption request. Used only while the built-in connection is enabled; it stops on sign-out or when notifications are turned off.

Parallax does not request Contacts, SMS or call-log access. Media playback uses a decrypted temporary file that the player needs; cleanup joins the playback work and removes the file when it finishes, though a failed disposal or process death can prevent cleanup. Attachments you explicitly save belong to the destination you choose and sit outside that cleanup policy.

5. Backups, exports and device transfer

Android application backup and device-transfer backup are disabled for Parallax. Your Matrix database, caches and notification data are not copied by Android’s backup facility. This does not protect a compromised or rooted device, or a running, unlocked app.

Exports you control

Room key exports, recovery keys and saved attachments are created only when you ask for them, and you choose the destination. Those files leave Parallax’s private storage and are not deleted when you uninstall the app. A room key export can unlock your encrypted history, so store it like a password and delete old copies you no longer need.

Parallax operates no cloud backup service of its own. The server-side copy of your messages lives with your homeserver operator, under its backup and retention rules.

6. Retention and deletion

To remove Parallax’s local information, use Android’s App info → Storage → Clear data and uninstall Parallax. Also delete any exported key files or saved attachments you no longer want. Revoking a permission stops future access but does not delete data held by another provider.

7. Other services and providers

Parallax connects you to other software and services. Your Matrix homeserver operator, UnifiedPush distributor and gateway, Google (Play purchases, optional Firebase, and ntfy.sh wake-ups), OpenStreetMap tile servers, your email provider and your network provider can process information under their own privacy policies. Their presence in Parallax does not make me the controller of their independent processing.

I do not sell personal information, share it with advertisers, or use third-party advertising or analytics SDKs in Parallax. External services used by a feature receive the information described above, along with the technical information inherent in a network request.

Support correspondence

If you email me, I receive your email address, your name if you provide it, your message and any attachments or app and device details you choose to send. I use that information to respond, provide support, improve Parallax, maintain security and keep appropriate records. Please remove sensitive message content, recovery keys, passwords or payment information before contacting me.

8. Security

Parallax relies on Android’s app sandbox, app-private storage and runtime permissions. Homeserver URLs must use HTTPS without embedded credentials, with no plaintext fallback. Encrypted sends keep recipient-trust checks and a final HTTP send guard, and encrypted attachments are encrypted before upload. Android blocks screenshots and recent-app previews while recovery credentials are displayed.

Parallax has not undergone an independent security audit, and its encryption behaviour has not been verified live against every other Matrix client. Automated tests cover transport, storage and notification paths; those results are a starting point, not a certification. No software, device or network transmission can be guaranteed completely secure. Keep your device updated, use a screen lock, guard your recovery key, and do not place secrets in chat on a device you do not trust.

9. Children

Parallax requires a Matrix account, and account creation is subject to the homeserver operator’s terms and age rules. The app is not directed at children, and I do not operate a server that collects children’s data. Parents and guardians should manage a child’s device permissions, location sharing, notification content and Google Play purchase controls, and check the age rules of the homeserver the child uses. Contact me if you believe information has been provided to me directly through support.

10. Your choices and privacy rights

You can control most information directly:

Depending on where you live, you may have legal rights to access, correct, delete, restrict or object to processing of personal information, or to request portability. Most Parallax information is only on your device, so the controls above are usually the most direct way to exercise those rights. For information held by your homeserver operator or another provider, contact that provider as well. You can contact me about information you send for support or about this policy, and you may have the right to complain to your local privacy or data-protection authority.

11. International processing

I am based in Australia. Your homeserver operator, UnifiedPush distributor, Google, email, hosting, network and map-tile providers can process information in other countries. Their locations, safeguards and legal mechanisms are described in their own policies. Parallax does not operate its own international user-data server.

12. Changes to this policy

I will update this policy if Parallax’s features, permissions or service providers change. The “Last updated” date will change, and material updates can be highlighted on the Parallax page or in release notes. Review the current policy when installing an update.

13. Contact

Questions, support requests and privacy requests can be sent to:

Sam Russell · Sam Russell Tech · Creative Spark Pty Ltd · Australia
Email: samrusselltech.dev@gmail.com

Please do not include passwords, recovery keys, payment details or sensitive message content in an email.