RIVALPAIR BY AALISOFT
Privacy policy
1. Who we are
RivalPair is developed by aaliSoft. This policy covers the Mac app and Android companion, package com.aalisoft.rivalpair. For questions, contact [email protected].
2. Direct connections and pairing
Wi-Fi features connect your Mac and Android device on your local network. QR pairing exchanges connection credentials after approval. Connections use TLS with the approved phone certificate pinned on the Mac. USB file transfers use MTP. RivalPair does not relay your transferred content through an aaliSoft cloud server.
Pairing credentials, phone identity and connection settings are stored locally. Protect these credentials and do not share screenshots of active pairing codes.
3. What each feature accesses
| Feature | Information used | Purpose |
|---|---|---|
| File transfers and folder sync | Selected files, folder contents, filenames and integrity metadata | Copy, compare, synchronise and preserve versions between your devices. |
| Gallery and backup | Photos, videos, thumbnails and media metadata | Browse media on the Mac and copy originals to your chosen storage. |
| Notifications | App names, notification content and supported actions | Display notifications on the paired Mac and perform replies or dismissal you request. |
| Clipboard | Shared text and a current revision | Manual or optional automatic text sharing. Sensitive-marked clipboard formats are skipped; no clipboard history is maintained. |
| Screen, camera and microphone | Screen images, camera pictures and microphone audio | Live streaming during sessions you enable. Sessions have controls and device sharing indicators. |
| Remote input | Pointer movements, clicks, keystrokes and control commands | Operate the other device while a permitted remote session is active. |
| Messages and calls | Permitted SMS/MMS content, message status and call state | Display information and carry out supported actions you request. Your carrier and phone messaging app handle their own services. |
4. Permissions and your control
Android and macOS permissions control access. Camera, microphone, media, notifications, screen capture, Accessibility and message/call permissions are separate. You can use USB file transfers without installing the Android companion. For companion features, grant only the access you want.
Stop screen, camera, microphone and remote sessions using the app controls. Pause notification or clipboard sharing, change app filters, and revoke device permissions in operating-system settings. Background sync and automatically opening the Mac app on connection are optional.
5. Local storage and retention
The Mac stores credentials, settings, received files, previews, backups and sync history in its local RivalPair data folder. Transfer staging and previews can temporarily occupy disk space. Received files, saved backups and previous versions remain until you remove them. A crash can leave temporary files for later cleanup.
Android stores credentials and configuration in app-private storage and uses Android Keystore for its certificate key. Received files and managed sync folders use app-specific storage. Arbitrary folder sync uses folders you explicitly select. Android app backup is disabled in this build.
Before uninstalling Android, preserve any files in RivalPair-managed storage. Uninstalling may remove those files. Folders selected outside app-managed storage stay in their original location, subject to your storage provider’s behaviour.
Local data relies on operating-system access controls and is not additionally encrypted at rest by RivalPair. Protect your device and storage, and keep a separate backup of important files. Exported RivalPair migration backups use password-based authenticated encryption; retain the password separately.
6. Pairing, removal and deletion
Forget a pairing on the Mac to remove its local credentials. To revoke existing Mac access at the phone, use Android’s Manage pairing control, which rotates the connection token. Removing the Mac’s local pairing does not revoke credentials copied elsewhere.
You can remove local app data and saved files from your own storage. Optional deletion mirroring and sync version history have their own controls; review these before deleting a synced folder. There is no aaliSoft account database to close.
7. Other services and support
Mobile calls and SMS use your carrier. Messages or attachments opened in another messaging app, Bluetooth connections, compatible camera/audio drivers and your operating system have their own behaviour and privacy controls. RivalPair does not implement native RCS or direct cellular call-audio routing in this preview.
If you contact support, we receive the details you choose to send, such as your email, device model and a problem description. Do not include private messages, pairing tokens or unrelated personal files. This product website may produce ordinary server request logs; these are separate from content transferred between your devices.
Tester feedback
Reports submitted on the tester page are saved privately on our server, including the report, device details you supply and an optional reply email. A keyed hash of the connection address limits spam; the feedback database does not store the raw address. We use reports for testing and support, retain them for up to 12 months, and remove older reports automatically. Do not submit passwords, pairing codes or private files.
8. Updates and contact
We will update this page and its effective date when the app’s data handling changes. The current policy is available at apps.aalisoft.com/rivalpair/privacy/.
aaliSoft
[email protected]