Privacy Policy
Last updated 8 October 2026
Farlink uses end-to-end encryption for ordinary file and message delivery. Farlink’s delivery servers do not hold the private keys needed to decrypt that content. This protection does not cover text you choose to send in a report to Farlink or in an email to support. This page explains the content and metadata we process, how long it is kept and the limits of account deletion.
Your content and keys
File contents, file names, folder listings and ordinary messages are encrypted on the sending device before they are carried by Farlink’s delivery servers. Your local contact names and notes are also encrypted when synchronised between your account’s devices. Your private device keys are not sent to Farlink’s servers.
Your public account information is different: servers can read your account identifier and nickname, device names and public keys, public recovery keys, account changes and delivery-server addresses. Servers also keep the contact and delivery metadata described below. A public nickname or device name may identify you if you choose to put identifying information in it.
What Farlink’s servers process and retain
| Data | Purpose | Retention |
|---|---|---|
| IP addresses, connection information and IP-based usage counters | Connections, delivery, request and connection limits, queue limits, and limits on free server traffic | Connection information is used while providing the service. Free-traffic counters are stored by IPv4 address or IPv6 /64 prefix for a UTC calendar month and reset when the meter next processes activity in a new month. Queue records can also contain the IP bucket. This is not a promise that every operational log or saved copy is erased at month-end. |
| Public account and device information: identifiers, nicknames, device names, public keys, public recovery keys and account history | Authenticating devices, verifying account changes and addressing deliveries | Kept while the account is in use and, where needed, while deletion is being propagated. Permanent deletion markers and the other exceptions below remain after account deletion. |
| Sender and recipient identifiers, delivery identifiers, sizes, timing and acknowledgement information | Routing, retrying and deduplicating deliveries | Delivery records expire with their queued items. Acknowledging a mailbox item removes its encrypted message body, but duplicate-detection and routing information can remain until expiry. |
| Contact-request and relationship state between account identifiers | Recording whether deliveries are pending, accepted, declined or refused | Pending deliveries expire, but accepted and removed relationship records are not subject to the seven-day delivery limit. Records are updated or removed as the relationship changes and are included in account-deletion processing. |
| Encrypted messages, delivery envelopes and file chunks | Delivery to devices that are offline or temporarily unavailable | Mailbox deliveries expire within seven days. File queues use a seven-day default lifetime measured from reservation. A shared queued file may remain until all receiving devices have acknowledged or relinquished their access, or until it expires. Expired items are removed by periodic cleanup; this is not an exact physical-erasure deadline. |
| Account, subscription and network allowance counters, and records that prevent duplicate charges against an allowance | Applying free, Relay and Teams server-traffic allowances | Counted by UTC calendar month and reset when the relevant meter next processes activity in a new month. Account deletion does not immediately remove these counters. |
| Signed App Store transaction data and verified purchase records: transaction identifiers, product, purchase and expiry information, refund or revocation information, and links to Farlink accounts, devices or Teams networks | Verifying purchases and allocating the purchased service | The current service does not automatically delete subscription records when an account is deleted and does not give them an automatic expiry. Purchase verification does not give us your Apple Account sign-in details or payment-card details. |
| Reports submitted directly to Farlink: the reported account, reporter account and device identifiers, reason, receipt time, optional delivery identifier and any text the reporter chooses to include | Handling reports of abuse and protecting the service | The report store removes files older than 90 days, measured from the stored file’s last modification time, during periodic cleanup. Reports are not retained for 90 days after a case is closed. Account deletion does not automatically erase them. |
| Hashes identifying deleted accounts and device identifiers | Preventing deleted identities from being used again | Kept indefinitely. These markers can be matched against known identifiers and should not be treated as anonymous data. |
The delivery service does not decrypt ordinary files, folder listings or messages. Text voluntarily included in a report to Farlink is readable by the receiving Farlink server. A report is not an upload of your whole conversation or of attachments.
Advertising, tracking and your address book
Farlink does not include advertising or third-party analytics SDKs and does not access your system address book. We do not sell your personal data or use it for advertising tracking. The service does process the identifiers, delivery information and usage counters described in this policy.
This website sets no cookies and loads no advertising scripts or third-party analytics; its images and styles are served from this website. Visiting the website still sends connection information, including your IP address, to the service hosting it.
You normally add a contact by exchanging a one-time code and comparing the verification numbers. After account recovery you may also accept an incoming request from an account whose contact record is no longer on your device; that does not by itself mark the person as verified.
Who receives data and where it is processed
Apple processes App Store payments and subscriptions under its own terms and privacy policy. Farlink receives signed transaction information and uses it to verify purchases and provide the relevant allowance; we do not receive your Apple Account sign-in details or payment-card details through that process.
The official Farlink server list identifies servers in the United States and Russia. Farlink uses hosting providers to operate these servers. Data handled by the service can include encrypted delivery content and the readable account, connection, contact-state, purchase and report information described above. End-to-end encryption protects ordinary delivery content; it does not hide all metadata or text submitted directly to Farlink in a report.
People you send content to receive it on their devices. Reports about network Mail are sent to eligible administrators of that network rather than to Farlink. If you email support, your email provider and the provider of the support mailbox also handle the email, which is not protected by Farlink’s end-to-end message encryption.
The United States and Russia may have data-protection rules different from those where you live. Contact flyoz@vk.com with questions about the processing locations and recipients relevant to your data.
Contacts, messages and reports
A contact message is signed by the sending device and encrypted separately for the receiving account’s devices. Offline delivery is subject to the queue expiry described above. A first delivery may be held as a request. Your device receives the request and its text and file descriptions before you decide; attachment files are not downloaded until you accept.
You can block a contact or report a contact or a received message in the app. A contact report is sent over an encrypted connection to a Farlink server and is readable there for safety handling. It includes the reported account identifier, your account identifier, your authenticated device identifier, the reason, the time the server receives the report and, when you report a message, its delivery identifier. It also includes any text you choose to submit, including the reported message’s text only if you choose to include it. In-app reports do not include attachment files.
A report about Mail inside a network follows a different route: the app sends an end-to-end encrypted report to eligible administrators of that network, excluding you and the person reported. The message text is included only if you choose to include it; attachments are not included. If there is no eligible administrator, you can block the sender and contact Farlink support about service abuse.
Why we process personal data
Where the EU GDPR or UK GDPR applies, we process account and device information, delivery metadata and purchase information as necessary to provide the service you request and administer your plan. This processing is based on performance of our contract with you.
We process proportionate security and abuse-prevention information, reports and deletion markers for our legitimate interests in protecting users, preventing misuse and keeping the service secure, balanced against your rights. Where processing is required by an applicable legal obligation, we rely on that obligation. Where we rely on consent for a particular optional use, we explain that use when asking for consent, and you can withdraw it without affecting processing already carried out.
Account identifiers, public device information and the connection and routing information needed to operate the service are necessary for its operation. Purchase verification is necessary to provide a paid server allowance. Submitting a report or adding text to it is optional; please do not include sensitive personal information or information about other people that is unnecessary to explain the problem.
Data comes from your devices, from signed App Store transactions and notifications, and from other users when they address a delivery to you or submit a report involving you. Quota and security rules automatically decide whether a connection or delivery can proceed. Contact support if you believe a limit or refusal has been applied incorrectly.
Your data-protection rights
Where applicable law gives you these rights, you may request access to your personal data, correction of inaccurate data, erasure, restriction of processing and a portable copy of data to which the portability right applies. You may object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it at any time.
Send requests to flyoz@vk.com. We may need information reasonably necessary to verify that a request concerns your account. Do not send your private device keys or recovery key. We cannot decrypt ordinary message or file content held only as end-to-end encrypted data.
We will respond within the period required by applicable law, normally one month for EU GDPR and UK GDPR requests. If an extension applies we will explain it as required by law, and if we cannot fulfil a request in full we will explain why.
You may complain to the data-protection supervisory authority competent for your situation: in the EEA, the authority in your country of habitual residence, work or the alleged infringement; in the United Kingdom, the Information Commissioner’s Office. You do not have to contact us before making a complaint.
Deleting your account
In the app, open Settings → Account → Delete Account. Deletion is irreversible. The app must reach the account service and have at least one server accept the deletion before it starts erasing this device’s Farlink data. If the request or local erasure fails, the app reports the problem so you can retry.
A server that accepts the deletion refuses further use of the deleted identity and starts removing the account’s queued items, invitations and contact-state records. Cleanup is retried, including a second local pass after at least two minutes. This is not a guaranteed completion time for every record.
The server sends the deletion to the other servers and retries propagation for up to 90 days. Account-chain and deletion evidence may be retained while that work is pending. The 90-day period limits retries; it does not guarantee that a server which stayed unreachable has deleted its copy. Contact support if you need help with an incomplete deletion.
Other devices erase their app-owned Farlink data when they reconnect and obtain confirmation that the account was deleted. An offline device cannot be remotely erased while it stays offline. Files saved in folders you selected outside Farlink’s own storage, copies already received by other people and backups you made yourself are not recalled by account deletion.
Deletion does not automatically erase safety reports, purchase records or monthly usage counters; their retention is described above. Servers also keep permanent hashes of the deleted account and device identifiers to prevent reuse. These hashes do not contain the original account record, but they can be matched against known identifiers and are not a guarantee of anonymity.
Deleting your account or uninstalling Farlink does not cancel an App Store subscription. Manage or cancel subscriptions in your Apple Account subscription settings.
Children
Farlink is not intended for children under 13. The app does not establish a person’s age from an account’s cryptographic keys. If you believe a child under 13 has provided personal data to Farlink, contact flyoz@vk.com so the matter can be reviewed and appropriate action taken under applicable law. Our intended audience is separate from the App Store age rating and from any higher age or parental-authorisation requirement that applies in your country.
Changes and contact
We will update this page and its date when this policy changes. Where applicable law requires notice of a material change or fresh consent, we will provide that notice or seek that consent before the relevant new processing begins.
The controller responsible for Farlink’s processing is the developer identified as the provider of Farlink on its App Store listing. For privacy questions and data-protection requests, email flyoz@vk.com. Apple’s handling of App Store payments does not make Apple responsible for Farlink’s own server processing.