Privacy Policy
This policy describes the information, purposes, access model and contact options involved in the current Remit.ee web upload flow. No-account upload does not mean private storage or zero technical logging.
Last updated: September 13, 2026
Information we may process
When you upload a file, the service receives the file you submit and the filename, extension, size, declared type and detected type needed to process and audit it. For images, the system may also read dimensions and generate a SHA-256 digest.
To prevent abuse and troubleshoot failures, the server may record upload time, IP or network endpoint, User-Agent, Referer, Origin, language, request identifiers, and proxy or edge-network metadata when available.
The site loads Google Analytics, stat.st, Google AdSense and related consent-management scripts. These services may use cookies or similar technologies to process usage and advertising information under their own policies.
How information is used
This information is used to receive, validate, process, store and serve file links, and to apply rate limits, concurrency controls, abuse prevention, troubleshooting, service analytics, advertising and responses to reports or legal requests.
Upload audit information may be sent with the file to the storage infrastructure configured for the current deployment so that storage, operations and content handling can work.
File access, retention and deletion
Generated direct and preview links are not password-protected resources by default. Anyone who has a link may be able to access the file; HTTPS protects data in transit but does not provide access control. Do not upload passwords, keys, identity documents or other confidential material.
The service does not promise permanent file retention or permanent link availability. Service rules, storage failures, maintenance, abuse handling or other operational reasons may restrict or remove access. Temporary request files are cleaned up after processing, but that does not mean stored files are automatically deleted.
Third-party services
The current code uses the configured cloud storage service for uploads; the production deployment uses the Telegram Bot API as its file-storage channel. The site also uses Google advertising, consent-management and analytics services, plus the stat.st usage script. Third parties may process related data in their own systems under their own policies and settings.
Your choices and contact
You can choose not to upload sensitive material and can manage some cookie and advertising preferences through your browser or third-party service settings. Blocking advertising or analytics scripts does not withdraw the server-side request information needed for upload security and troubleshooting.
For a privacy question, file report or request under applicable law, provide enough information to help locate the relevant file or request. Because the current upload flow does not require an account, we may be unable to identify or complete a request without a link or other identifying context.