Driftly Privacy Policy
Version: 2026-10-15.1 · Limited test edition
Prepared: 15 October 2026 (UTC)
Effective: when this version is published in the service; the publication record supplies the effective date.
Privacy and deletion contact: [email protected]
1. Scope and important test limitations
This Policy describes personal data handling by the administrator of the Driftly test service at driftlyapi.jary.top and connected clients. It does not cover unrelated applications, external services you visit or another user’s independent handling of a copy they receive.
The current test supports email and password accounts. Guest login, external identity providers, external media storage and chat integrations, AI services, advertising integrations and payments are not enabled in this deployment. This Policy does not treat product plans as current data collection. A new integration or materially different use will require an updated notice and any required permission before activation.
This test is not anonymous or end-to-end encrypted. Public HTTPS terminates at Cloudflare, and the connection from Cloudflare to the origin currently uses unencrypted HTTP. The HTTPS address therefore does not mean every network segment carrying a login or message is encrypted. Do not submit confidential, highly sensitive or real-world identifying test content. Full automated erasure and export are also incomplete; see section 7. These limitations are not a request to waive your legal rights.
2. Data we receive and why
The precise fields depend on the enabled operation. The following categories describe this test, not permission to collect every possible item:
| Category and source | Examples | Purpose |
|---|---|---|
| Account and authentication data you provide or the service creates | Email address, one-way password verifier, email verification records, user ID, session and security records, acceptance of document versions | Register and authenticate accounts, verify actions, recover access, prevent account misuse and record required acceptance |
| Profile and preferences you enter | Nickname, enabled profile fields such as date of birth and gender, language, region and interaction preferences | Display an account, apply current eligibility rules, deliver localized features and use the preferences you select |
| Content and interactions you submit | Bottle text, replies, messages, participant references, favorites, blocks, reports and their timestamps; media only where an upload feature is actually enabled | Provide discovery and conversation, keep account history and preferences, enforce access and handle safety issues |
| Technical data produced by use | IP address, request time and route, client or device information supplied with requests, app version, error and rate-limit records | Route traffic, diagnose failures, secure accounts and infrastructure, investigate abuse and operate the service |
| Support and governance records you send or we create | Contact email, request description, limited evidence, actions and appeals, administrative audit records | Respond to requests, investigate complaints, document decisions and meet applicable obligations |
Passwords are checked using a one-way verifier rather than stored as a recoverable account password. Authentication credentials are still sensitive while being transmitted. Do not put passwords or verification codes in support messages or public content. We do not intentionally record plaintext passwords or authentication tokens in ordinary application logs.
The deployed service does not require precise GPS location, a contact list, government ID images or microphone access for email registration. Do not include such information in messages merely to test the service. A future client permission request needs a feature-specific explanation; this Policy is not advance consent for it. We do not treat an IP-derived region as verified residence or identity.
3. What other users and administrators can see
Recipients of a bottle, reply or conversation can see the content and account information presented by that feature, such as the nickname and displayed profile. Driftly is designed around an ordinary account profile, not a guarantee of an anonymous identity. Use profile fields with that expectation. Email login information, private IP records and security records are not intended as other users’ profile information.
Conversation participants can retain their own copies. A block or account deletion cannot recall a screenshot or information already disclosed outside our control. Do not share another person’s private information without permission or a lawful reason.
Authorized administrators may access relevant data to resolve a support or safety issue, maintain the service or comply with a lawful obligation. Private content and reports are not public search material. Access should be limited to the task; a report does not authorize browsing unrelated conversations or disclosing a reporter’s identity. Messages are not protected from the service administrator by end-to-end encryption.
4. Service providers and other disclosures
The current infrastructure uses the SmartVPS hosting service purchased through Sharktech, Cloudflare for DNS and proxied network traffic, and NetEase’s 163 SMTP service for outgoing email. Hosting can process stored application data; the network proxy can process traffic and related network metadata; the email service can process recipient addresses and message contents when email is sent. If you email our 163 contact address, the mailbox provider also processes that correspondence. We use these services to operate Driftly, not as a statement that all vendors process data in one country.
The current deployment does not send user content to external AI, moderation, media storage, external chat, advertising or payment integrations. Email delivery is enabled and may be triggered by operations that need it. We do not sell personal data or use private messages for behavioral advertising or external general-purpose AI training in this test.
We may disclose necessary information when responding to a valid legal requirement or a serious safety or security incident, after assessing the request and applicable law. Such disclosure is limited to what is justified. We do not provide unrestricted access merely because someone claims to represent an authority. If the operator or purpose materially changes, affected users require appropriate notice and safeguards; this Policy does not authorize unrestricted transfer to a buyer.
5. Locations and legal grounds
The server’s physical data-center location and the complete processing locations of its providers have not yet been verified for this test. Providers may process traffic, email or operational records in countries other than yours. A public IP address, language setting or region selected in the app does not establish data residency. We cannot promise that all data remains in a particular jurisdiction. Confirmation of processing locations and any required transfer arrangements is necessary before a wider release.
We use data to provide the operations you request, protect the service, handle support and comply with applicable obligations. Where the law requires consent for a particular purpose, we must request it with enough information for a meaningful choice. Optional consent may be withdrawn through the available control or the contact above; this can stop the related feature without automatically cancelling unrelated functions. Withdrawing consent does not make earlier lawful processing unlawful. Accepting service terms is not blanket consent to advertising, cross-app profiling or future integrations.
The rights and legal grounds that apply depend on the user’s situation and applicable law. This test has not been represented as approved for every country. No provision limits rights granted by mandatory law.
6. Security and sessions
The service uses account authentication, one-way password verification, permission checks and restricted administrative and configuration access. Database, cache and message-broker connections used by the application have TLS enabled. These measures do not remove the unencrypted proxy-to-origin connection described in section 1, and they do not establish encryption of every disk or backup.
Clients may keep session credentials on your device to maintain a login. The backend uses session and verification records to authenticate requests. Website analytics, advertising cookies or every future client’s SDK behavior are not authorized by this Policy; an actual client must disclose its own additional collection before release.
No service can promise absolute security. Protect your device and email account, use a unique test password and sign out on shared devices. Report suspected unauthorized access to our contact address without sending your password. We will investigate credible incidents and notify affected people and authorities where required by applicable law. We do not promise continuous emergency monitoring.
7. Retention, deletion and backups
Account data, content and security records are stored to support the purposes above. There is currently no confirmed, implemented category-by-category retention schedule or automatic ordinary-account inactivity purge. Do not assume records expire after an arbitrary number of days. Before wider release, the operator must establish and enforce retention periods for account data, content, logs, reports, providers and backups rather than keeping them indefinitely by default.
You can request account deletion in an available client function or by email without reinstalling the app. The current API schedules the account deletion process with a seven-day cancellation window. It does not certify complete erasure at the end of that window. Full cleanup across account records, content, queued work, caches, provider copies and backups is not implemented as one verified automated process in this test. Requests needing further cleanup require administrative follow-up; ask for confirmation of what has actually been removed and what remains.
Deletion may not remove content independently retained by recipients. Where applicable law permits or requires retaining limited evidence of abuse, disputes or legal compliance, we must restrict its use, explain the reason and applicable period unless prohibited, and delete it when that reason ends. We should not keep unrelated content merely because a report exists.
Manual operational backups can contain earlier data and credentials. They are access-restricted; immediate erasure from every existing backup is not guaranteed. A documented backup expiry and deletion-on-restore process has not yet been completed. Any restoration must be checked for previously requested deletions. We will not represent a deletion as fully completed while known copies requiring action remain unaddressed.
8. Requests and choices
Email [email protected] to request access to your data, correction, deletion, an available copy, withdrawal of optional consent, or review of a privacy complaint. Indicate the request and account identifier. These channels remain available if you are suspended or cannot reinstall the app. The test does not currently provide a complete automatic export facility; requests require individual handling and assessment.
We will use proportionate ownership checks, explain the scope and limitations of a response, and apply any legally required deadlines. We may limit or redact a copy to protect another person’s rights, security secrets or legally protected information. Do not send your password, authentication code, recovery key or full identity documents in an initial email. An inability to verify ownership may prevent disclosure or account changes, and should be explained rather than silently ignored.
Depending on applicable law, you may also have rights to object, restrict processing, nominate a representative or complain to a competent privacy regulator. You need not waive those rights to participate in the test. Raising a complaint does not justify retaliation or disclosure of your identity to another user.
9. Children
The current limited test is restricted to adults aged 18 and over and is not intended to collect children’s accounts. If you believe a child has supplied personal data or is at risk, report the account reference and concern to the contact above. Do not resend exploitative images or unnecessary identifying material. We will assess the concern, restrict access where appropriate and handle removal or legally required preservation through a controlled process. A future change to eligibility requires a new review and notice.
10. Updates and contact
We will identify policy revisions by version and effective date and provide appropriate notice of material changes. A material change in collection, recipients, security limitations, retention or purpose must not be hidden behind an unchanged version. Where required, new processing will wait for a valid choice or consent.
Privacy, deletion and complaint contact: [email protected]. This mailbox is not an emergency service.