Crossbar
Privacy Policy
Crossbar is a voice and video calling app that connects to a server operated by you, your household, or your organisation. This policy explains how personal information is processed by the iOS app, your chosen server, and the Crossbar Push Relay.
Privacy at a Glance
- No advertising, behavioural tracking, or analytics SDKs.
- No access to your address book, photo library, or location services.
- The app does not record call audio or video.
- Your server operator manages account and call records.
- The push relay processes notification details, not call audio or video.
- Self-created accounts can be deleted in Settings.
Scope and Responsibility
Crossbar is developed by Abdullah Azzaam Faisal Chaudhry. In this policy, “we”, “us”, and “our” refer to the developer, who provides the iOS app and operates the central Crossbar Push Relay at push.callcrossbar.com.
Your server operator is the person or organisation that runs the server you use. It controls your account, contacts, call records, logs, and backup arrangements. If we do not operate that server, consult its operator’s privacy notice for information about that processing.
Where we also operate your server, this policy covers our operation of that server.
Information We Process
You provide information when you set up an account, add contacts, or make calls. iOS supplies device push tokens, and connections to the service generate network and request metadata.
On Your iPhone
The app stores your server address, connection settings, device identifier, and active-call identifier. Device signing credentials and session tokens are stored in the iOS Keychain. Release builds do not write local diagnostic log files. Development builds may log call details, signalling messages, and network addresses; diagnostic messages are filtered to redact credential values.
Your account password is not saved by the app. Development diagnostic files should still be treated as sensitive.
On Your Server
The server stores your display name, handle, optional profile image, and password hash, along with device identifiers, public keys, names, platforms, and status. It also keeps contacts and contact requests, group memberships, online and last-seen information, call records (participants, type, timestamps, and outcomes), push tokens, and operational and security records.
Your server operator controls this information and any server-side backups.
At the Push Relay
The relay receives server installation and device identifiers, installation labels, incoming-call and notification push tokens, call and request identifiers, caller details, a video-call indicator, and missed-call notification text. It stores delivery results, request fingerprints for duplicate suppression, and rate-limit counters, including hashed IP addresses used when a server registers.
The relay does not receive your password, contact list, or call audio or video.
Calls and Camera Access
The microphone is used for calls. The camera is used for video calls and, if you choose, to scan a server setup code. WebRTC sends call audio and video directly between participants or through a TURN relay, with media encrypted in transit.
The app, server software, and push relay do not record call audio or video. Other participants may make their own recordings.
This website uses no cookies or analytics and loads no third-party scripts or fonts.
How Information Is Used
- To authenticate you, manage accounts and devices, maintain contacts, and show availability.
- To establish calls, display call history, and deliver incoming-call and missed-call notifications.
- To diagnose connection problems, apply rate limits, and protect against misuse.
- To comply with applicable legal obligations and protect legal rights.
We do not sell personal information, use it for behavioural profiling, or share it for cross-context behavioural advertising. Where a legal basis is required, we rely on providing the service you request, legitimate interests in operating and securing it, compliance with legal obligations, or consent where required.
Who Receives Information
We may disclose information where required by law or where reasonably necessary to protect people, prevent abuse, or defend legal rights.
Retention and Deletion
- On Your iPhone
- Signing out clears the saved device key and session but retains server settings. The app removes diagnostic files on sign-out or setup reset, including after successful account deletion. Release builds also clear legacy diagnostic files at startup; development logs are otherwise overwritten when reopened for a new logging session. Uninstalling does not revoke a device or delete server-held information. iOS manages its own call-history entries.
- On Your Server
- Account and call records have no automatic expiry. Deleting a self-created account removes its password, devices, contacts, group memberships, presence, and call participation. A “Deleted person” record remains for calls you placed. Operator-managed accounts may be disabled rather than deleted. Logs and backups follow the operator’s retention arrangements; deleted information may remain in backups.
- At the Push Relay
- Installation records and rate-limit counters have no automatic expiry. Device registrations remain until explicitly removed; replacing a token or revoking an installation does not delete the registration. Duplicate-suppression records use a 24-hour window and are removed by a daily cleanup, normally within about two days of their last update. Cleanup failures can delay removal. Hosting logs and database recovery copies follow Cloudflare’s service settings.
To delete a self-created account, open Settings and choose Delete account. For operator-managed accounts, contact the operator. You can also remove devices or contacts in the app. Removing a device requests removal of its push registration; this may be delayed while the server retries an unavailable relay.
Your Choices and Rights
Depending on applicable law, including California privacy law where relevant, you may have rights to access, correct, delete, or obtain a portable copy of your information; restrict or object to processing; and withdraw consent where processing relies on consent. You may also complain to your local data protection authority.
For information held on your server, contact its operator. For the app or central push relay, use the privacy contact below. We may need to verify your identity and will respond within the period required by applicable law.
You can manage camera, microphone, local-network, and notification permissions in iOS Settings. Microphone access is needed for call audio; camera access is needed for video or code scanning. Codes can also be entered manually. Disabling notification alerts does not necessarily prevent incoming calls.
Security
The standard public deployment uses HTTPS and secure WebSockets (WSS). Your server operator is responsible for its TLS configuration; the central push relay is reached over HTTPS.
Passwords are sent to your server for authentication and stored there as salted scrypt hashes. Device keys are generated on the iPhone and protected using the iOS Keychain, with the Secure Enclave used when available. Relay installation credentials are stored as hashes.
No system is completely secure. Protect your device and credentials, and contact your server operator if you suspect unauthorised access.
Children’s Privacy
Crossbar is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child under 13 has provided information through Crossbar, contact us and the relevant server operator so that appropriate action can be taken.
Where Information Is Processed
Your server’s location is chosen by its operator. Cloudflare and Apple may process information outside your country under their service arrangements. Contact your server operator for details of its hosting location and any international-transfer arrangements.
Changes to This Policy
We may revise this policy to reflect changes to Crossbar or applicable requirements. We will update the effective date and version, and highlight material changes on this page or provide notice in the app.
Privacy Contact
For questions or requests about the app or central push relay, contact the developer at the address below. Direct requests about information held on an independently operated server to that server’s operator.