Dropr Privacy Policy

Review draft, November 3, 2026. Not in effect. Resolve every [NEED: ...] item before publication.

Review revision: draft-2026-11-03-r16. No binding version is approved.

Effective date: [NEED: publication date]

CodePilot Inc., based in San Francisco, California, operates Dropr. This policy explains how we handle information about people using our Mac app and websites, uploading files, or opening shared links.

The intended market for Dropr accounts at launch is the United States. Public files can be opened without an account.

Privacy requests: hello@codepilot.com.

CodePilot Inc. public policy correspondence address: 981 Mission Street, San Francisco, CA 94103, USA.

Files uploaded to Dropr are public. Anyone with a share or direct file link can view and download them without an account. Links can be forwarded. Original filenames, previews, and information embedded in files can reveal personal information. A random link is not a password. Do not upload confidential information or information you lack permission to publish.

1. What we collect and why

Accounts and sign-in

We collect your email address, name, account identifier, and optional profile image to create and manage your account. We store sign-in and connected-device records, including IP addresses and browser information for web sessions, to keep accounts working and help prevent misuse.

When an available Apple or Google sign-in option is used, we receive an account identifier and identity information the provider supplies, such as your email address and name. The provider also processes information under its own privacy policy. We do not receive your Apple or Google password.

Files and previews

We store files you upload, their original filenames, file sizes, types, checksums, upload identifiers, and upload and deletion times. We process these to receive files, prevent duplicate retries, enforce storage limits, create previews, and deliver public links. A file can contain personal information about you or other people, including metadata that your software added.

Billing

Stripe processes payment details when you subscribe to Plus. We receive information needed to manage billing, such as customer and subscription identifiers, subscription status, billing interval, payment-confirmation events, and the date your paid access ends. We do not store your full payment-card number or security code on Dropr's servers. Stripe handles payment and fraud-prevention information under its own privacy policy.

Visits, support, and abuse reports

Our servers and infrastructure providers process technical information when you visit, sign in, upload, or open a public file. This can include IP address, browser or device information, requested URL, request time, and response status. A request log may contain a public file's identifier. We use this information to deliver requests, diagnose errors, protect the service, and investigate abuse.

If you contact us or submit a report, we receive your contact details and message. Our contact form also records IP address and browser information. We use these records to respond, investigate, and keep a record of the issue.

2. Information stored on your Mac

The app uses macOS permissions for screenshot capture and Finder selection. These features act when you request them; Dropr does not continuously record your screen or access your camera or microphone. You can still choose to upload files containing recordings you made elsewhere.

Sign-in credentials are stored in the macOS Keychain. Preferences, retry copies of files, and recent-upload history are stored locally. The recent list shows up to ten successful uploads for the connected account and server, with local image thumbnails where available. It is not a history synced across your Macs.

Failed uploads can remain on your Mac for retry until they succeed or you discard them. Deleting a published file from the server does not automatically erase your original files, local recent history, thumbnails, or copies in your own backups.

3. Cookies and tracking

Dropr uses browser cookies and similar storage for sign-in, security, and navigation through account setup. Blocking those cookies can prevent account features from working. The separate host that serves raw files and generated previews does not set Dropr sign-in cookies. This does not prevent that host from processing request information such as an IP address.

Embedded Stripe checkout and optional identity providers can process device and browser information when you use them.

[NEED: verify the complete deployed website, application, infrastructure, and provider inventory before finalizing the following disclosures: whether any analytics or advertising technologies run; whether third parties collect information over time and across services; whether CodePilot sells personal information or shares it for cross-context behavioral advertising; and how Do Not Track and Global Privacy Control signals are handled. Do not publish a blanket no-cookies or no-tracking claim.]

4. When information is shared or accessed

Public access you initiate. Uploading makes your file, filename, and preview available through public links. Recipients may copy or redistribute them. We cannot control what recipients do with their copies.

Service providers. We use providers to host the app, store files, send account emails, process payments, and operate support. Apple and Google handle sign-in when you choose an available provider option. Providers receive the information needed for their roles.

