1. Scope and privacy contact
This Privacy Policy applies to DirectBeam: File Transfer,
Android package name com.quizfans.directbeam, referred to in this
policy as “DirectBeam”, “the app”, “we”, “us” or “our”.
DirectBeam is an Android application that provides user-initiated file transfer between compatible Android devices and local browser-enabled devices, including iPhone, iPad, Mac and PC.
Publisher brand: Quiz Fans Studio, Romania. Windows Companion is an optional desktop component of DirectBeam; it is not a separate cloud-storage provider. The individual data controller's full legal identity is available in Section 23: Contact and legal controller.
Privacy and support contact: quizfans.studio@gmail.com.
2. Key privacy summary
- DirectBeam does not require a DirectBeam account.
- DirectBeam does not operate a cloud-storage service for selected local-transfer files.
- Files are transferred between devices chosen or authorized by the user.
- Android-to-Android and browser-based transfers use different security models.
- The app may use Google services for nearby connectivity, advertising, consent, billing and code scanning.
- Operational settings, transfer history and diagnostics may be stored locally on the Android device.
3. Files and content selected for transfer
DirectBeam accesses files, folders, photographs, videos, audio, documents, archives or other content only when you select, authorize or make that content available through Android permissions, Android system pickers, a local browser session or another supported transfer workflow.
The selected content is processed to provide the transfer you initiate. We do not claim ownership of your files.
3.1 Android-to-Android transfer
Selected files and necessary transfer metadata are transmitted to the compatible receiving Android device that you approve. Supported Secure Transport V6 sessions use authenticated AES-256-GCM encryption, ephemeral session keys and integrity verification.
3.2 Group Beam
When you use Group Beam, selected files and transfer metadata are sent to the compatible nearby receiver devices you approve. Progress, retry state and completion information may be maintained separately for each receiver.
3.3 PC Connect
PC Connect allows a browser on a computer to upload files to Android or download files that the Android user has authorized. The transfer page is hosted temporarily by the Android device on the local network.
3.4 Apple & Web Transfer
Apple & Web Transfer permits an iPhone, iPad, Mac, PC, tablet or other compatible browser-enabled device to exchange files with the Android device. The browser device connects by scanning a QR code or opening a temporary local address displayed by DirectBeam.
The browser user may:
- select photographs, videos, documents or other files for upload to Android;
- download files that the Android user has made available for the session;
- view local transfer status and progress;
- use the same trusted Wi-Fi network or a DirectBeam local-only hotspot.
The browser device does not need a DirectBeam application or DirectBeam account. The local transfer page and transfer content are served by the Android device rather than by a DirectBeam cloud-storage server.
3.5 Optional DirectBeam Windows Companion
The Windows Companion is a separate, optional Windows desktop application used with DirectBeam on Android. When you explicitly connect and authorize it, the desktop app may discover your Android device on the local network, establish an authenticated HTTPS connection with certificate-fingerprint verification, display the files and folders made available by Android, and send or receive files you select. The desktop client is distinct from the browser-based PC Connect HTTP workflow.
For those operations, the two devices may exchange device identifiers, display names, local IP addresses and ports, TLS certificate fingerprints, pairing or session credentials, file names, sizes, folder information, progress, integrity information and selected file contents. Only the connected devices participate in the ordinary local file transfer. The user controls which device, folder, file and destination is authorized; other local-network participants must not be treated as trusted merely because they share a Wi-Fi connection.
3.6 Photo and video library permissions for Windows Phone Library
The optional Windows Phone Library feature can list photos and videos from Android's media library for browsing and selective download on a paired, authorized Windows PC. After you explicitly select ALLOW MEDIA ACCESS in DirectBeam and approve the Android permission prompt, the Android app may read the permitted images and videos using Android MediaStore. Depending on the permission scope, the companion may display file names, sizes, media types, dates, folder information and available previews, and can download the files you choose.
For this functionality, DirectBeam requests android.permission.READ_MEDIA_IMAGES and android.permission.READ_MEDIA_VIDEO on supported Android versions. These permissions support browsing the authorized library from Windows; Android Photo Picker is also available for selecting specific files directly on your phone, but does not itself provide remote library browsing. Granting broad media access is optional: you can use the separate CHOOSE PHOTOS / DOCUMENTS picker instead. On supported Android versions you may choose selected photos and videos rather than the full library. You can later modify or revoke access in Android Settings.
Only pair with computers you trust. Anyone using an authorized PC may see the media items exposed by the permissions you grant and may keep local copies of files downloaded during the session. DirectBeam does not automatically upload the Android photo or video library to a DirectBeam-operated cloud service; transfer of file content occurs through supported device-to-device workflows.
4. Transfer metadata and technical information
To identify, transmit, resume, verify and save files, DirectBeam may process information associated with a transfer, including:
- file name and extension;
- file size and MIME or media type;
- file modification time, where available;
- relative folder or path information, where supported and authorized;
- transfer identifier and session identifier;
- chunk number, byte offset and upload or download state;
- progress, speed, remaining-time estimate and completion status;
- cryptographic hash or integrity-verification result;
- sender or receiver display name and device role;
- local IP address, network port and local connection status;
- browser request headers or browser user-agent information received by the local Android server;
- temporary session tokens used to restrict access to the local session.
Depending on the selected file and access granted, files may already contain embedded metadata such as EXIF, media, document-author, creation-time or geographic metadata. DirectBeam transfers file bytes and does not intentionally remove all embedded metadata.
5. Local browser-session security
PC Connect and Apple & Web Transfer use a temporary authenticated local HTTP session. The session may use a random token included in or associated with the displayed QR code or local address.
The temporary token, local address and QR code should be treated as private. A person who can access the same network and obtains valid session information may attempt to connect to the local transfer page.
DirectBeam may expire or invalidate local browser sessions after inactivity, completion, manual shutdown or when the user leaves the transfer function.
5.1 Windows Companion pairing security
Supported Windows Companion connections use HTTPS with verification of the Android device's presented TLS certificate fingerprint. The first connection requires device pairing and user approval. A remembered device may subsequently reconnect using locally stored pairing information. This desktop connection does not make browser-based HTTP mode encrypted; browser mode remains a different transfer path. Protect your phone, PC, pairing code and local network, and unpair devices you no longer trust.
6. No DirectBeam cloud storage
DirectBeam does not upload files selected for local transfer to a cloud-storage server operated by us. Files are transmitted between the devices participating in the session.
This statement does not mean that every third-party service used by the app processes no technical data. Google services and operating-system components may process limited technical information as described below and under their own privacy terms.
7. Device discovery, nearby permissions and connectivity
To discover, advertise, connect or communicate with compatible devices, DirectBeam may use:
- Wi-Fi Direct;
- local Wi-Fi or LAN communication;
- Google Nearby Connections;
- Bluetooth or Bluetooth Low Energy capabilities used by supported discovery services;
- Android nearby-device permissions;
- Android location-related permissions on operating-system versions where those permissions are technically required for nearby discovery;
- a local-only Android hotspot for supported browser-transfer sessions.
DirectBeam does not use nearby or location-related permissions to create an advertising location history or a DirectBeam location profile.
Android, Google Play services or the Nearby SDK may process device and performance information required to provide nearby discovery and connectivity. This may include discovery latency, connection latency, reliability, throughput, device information and related diagnostic metrics, subject to Google’s settings and privacy practices.
8. Information stored locally on your Android device
DirectBeam may store the following operational information locally:
- application preferences and feature settings;
- transfer history and completion status;
- file names, sizes and local destinations shown in transfer history;
- connection diagnostics and error details;
- saved folder permissions granted through Android’s Storage Access Framework;
- temporary or partial file data required for supported resume workflows;
- local session information and temporary tokens;
- advertising-consent state;
- purchase or entitlement status needed to identify available Pro functions.
Local information can generally be removed through available in-app controls, by clearing DirectBeam storage in Android settings or by uninstalling the app. Files already saved outside the app’s private storage must be deleted from their destination by the device owner.
8.1 Information stored locally on a Windows PC
The Windows Companion implementation reviewed for this update stores paired-phone metadata (device identifier, TLS fingerprint and last-known local endpoint) at %LOCALAPPDATA%\DirectBeam\Companion\phone.json. The pairing secret is stored separately in Windows Credential Manager, not in that metadata file. Pairing failures may create a local pairing-diagnostic.log with timestamps, operation stage, exception type and HTTP status, without intentionally recording pairing codes or transfer-file contents.
Files received or exported to Windows are saved to the folder you select or the application's displayed default destination, commonly under your Windows Downloads folder. Windows may also create temporary files or operating-system records during ordinary operation. Deleting the desktop program does not necessarily delete files already exported, paired-device metadata, stored credentials or local logs. The Windows PC owner must manage those separately. The Companion does not require a separate DirectBeam account.
9. Diagnostics and support information
DirectBeam may generate local diagnostic information such as connection state, selected transport, transfer errors, file-processing results and compatibility information.
Unless a specific reporting function clearly informs you otherwise, DirectBeam does not automatically upload transfer-file contents to us for support. If you voluntarily email diagnostic information, screenshots, descriptions or files to support, we will process the information you choose to provide for responding to your request and investigating the reported issue.
10. Advertising and privacy consent
The free version may display advertising through Google Mobile Ads. DirectBeam may use Google’s User Messaging Platform (UMP) to request and manage privacy choices where required.
Depending on your region, consent choices, Google account, device settings and advertising configuration, Google and its advertising partners may process:
- advertising or application identifiers;
- IP address and approximate region inferred from network information;
- device model, operating-system version and language;
- application interactions and ad interactions;
- consent choices and privacy-message status;
- fraud-prevention, security, measurement and diagnostic information.
Personalized advertising is used only where permitted by applicable law, consent and platform settings. Where available, privacy choices may be managed through the app, the Google consent interface, Android settings or Google account settings.
Google processes information under its own privacy terms: Google Privacy Policy.
11. Google Play Billing and DirectBeam Pro
Optional DirectBeam Pro features may be purchased through Google Play Billing. Google processes the payment transaction. We do not receive your complete payment-card details.
DirectBeam may receive or process:
- product identifier;
- purchase state;
- purchase or transaction token;
- acknowledgement and entitlement status;
- information required to unlock or restore the purchased feature.
Purchase records are also processed and retained by Google Play under Google’s own terms and legal obligations.
12. Third-party services and SDKs
Depending on the distributed application build and features enabled, DirectBeam may include or interact with:
| Service | Purpose | Possible technical processing |
|---|---|---|
| Google Nearby Connections | Nearby-device discovery, connection and data exchange | Device information, connection and performance metrics, identifiers required by the service |
| Google Mobile Ads | Advertising in the free version | Advertising identifiers, IP address, device information, app and ad interactions, diagnostics |
| Google User Messaging Platform | Privacy disclosures and consent choices | Consent status, privacy-message eligibility, device and regional signals |
| Google Play Billing | DirectBeam Pro purchase and restoration | Product, transaction, token and entitlement information |
| Google Play services or code-scanning components | QR or barcode processing and supporting Android functions | Technical and diagnostic information required by the component |
Third-party providers process information under their own agreements, privacy policies and retention practices.
At the date of this policy, the current application configuration described to us does not use Firebase Analytics or Firebase Crashlytics. If either service is added in a future build, this policy and the Google Play Data Safety declaration must be updated before or when that build is distributed.
12.1 Website and installer distribution
DirectBeam's public policy pages and Windows installer are provided through GitHub Pages and GitHub Releases. When you open those pages or download an installer, GitHub may process IP addresses, access requests, security logs and related technical data according to GitHub's own privacy terms. Those website or download interactions are separate from transferring files locally between your devices. Do not send private pairing codes, file contents or purchase tokens to support unless strictly necessary and expressly requested through an appropriate secure channel.
13. How information is used
Information is processed only as reasonably necessary to:
- provide file selection, sending, receiving and saving functions;
- discover and connect compatible devices;
- operate local browser sessions;
- show progress, history, resume state and integrity results;
- maintain security, prevent misuse and diagnose failures;
- provide support requested by the user;
- display and measure advertising where applicable;
- manage privacy consent;
- process and restore DirectBeam Pro entitlements;
- comply with legal obligations and protect legal rights.
14. Legal bases for EEA and UK users
Where the GDPR, UK GDPR or similar law applies, processing may rely on:
- performance of a contract or requested service, for providing the file-transfer function you initiate;
- consent, for permissions, personalized advertising or other processing where consent is legally required;
- legitimate interests, for security, fraud prevention, compatibility, diagnostics and service protection, where those interests are not overridden by your rights;
- legal obligation, where processing is required by applicable law.
15. Sharing and disclosure
We do not sell your selected transfer files or personal information.
Information may be disclosed or processed only in limited circumstances:
- to the device, browser or computer that you intentionally connect to;
- to Google services used for nearby connectivity, advertising, consent, billing and supporting application functions;
- to service providers assisting with a support request you initiate, where applicable;
- when required by law, legal process or competent authority;
- when reasonably necessary to investigate fraud, prevent harm, protect users or defend legal rights.
16. Retention and deletion
- Transferred files: retained on the sending or receiving devices until deleted by the relevant device owner.
- Partial or temporary transfers: retained locally only as needed for the active or supported resumable transfer, cleanup or recovery process.
- Transfer history and local diagnostics: retained on the Android device until removed through app controls, application-data clearing or uninstallation.
- Browser-session tokens: intended to be temporary and invalidated after expiry, shutdown, completion or manual termination.
- Support communications: retained as reasonably necessary to respond, document the issue and meet legal obligations.
- Purchase records: retained by Google Play according to Google’s requirements.
- Advertising and consent data: retained by Google or its partners according to their applicable policies, consent and account settings.
DirectBeam has no DirectBeam account database to delete. Local-data removal instructions are available on the Data Deletion and Local Data Controls page.
Windows Companion data: paired-device information and local diagnostic logs are held on the user's PC until erased there; an authorized user can unpair the phone, delete local Companion metadata and logs in %LOCALAPPDATA%\DirectBeam\Companion\, and remove corresponding entries from Windows Credential Manager. Downloaded files and exported copies must be deleted separately from their storage folders. Uninstallation alone should not be relied on to remove all such data.
17. Your privacy choices and rights
Depending on your jurisdiction, you may have rights to request access, correction, deletion, restriction, objection, portability or withdrawal of consent concerning personal information processed by us.
Many DirectBeam records are stored only on your device and are not accessible to us. For local data, you can:
- delete transfer-history entries inside the app where available;
- delete received or transferred files from their destination;
- revoke file, nearby-device, notification or storage permissions through Android settings;
- clear the application’s local storage;
- uninstall DirectBeam;
- manage advertising and consent choices through available app and Google settings.
Requests concerning information actually held by us may be sent to quizfans.studio@gmail.com. We may need sufficient information to identify the relevant communication or request, but we will not ask for unnecessary transfer-file content.
For Windows desktop transfers, keep Windows updated, protect local account access, verify the Android device fingerprint during pairing and use a trusted network. A verified HTTPS connection between devices does not make a file safe to open; scan unknown files and maintain backups. If a computer is shared, other persons with access to that Windows profile or its download folders may be able to view received files.
Your right to complain: If you consider that our processing of personal data infringes applicable data-protection law, you may lodge a complaint with a competent supervisory authority, including the Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP), without prejudice to other available remedies. Where processing is based on consent, you may withdraw that consent at any time without affecting processing lawfully carried out before withdrawal. We will respond to rights requests according to applicable legal deadlines.
18. Security
DirectBeam uses safeguards appropriate to its functions, including temporary session tokens, permission-based access, transfer validation, integrity checks, local-session controls and encryption for supported Android-to-Android Secure Transport V6 sessions.
No method of electronic transmission, device storage or network communication is completely risk-free. Security also depends on:
- the security and integrity of each participating device;
- the network used;
- the recipient selected by the user;
- whether the QR code, address or session token is kept private;
- operating-system and browser behavior;
- whether important files are independently backed up.
19. International processing
Google and other third-party service providers may process technical information in countries other than your own. Their processing is governed by their respective privacy terms, contractual measures and legally required safeguards.
20. Children’s privacy
DirectBeam is a general file-transfer utility and is not directed to children under 13 or the minimum digital-consent age applicable in the user’s country. Children should use the app only with appropriate parental or guardian supervision where required.
We do not knowingly operate a DirectBeam account system for collecting children’s names, profiles or passwords. If you believe that information was submitted directly to us by a child through a support communication, contact us so that the matter can be reviewed.
21. External platforms and trademarks
Android, Google Play, Google Mobile Ads and related marks are trademarks of Google LLC. Apple, iPhone, iPad, Mac and Safari are trademarks of Apple Inc. DirectBeam is independent and is not endorsed or sponsored by Apple Inc. or Google LLC.
22. Changes to this Privacy Policy
We may update this Privacy Policy when application functions, SDKs, permissions, service providers, security models or legal requirements change. The updated version will be published on this page with a revised effective or last-updated date.
23. Contact and legal controller
Privacy questions, legal requests or support enquiries: quizfans.studio@gmail.com.
Legal publisher and data controller: Laurențiu Iancu, independent developer publishing under the public name Quiz Fans Studio, Romania.