Privacy Policy

What we don't store

File content and names are sent through the WebRTC DataChannel between devices. They are not sent to Firestore, Google Analytics, or Senddfile's operational and diagnostic records. We do not host a copy for later download and cannot recover the file after the transfer. The name is shown only to the recipient through the WebRTC channel so they can review what they are receiving.

Data needed to connect

For browsers to find each other, Firebase Firestore temporarily exchanges technical session information:

• SDP — describes how the WebRTC connection should be configured.
• ICE candidates — describe possible routes and may contain network addresses and ports.
• Transfer code (callId) — lets the recipient find the correct session.

This data is used to establish or resume the connection; it does not contain the file name or content. We use Google's public STUN servers to discover a direct route. We do not use a TURN server, so Senddfile does not relay the file through one.

Operation and diagnostics

We keep limited technical records to understand whether the service works and investigate transfers that end in success, failure, or cancellation:

• Activity: timestamps, transfer state, and an optional result code.
• Diagnostics: browser, duration, byte counts, performance metrics, a technical timeline, and connection data such as SDP and ICE candidates.

These records do not include the file name, content, or callId. Connection data may include network addresses. We do not ask for sensitive personal information to use the service. Firestore read access is restricted to the authorized administrator account, and the records are used for operations rather than profiling or targeted advertising.

How long we keep it

Signaling sessions are temporary, and the app attempts to remove them when they finish. Diagnostics receive a 14-day expiration date and summarized activity records a 90-day expiration date. Firestore deletion may occur after those dates while it depends on operational cleanup or asynchronous TTL processing.

Accounts and signup

Public use of Senddfile requires no signup or login and does not keep a profile, contact list, or personal file history. There is only a restricted administrator account used to view operational records protected by Firestore rules.

Cookies and analytics

We use Google Analytics with analytics storage denied, so the _ga cookie is not created. We send page views and events with limited categories such as transfer role, size range, result, grouped browser, and CTA clicks. We do not send the file name, content, or callId. Language and theme may be saved in localStorage and remain on the device.

Services we use

The site uses Firebase Hosting, Firestore, and Google Analytics, plus Google's public STUN servers for WebRTC route discovery. These services may process technical data normally present in an internet connection under their own terms. We currently use no TURN relay, cloud storage for files, or server that receives transferred content.

Your rights

You may contact us with questions or requests related to your data. Because there are no user accounts and operational records do not keep names, email addresses, or callIds, it may not be technically possible to associate a specific record with a person without additional information they provide.

Contact

For privacy questions or about this policy, write to us at: