Snapy ("Snapy", the "service") lets you upload a document or page and get a shareable, tracked link. Every upload requires an account with a verified email address: you confirm your address once with a short code, and nothing can be published before that. Snapy does not accept anonymous uploads of any file type. This Privacy Policy explains what information Snapy handles and how. By using Snapy, you agree to this policy.
Information Snapy collects
Snapy is built to collect as little as possible, but not so little that an upload cannot be traced back to the person who made it. Uploading requires a verified email address, confirmed once with a short code; there is no password to create. When you use the service, Snapy may handle:
- Files you upload. The content of any file, page, or project you upload, in order to store it and serve it from your link.
- File metadata. The file name, size, type, and the time of upload.
- A device identifier. A random identifier stored in your browser (in local storage) so Snapy can apply fair usage limits per device. It is not tied to your name or email.
- IP address. Collected with each upload to help prevent abuse and apply rate limits.
- Basic technical data. Standard request information such as browser type (user agent) and timestamps, used for security and reliability.
Snapy asks for your email address once, when you verify it, so that every upload is traceable to a real account and abuse can be acted on. It does not ask for your name, and no payment details are needed to upload.
How Snapy uses this information
- To store your file and serve it from the link you create.
- To prevent abuse, spam, and misuse, and to apply per-device usage limits.
- To keep the service secure, reliable, and working as intended.
- To understand overall usage in aggregate so the service can be improved.
Snapy does not sell your information, and does not use it for advertising.
Cookies and local storage
Snapy uses your browser's local storage to keep the random device identifier described above. The service is delivered through Cloudflare, which may set its own cookies for security and performance. Snapy does not use tracking or advertising cookies.
Who can open your link
A Snapy link is unlisted, not public. Links are never listed, browsed, or searchable on Snapy: there is no public directory of what people upload. Hosted content is served with noindex by default, so it stays out of search results unless you deliberately choose to make a page indexable.
Unlisted is not the same as protected. On an unprotected link, anyone who has the address can open it, so treat the address itself as the key. Where that is not enough, a link can be restricted before you share it:
- a password;
- an email gate, so a reader identifies themselves before the document opens;
- view-only, which serves the document without a download;
- an expiry date, after which the link stops working;
- a one-time link, which is destroyed after it is opened once.
Do not share anything confidential on an unprotected link.
Service providers
Snapy stores files and serves traffic using Cloudflare (storage and content delivery). These providers process data only to provide hosting and delivery for the service. Snapy does not share your information with third parties for their own marketing.
Accounts and payments
An account with a verified email address is required before anything can be uploaded, so that every link can be traced to someone if it is abused. Snapy collects the email address you give, in order to contact you, manage your account, send the open alerts and reports you ask for, and act on abuse reports. If and when paid plans go live, payments are handled by a third-party payment processor, and Snapy does not store your full card details. You can ask Snapy to delete your account and its email at any time using the contact page.
Data retention and removal
Files and their metadata are kept so your links keep working. You can request removal of a file or link at any time by contacting the address below, or through the report page if a link should not be public. Snapy may also remove content that breaks the Terms of Service.
Security
Traffic is served over HTTPS. Uploaded projects are served from a separate address space so user content is isolated from the main site. No method of storage or transmission is completely secure, so Snapy cannot guarantee absolute security.
Children
Snapy is not directed to children under 13, and it does not knowingly collect information from children.
Changes to this policy
This policy may be updated from time to time. Material changes will be reflected by the "last updated" date at the top of this page.
Contact
For privacy questions or to request removal of content, see the contact page or the report abuse page.