Privacy Policy

The controller is Wassermann Media s.r.o., Vojtěšská 211/6, 110 00 Prague 1, Czech Republic, Company ID 09938842. Send privacy questions and requests to info@souborovna.cz.

For a registered account we process your email address, a password hash (never the password itself), an optional name or company name, your plan and purchase status, sign-in sessions (in the app a secure token valid for up to 90 days and the device name; on the web a revocable session for up to 30 days, an approximate browser/system label, creation and last-use times), email notification preferences and security records of account changes. To link App Store and Google Play purchases to your account we use a random account identifier, not your Apple ID or Google Account.

We process uploaded files and their metadata: name, type, size, a content hash, owner, chosen validity, password (as a hash only), download limit and aggregate view and download counts. We create previews and playable versions of videos and photos; the original is never modified. Content is not publicly indexed. The file hash is also used to block repeatedly uploaded prohibited content.

A recipient does not need an account. When a transfer is opened or downloaded, we process the IP address needed for delivery and abuse prevention; download and report records store only a cryptographic hash of it and browser information. For password-protected transfers the browser keeps a verification cookie for 1 hour. A client uploading through a “Request files” link delivers the files to the folder owner, who receives an email notification with the file name.

When you open someone else's transfer while signed in, we remember which transfer you opened and when, so you can find it in your Received list. Only you can see this record; the sender is not told about it. The transfer disappears from the list when it expires or the sender deletes it, and you can remove it yourself.

Without an account, only your device (the app or the browser) remembers the transfers you opened: the link and when you opened it. When you view the list, the device sends them to the server only to check that the transfers are still available; without an account the server does not store them. When you sign in to the app, transfers opened on that device are added to your Received list.

For plan limits we record how much data a sender uploaded per month and how much was delivered from their transfers to recipients (in aggregate, without recording who downloaded or played them). For uploads without an account we use a hash of the IP address for the daily limit and delete it within two months at the latest.

Ads shown with transfers are not personalised: we do not use your data to select or target them, and we use no advertising cookies or third-party tracking tools. Tapping an ad's button takes you to the advertiser's site, where its own policy applies. For transfers with the sender's own campaign we record aggregate statistics (views, plays, clicks, downloads) with a random identifier for this visit so that the sender can see the results of the campaign.

• The app contains no third-party advertising or analytics SDKs and does not track you across other companies' apps or websites.
• It sends only the files you select (the system photo picker without access to your whole library, files, or the Share extension).
• It asks for add-only Photos access only when you choose to save a downloaded item.
• It stores the sign-in token in the secure Keychain and temporarily keeps files on the device to resume an interrupted upload.
• Notifications are local and are requested only after you confirm.

• Android uses the same account, server transfers, plans, Received history and data processing described above.
• It uploads only files you select through the system photo or file picker or Share action. Uploading does not require access to the whole photo library.
• The sign-in token and settings are kept in app-private storage. Selected files may be stored temporarily on the device to resume uploads; a background service with a notification can continue the transfer.
• Saving downloaded media uses the system media store. Android 8–9 requests write permission when saving. Notifications can be managed in app and system settings.
• The app contains no third-party advertising or analytics SDKs. Advertising and aggregate server statistics follow the description above. Visits and screen measurement

For resuming uploads, the browser uses selected file names and sizes, transfer status and resulting links for up to 24 hours since the last save; old local records are removed when the queue is next loaded. File contents and passwords are not stored in browser local storage. Incomplete server chunks are removed after 24 hours of inactivity.

We measure website usage with self-hosted Umami to produce aggregate usage statistics and improve the service. The legal basis is our legitimate interest in these statistics. Measurement is enabled by default, without a dialog. It uses no cookies or persistent device identifier and is not linked to your account.

We process the IP address and browser information when a web request arrives. We do not store the IP address itself in analytics; we use a temporary technical visit hash and general browser, operating system and approximate location information. Private transfer links are replaced with an anonymous path template without the transfer identifier. We do not send transfer contents, file names, email addresses or account and file identifiers to analytics.

From the web and server-side app requests, we record uploads, upload errors, sharing by creating a link, transfer opening, registration, sign-in, page publication, purchases and language changes for aggregate counts. Server-side action records contain no user identity. We distinguish web, iOS and Android when the platform can be recognised; otherwise it remains unknown. Action data is limited to predefined categories, such as file-size and file-count bands or the payment channel, without the purchase amount.

