プライバシーポリシーPrivacy Policy

Drovyu (operations manager: Sakuya Tsuda) operates Drovyu Preview, the dvyu CLI, and related domains. Use the contact form for questions about this policy.

No account registration is required. The CLI generates a per-device identifier (UUID), stores it in ~/.dvyu/device.json, and sends it in request headers. Names and email addresses are not requested for standard use. When supporter features are used, the device identifier is linked to a supporter record containing a hashed email address.

The browser trial stores a trial identifier (UUID) in localStorage and sends it in a request header. It also sends each file extension, but not the file name or path, in plaintext so prohibited formats can be rejected by the server.

When a preview is created, we store encrypted files and an encrypted manifest, random storage keys, the preview id, device id, file count, total size, created / updated / last accessed timestamps, status, expiry, and retention settings.

The contact form collects the selected category, reply-to email address, subject, message, language, and Turnstile verification data. The message and email address are sent through Cloudflare to Discord.

Cloudflare may process standard infrastructure logs such as IP addresses, User-Agent strings, and request timestamps for delivery, security, and incident response.

During normal upload processing, file contents, file names, MIME types, entry points, and decryption keys are not sent to the server in plaintext. The decryption key exists only in the #k= URL fragment, which is not included in normal HTTP requests.

Stored data cannot be read without the decryption key. However, the Viewer JavaScript that performs decryption and its delivery infrastructure are part of the trust boundary. The service does not claim complete active-server zero knowledge against a compromised delivery system.

Payments are processed by Ko-fi, and Drovyu does not receive card numbers. Ko-fi webhooks temporarily provide an email address, event id, timestamp, and information such as the private message attached to a contribution.

We store an HMAC of the email address, hashes of tokens and claim codes, event ids, processing status, and related timestamps. During recovery, the submitted email address is sent to Resend to deliver a verification email.

We use the information to create, update, deliver, and delete previews; enforce usage limits; provide supporter benefits; respond to inquiries; prevent abuse; respond to incidents; and produce aggregate usage statistics.

The CLI stores previews.json, settings.json, device.json, and support.json under ~/.dvyu. They can be removed with dvyu uninstall.

Drovyu does not use its own analytics or advertising cookies. The site stores the language preference and browser trial identifier in localStorage and fetches an API that returns aggregate statistics only. Cloudflare's processing of standard infrastructure logs is described above.

• Standard previews generally expire after 48 hours. Encrypted files are progressively removed after expiry by an hourly cleanup process.
• Browser trial previews expire 24 hours after creation and are removed by the same cleanup process.
• Previews using the permanent setting expire after 30 days without access. This period cannot be extended after supporter benefits end.
• dvyu delete requests deletion. Encrypted files are removed by the cleanup process.
• Preview metadata rows currently have no fixed automatic deletion period.
• Claim and email verification records are generally retained for about 90 days; Ko-fi event ids and recoverable contribution records for about 180 days.
• Supporter records and device links currently have no fixed automatic deletion period. Contact us to request deletion.
• Contact messages are retained in Discord for as long as needed for support and recordkeeping. No fixed automatic deletion period is currently set.

Drovyu does not create independent secondary or scheduled backups of encrypted preview files uploaded by users. Source code is version-controlled on GitHub, but user-uploaded data is not stored there. Users must retain their original files.

Cloudflare R2, which stores encrypted preview files, uses internal replication and redundancy for durability. After expiry or a deletion request, files are removed from the active bucket by the cleanup process described above. Drovyu does not provide restoration of deleted files.

Cloudflare D1, which stores metadata such as preview and supporter records, automatically enables provider-managed Time Travel history. Depending on the Cloudflare plan and service specifications, changed or deleted metadata may remain in recoverable history for up to 30 days. This history is for database-level disaster recovery and does not guarantee restoration of an individual preview or data retention for users.

We use Cloudflare for storage, delivery, security, and Turnstile verification; Discord to receive contact messages; Ko-fi for contribution payments; and Resend for verification email delivery. GitHub and npm distribute source code and the CLI, but normal preview data is not sent to them.

We do not sell information. We may disclose information as permitted by applicable law to comply with legal obligations, protect rights and safety, address abuse, or complete a business transfer.

Cloudflare, Discord, Ko-fi, Resend, GitHub, and npm may process or store information in multiple regions, including outside Japan. Processing locations vary with each provider's infrastructure, terms, and service use; Drovyu does not guarantee a specific storage country. Review each provider's privacy information as well.

If a security incident or data breach is confirmed, we will investigate its scope and work to contain, recover from, and prevent recurrence of the incident. When users may be materially affected, we will disclose the known impact, response status, and any action users should take as soon as reasonably practicable through the official site, the status page, or another appropriate channel. Where contact information is available, affected individuals may be notified directly as appropriate, and legally required reports will be made to relevant authorities. Direct notice may not be possible for anonymous users who have not registered an account.

Send questions or deletion requests through the contact form. Do not submit decryption keys, claim codes, verification tokens, or other secrets, including through the form.

We may update this policy as the service or applicable law changes. Material changes will be announced on this site.

• July 12, 2026: Added the operations manager, backup disclosures, and incident notification policy.
• July 12, 2026: Added international processing and aligned disclosures with the Trust and Security pages.
• July 11, 2026: Initial publication.