Privacy policy
This page is a template and has not been reviewed by a lawyer. It is not legal advice. The operator of this service should review it before relying on it.
This page explains what personal data Waypoint at dev.wayp.one handles, why, and how long it keeps it. We collect what the service needs to work and nothing more.
What we collect
Account data
- Your email address and display name.
- If you sign in with Google, GitHub or Apple, the profile details that provider shares with us (the account identifier, email, name and picture). We do not receive your provider password.
- Your workspace memberships and roles.
Sessions
When you sign in we store a session record: a hash of the session token (never the token itself), the device and browser from your user agent, and when it was created and last used. You can see and end your sessions on the account page. A session ends after 30 days without use.
Content you create
Links, tags, collections, domains, API key names and prefixes (not the secrets, which are stored as hashes), and invitations you send.
Click data
When someone opens a short link, we record the time, the country (from the network edge), the device type, browser, operating system, the referring website's host name, and whether it looks like a bot. We also record which of the link's destinations the visitor was sent to. We do not store the visitor's IP address. Raw click records are kept for 400 days. Daily totals derived from them are kept for as long as the link exists.
Reports
If you report a link we store the link, your reason, any details and the email address you choose to give. Reports are kept while we review them and for a reasonable period after.
Logs and network data
Your IP address is used briefly in memory to rate limit sign-in, link creation, reports, and password attempts on protected links, and is not stored by the application. The server and the network providers in front of it may keep their own access logs.
Cookies and local storage
We use one cookie that you cannot do without: a session cookie that keeps you signed in (HttpOnly, SameSite Lax). During sign in with Google, GitHub or Apple a short-lived cookie holds the sign-in state for up to ten minutes. The mobile app keeps its sign-in tokens in the device's secure storage, not in cookies. We use no advertising or analytics cookies.
A short link sets no cookie unless its owner turned on one of two features, and then sets one strictly necessary cookie for that link, valid only on that link's address, holding no identifier of you:
wp_ab_followed by the link number, on a link that splits visitors between destinations (an A/B test). It holds which destination you were given, so you get the same one on your next visit, and lasts 30 days.wp_unlock_followed by the link number, on a password-protected link, after you enter the right password. It holds a signed expiry time, so you are not asked again, and lasts 24 hours.
Your browser's local storage remembers your theme and your last workspace, and stays on your device.
How we use it
To run the service: sign you in, show your links and statistics, send sign-in and invitation emails, enforce limits, protect the service from abuse and spam, and respond to reports. We do not sell personal data.
Who processes it
- Our hosting provider and network or CDN provider, who handle traffic and store the data.
- An email delivery provider, when configured, for sign-in and notification emails.
- Google, GitHub and Apple, only if you choose to sign in with them.
- Google Safe Browsing, when enabled, which receives link destinations you save so they can be checked for malware and phishing.
Your choices
- Access and portability. Download your account data as JSON from the account page. Export a workspace's links as CSV from the links page.
- Correction. Edit your name on the account page.
- Deletion. Delete your account from the account page. This removes your profile, sign-in methods, sessions and memberships, and the workspaces you alone own. Links you created in workspaces owned by others stay there with your name removed. Audit records of administrative actions are kept without personal details beyond an internal identifier.
Security
Tokens are stored as hashes, connections use HTTPS, and access to data is limited to what the service needs. No system is perfectly secure, so please use a strong email account.
Changes
We may update this page. The date at the top shows the latest version.
Contact
Privacy questions or requests: [email protected].