[NEED: confirm the active hosting, file-storage, email, payment, and support providers, their relevant legal entities, processing locations, and contractual safeguards; complete the provider list before publication. Code configures Resend for outgoing email and supports Cloudflare R2 storage, but configuration and historic deployment records alone do not verify the current production provider inventory or geographic locations.]

Support, security, and enforcement. Authorized personnel may access relevant files and account records to resolve support requests, maintain the service, investigate reports, enforce our content rules, or protect people and systems. We do not review every upload before publication.

Legal obligations. We may preserve or disclose relevant information to comply with law or valid legal process, respond to unlawful content, or protect against serious harm where the law permits. Copyright notices and counter-notices may be shared with the other party, including contact details needed for that process.

Business changes. Information may be transferred as part of a merger, acquisition, or sale of the service, subject to applicable law. We will provide any notice or choice the law requires.

5. Retention and deletion

Published files do not automatically expire. They normally remain available until you delete them or we remove them under our terms or the law. For account closure and associated deletion, contact us as explained below. Downgrading from Plus alone does not delete published files.

When you delete an upload, Dropr blocks new requests through its share and direct links. A background process removes the stored original and generated previews. This does not recall downloads or transfers already underway. We retain a database record of the allocated link and upload, including some metadata, to prevent link reuse and support retry identity. Deleting file bytes is not the same as deleting every associated record.

Unfinished server-side uploads are scheduled for cleanup after 24 hours. Job failures can delay storage cleanup. Local retry copies on your Mac are separate from server-side cleanup.

[NEED: define and verify retention periods or specific retention criteria for account information, deleted-upload metadata, access and security logs, contact messages, billing records, abuse evidence, and backups. Include a bounded deletion procedure for account-closure requests and exceptions for tax, disputes, security, and legal holds. No verified full-account erasure or backup-expiry timetable exists in this draft.]

6. Your choices and requests

You can update available profile details, delete individual uploads, revoke connected access, and manage billing through your account. You can change macOS permissions in System Settings.

Contact our privacy address to request access to, correction of, or deletion of personal information, or to request account closure. We may need to verify your identity. We will explain any lawful reason we cannot complete a request. Do not send us your sign-in code, upload token, or payment-card details.

Depending on where you live and which laws apply, you may have additional rights to obtain a copy of your information, limit certain uses, object to processing, appeal a decision, or complain to a privacy regulator. We do not penalize you for exercising applicable privacy rights. A deletion request does not require us to erase records we must lawfully retain.

[NEED: assess California privacy obligations at the CodePilot Inc. level, including CCPA coverage and any service-provider role; add the required notice at collection and request or opt-out methods if applicable. For UK/EEA or other international users, assess applicable laws and add required legal bases, transfer safeguards, representative or regulator details, and request procedures. The intended US-only account market does not resolve review of international recipients, actual use, provider processing, or applicable international law.]

7. Security and international processing

Dropr uses HTTPS for production connections and access controls for account management. Uploaded files are intended to be public; access controls around the storage system do not make a published link private. No service can guarantee complete security.

CodePilot is based in the United States. Providers may process information in other countries, where laws can differ from those where you live.

[NEED: verify actual hosting, storage, email, and support locations and any required international transfer arrangements. Do not claim US-only or EU-only storage without verification.]

8. Children

Dropr accounts are for people aged 13 and over. Users under 18 must have permission from a parent or legal guardian. We do not offer accounts to children under 13. Contact our privacy address if you believe a child under 13 has created an account or supplied information directly to us, so we can investigate and take appropriate action.

[NEED: verify the procedure for accounts discovered to belong to children under 13, and review obligations concerning public recipients and information about children contained in other people's uploads. An account-age rule and parental permission for teenage users do not establish compliance with children's privacy or contract law.]

9. Changes and contact

We will update the effective date when this policy changes and notify account holders of material changes. We will obtain consent when required by law. You can send questions or privacy requests to the privacy contact above.

Document credit

Adapted in part from the Basecamp open-source policies, licensed under CC BY 4.0. CodePilot has rewritten and added provisions for Dropr. This credit concerns the policy text, not the licensing of the Dropr app or user uploads.