In the iPhone and iPad app from version 2.3.2 and the Android app from version 2.4.1, we also measure visits and screens that are actually displayed. We send the iOS or Android platform, app version, language, event type, screen category and the reason a visit starts (launch or return to the foreground); the server assigns the receipt time. Screens use a closed set of categories: home, upload, files, received transfers, sharing, billing, settings, authentication and other. Screen contents, custom screen names, links and file or transfer paths are not sent.

On launch and each return to the foreground, the app creates a new random technical visit reference. The app keeps this reference and unsent events only in memory; they are not saved to disk and are lost when the process ends. This is not an account, device, installation or advertising identifier, and we do not use it to link different visits. It is sent to our server to group the events of one visit into aggregate counts. Native statistics do not store the IP address or browser information; the server uses the IP for request delivery and short-term abuse prevention.

Visits, screen views and aggregate server-side app actions are measured by default. You may request that measurement be disabled by emailing info@souborovna.cz. These statistics contain no user identity or persistent account, device or installation identifier. You may object to processing based on legitimate interests under Article 21 GDPR by contacting info@souborovna.cz.

Individual pageview and event records are kept for 90 days and daily aggregate counts for 13 months. The Souborovna operator is the controller; we run Umami ourselves and do not disclose these statistics to third parties.

We respect Do Not Track (DNT: 1) and opting out in this browser: Disable measurement in this browser. Opting out stores only the local umami.disabled preference, without an identifier or cookies, until you clear this site's browser data. If local storage is unavailable, measurement is disabled at least for the current page. This choice applies to this browser, not to other browsers or apps. It does not restrict access to the service.

Purchases in the iPhone and iPad app are processed by Apple; we receive only transaction data from Apple (identifier, product, status and validity period). Purchases in the Android app from Google Play are processed by Google Play; we receive only subscription data from Google (purchase token, order number, product, status, country of purchase and validity period). Card payments on the website are processed by Stripe; we record customer and transaction identifiers, subscription status, amounts and payment status. For bank transfers we record the payment reference and amount. We never store card numbers.

For content reports we process the reporter's contact details (if provided), reason, description, link, status and a record of actions taken; for sender blocking, the link between the two accounts. We use email for account verification, password reset, notifications you turn on, support replies, and notifications about report outcomes and reasons for restrictions. We also record complaints, human reviews, outcomes, prior warnings and proportionate restrictions for repeated violations.

• performance of the contract — account, transfers, purchases and support,
• legitimate interests — security, abuse prevention, moderation, campaign statistics for senders and service usage measurement,
• legal obligations — accounting and cooperation with authorities where required by law.

We run the service on our own servers in the Czech Republic (including backups). We also use Cloudflare (DNS and website protection), Stripe (card payments on the website), Apple and Google (in-app purchases); emails are sent from our own mail server. These providers may process data outside the EU on the basis of standard contractual clauses or the EU–US Data Privacy Framework. We do not sell personal data.

• files and previews until the chosen validity ends or the transfer is deleted, then access is disabled and automatic cleanup removes content and derived versions, retrying failures. They may remain in operational backups for a limited time until overwritten.
• the account until it is deleted; app sign-in sessions for up to 90 days and web sessions for up to 30 days; revoked sessions are kept until expiry to prevent replay,
• records of received transfers you opened until the account is deleted,
• payment and accounting records for the period required by law,
• reports, enforcement actions and security records for as long as needed to handle them and prevent repeated abuse.

You have the right to access, rectify and erase your data, to restrict processing, to data portability and to object. You can delete your account and data on the web in Settings → Account deletion, in the app (Account → Delete Account and Data) or by emailing info@souborovna.cz. You may lodge a complaint with the Czech Office for Personal Data Protection (www.uoou.cz) or your local data protection authority. Only a person older than 15 may create an account. App stores may apply a higher age rating or target age group.

Related: Terms of Service, Cookies, Security.

We are the controller for account management and service operations. When a business stores content containing other people's personal data, it is the controller for that content and we process it under the Data Processing Agreement.

Completed account-deletion jobs are deleted 30 days after completion. Resolved monitoring incidents are kept for up to 90 days after resolution; open incidents remain until resolved, with at most 200 incidents in the history. Web-server logs are rotated daily with 14 archives alongside the active log. These periods do not imply the same retention for all moderation or application records.