Privacy Policy
This policy explains how PriVLink processes data when you use the chat, calling, and group features.
Effective: 2 November 2026 · Last updated: 2 November 2026
1. About PriVLink and the data controller
PriVLink is a private communication app operated by the PriVLink/Bukapasar team. In this policy, “we” means the PriVLink operator. For privacy questions or requests, contact admin@bukapasar.com.
This policy applies to the PriVLink Android app and the official page at bukapasar.com/privlink. It does not apply to third-party sites or services, including Google advertising.
2. Data we process
2.1 Device identity
On first use, PriVLink generates a Peer ID, an X25519 key pair, and an Ed25519 signing key locally. Private keys are stored in secure storage on the device and are not sent to the server. The Peer ID and public keys are sent to the signaling server and to contacts/groups you communicate with so that messages can be routed and verified.
2.2 Profile
You may provide a display name, bio, and avatar. Avatar and bio are stored locally. Your display name may be shared with people on the same local Wi-Fi when Nearby is active and with contacts you add. Bio and avatar are optional.
2.3 Contacts and groups
PriVLink stores the contacts you add (Peer ID, public key, name, trust status) and group metadata (group name, group ID, members, admins, membership status) on your device. PriVLink does not read your device address book. Group metadata is also processed by the server to deliver membership events and group messages. The list of users you block (Peer ID and name) is stored locally on your device.
2.4 Messages and attachments
Personal and group messages are end-to-end encrypted on the device before transmission. The signaling server receives ciphertext and the routing metadata needed to deliver it (sender, recipient, group, timestamp, message ID).
- For offline recipients, the server may store ciphertext for up to 7 days or until the recipient acknowledges it, with a limit of 500 messages per peer.
- Group messages and membership events may be stored temporarily with the same time and count limits.
- Plaintext messages, attachments, photos, documents, and voice notes are stored in the app's internal storage on your device until you delete them, use panic wipe, or uninstall the app.
- Messages already received and decrypted by a recipient cannot be withdrawn from that recipient's device by us.
2.5 Audio and video calls
Call media is sent peer-to-peer over WebRTC. The app does not record calls. The server only processes offer/answer/ICE signals and connection metadata to help establish the call. To assist with NAT traversal, the app uses Google STUN servers; your IP address may be visible to the STUN provider. Network providers and operating systems may also process connection metadata under their own policies.
2.6 Local Wi-Fi and SoftAP
When local mode is active, PriVLink discovers peers on the local Wi-Fi network by broadcasting the Peer ID, display name, public key, local IP address, and service port. This information can be seen by other PriVLink devices on the same network. Discovery information is not sent to the internet server.
If you enable a local hotspot (SoftAP), Android creates the SSID and password. PriVLink displays them so you can connect other devices. PriVLink does not collect GPS coordinates or track your location. Any location permission requested by Android is used only for Wi-Fi/SoftAP functionality on certain Android versions.
2.7 Advertising
PriVLink displays banner and interstitial ads from Google AdMob. Google and its advertising partners may process data such as the device advertising ID, IP address, approximate location, device/app information, and ad interactions to provide, measure, and prevent abuse of advertising. This processing is governed by Google's privacy policy: policies.google.com/privacy.
You can reset or delete your advertising ID in Google/Android settings. In regions that require ad consent, Google may display or use consent signals under its policies.
2.8 Server logs and security
The signaling server may process IP addresses, connection times, Peer IDs, public keys, connection status, and other technical information needed to operate the service, prevent abuse, and diagnose failures. Logs are retained for a limited period for security and operational purposes.
2.9 Diagnostics
The app does not include a third-party analytics or crash reporting SDK. Android and Google Play may process diagnostic data under Google's policies. Local app logs can be viewed on a development device and are not automatically sent to us.
2.10 Abuse reports
If you use the Report feature, the app opens your email app and prepares a report containing the target type, name, user/group ID, group name (if any), reason, additional details, time, and app version. The report is sent only if you send the email. We use report data to review and address abuse.
3. Purposes and legal bases
- Providing the service: creating identity, routing messages, calls, groups, notifications, and local features.
- Security: verifying keys, preventing replay and spam, and maintaining availability.
- Advertising: displaying and measuring ads through Google AdMob.
- Support and compliance: responding to questions, abuse reports, and legal obligations.
Legal bases may include performance of a contract, consent (for example for personalized ads where required), legitimate interests (security and operations), and legal obligations. You may withdraw consent as permitted by applicable law.
4. Sharing data
- With other users: messages, attachments, display name, Peer ID, public keys, and group metadata needed for communication.
- With the signaling server/hosting provider: ciphertext and routing metadata, including store-forward data.
- With Google AdMob and ad partners: ad data under Google's policies.
- With authorities: where required by applicable law or to protect rights and safety.
We do not sell personal data. We do not share plaintext message content with advertisers; advertisers receive ad data processed by Google.
5. Retention and deletion
- Local data (identity, contacts, messages, attachments, profile) remains until you delete it, leave a group, use panic wipe, clear app data, or uninstall.
- Server store-forward queues: up to 7 days, acknowledgment, or the limit of 500 items per peer, then deleted.
- Server logs: a limited period for security and operations.
- Ad data: handled by Google under its policies.
Because PriVLink does not use a server account, there is no user account to delete. To request deletion of data that may remain on the server, contact admin@bukapasar.com. Messages already received by a recipient cannot be deleted from their device by us.
6. Security
PriVLink uses X25519 and AES-256-GCM end-to-end encryption for messages, Ed25519 signatures for invitations and membership, and TLS/WSS to the server. Private keys are protected by the device's secure storage. No system is completely secure. Metadata such as timing and communicating parties is not encrypted, and a compromised device may expose data.
7. Device permissions
| Permission | Use |
|---|---|
| Camera | Video calls, QR codes, and avatar |
| Microphone | Voice notes and audio/video calls |
| Notifications | Incoming message notifications |
| Internet / network | Signaling, WebRTC, and ads |
| Wi-Fi / Nearby Wi-Fi | Local discovery and hotspot |
| Location (if requested) | Wi-Fi/SoftAP functionality on certain Android versions; not GPS tracking |
8. Your rights
Depending on applicable law, you may have the right to access, correct, delete, restrict, or object to processing, and to request portability. You may also lodge a complaint with a competent data protection authority. To exercise these rights, contact admin@bukapasar.com. We may request additional information to verify a request.
You can control local data directly in the app (delete contacts, leave groups, panic wipe) or by clearing app data/uninstalling.
9. Children
PriVLink is intended for users aged 18 or older. We do not knowingly collect data from children under 18. If you believe a child under 18 is using the app, contact us so appropriate steps can be taken.
10. International transfers
The signaling server, hosting providers, and Google may process data in other countries. We seek providers that offer protections required by applicable law, including contractual safeguards where necessary.
11. Changes to this policy
We may update this policy from time to time. Material changes will be announced on this page or in the app. The “last updated” date shows the latest version. Continued use after changes means you accept the updated policy to the extent permitted by law.
12. Governing law
This policy is governed by the laws of the Republic of Indonesia, including applicable personal data protection rules. If you are in another region, mandatory rights under local law still apply.
13. Contact
Privacy questions, abuse reports, or data requests: admin@bukapasar.com
This page is available at https://bukapasar.com/privlink/privacy-en.html.