Short memory, on purpose
Privacy
Last updated: [Date]
A zap is built to disappear. The file stays only long enough to be collected, then its timer ends. Running that brief trip still creates some data. This policy explains what exists, why it exists, and when it leaves.
The quick read
We keep files only for their live zap window, collect the operational data needed to run and defend the service, do not sell personal information, and do not build advertising profiles from your zaps.
Data a zap creates
The file. The upload itself, stored temporarily so the zap link can deliver it. The file is deleted when the zap expires or is removed.
Zap details. Filename, size, type, transfer ID, creation and expiration timestamps, and any note attached to an incoming file request.
Network and security data. IP address, browser and device details, request events, and security logs used to operate, measure, troubleshoot, and protect zappp.
Payment details. Stripe handles card information. We receive payment confirmation and limited billing details, not your complete card number.
Messages you send us. Support email and the context needed to answer it.
While a zap is live
Files move over encrypted HTTPS/TLS connections and wait in Cloudflare R2 until the zap ends. Access is scoped to operating and protecting the service. We do not use file contents for advertising or model training. Automated malware or abuse checks may inspect zaps for safety.
When the timer ends, the file is removed from active storage. Residual data in caches, backups, or logs is cleared on a limited rolling schedule. Deletion is permanent; a faded zap cannot be restored.
What we do not do
We do not sell personal information, hand files to advertisers, require a profile, or track you across unrelated sites. zappp is not “completely anonymous”: an online service necessarily processes technical data such as IP addresses.
Cookies and measurement
We use only service-essential storage and limited aggregate measurement needed to understand whether zappp works, such as total zap volume. We do not use third-party advertising cookies.
Who powers the trip
Cloudflare delivers the site, runs the Worker, and stores live zaps through Pages, Workers, and R2. Stripe processes payments. They process only the information required for their role and operate under their own privacy and security commitments.
How long things stay
Files remain until the zap expires, then are deleted. Zap metadata may remain for a limited period for security, abuse prevention, and troubleshooting. Security logs follow a limited rolling window. Payment records stay as long as accounting or law requires. Support messages stay as long as needed to resolve and reference the conversation.
Law, safety, and bad actors
We may preserve or disclose data when we reasonably believe law requires it, including a valid legal order, or when necessary to investigate abuse, prevent harm, or protect users, the public, or zappp. Because zaps fade quickly, there may be nothing left to provide by the time a request arrives.
Your choices
No account means no profile to manage. To request early removal of a zap or exercise a privacy right available in your region, email [Support Email] and include the link or ID if available.
Children
zappp is not directed to children, and we do not knowingly collect their personal information. Contact us if you believe a child has used the service in a way that requires attention.
When this changes
We will update the date above and call out material changes. Questions go to [Support Email].