Klipo is preparing for launch. This page lists the policies that are still being written, and the facts we can already confirm from how the product works today.
Drafts. The legal documents linked here are published for review and are not in force yet, so nothing on this page is a contract, a legal commitment or a guarantee.
Visit records don’t contain visitors’ IP addresses. To count unique visitors, Klipo keeps a one-way hash made with a random key that is replaced every day.
For each visit Klipo records the time, the country, the website the visit came from (the site only, not the full page address), the device type, operating system and browser, and whether it came from an in-app browser.
Link-preview bots (for example WhatsApp or Slack previews) are marked as bots and left out of all statistics.
Reports: the network part of the reporter's IP address is kept for 30 days at most, and resolved reports are deleted after 90 days.
From the dashboard you can download all your data as a JSON file and delete your account (confirmed by e-mail).
Terms of service
being drafted · legal review pending
The terms of use are being written and will be reviewed before they apply.
Every destination is checked when a link is created or edited: links to private networks, to Klipo itself or to blocked domains are refused.
Klipo can disable a link that breaks the rules; a disabled link shows a notice instead of redirecting.
When people on 3 different networks report a link within 24 hours, visitors see a warning page first. Only a Klipo administrator can block a link, and the owner is told why by e-mail.
Klipo uses no advertising or analytics cookies: only a sign-in cookie and, for links made without an account, a claim cookie that page scripts cannot read.
Report abuse
facts from the current product
Report a harmful link at klipo.eu/report. A short check runs in your browser instead of a tracking captcha, and only the network part of your IP address is kept, for 30 days at most.
Passwords are stored only as salted one-way hashes, and sign-in sessions use HttpOnly cookies that page scripts cannot read.
API keys are stored as hashes, shown only once when created, and can be limited to read-only access.
A link made without an account can only be attached to an account with a secret kept in an HttpOnly cookie in the browser that made it; knowing the short link is not enough.
Short links are never cached: every visit checks the link's current destination and safety status.
Changing a link's destination or creating an API key sends a security e-mail; a destination change can be undone from that e-mail for 24 hours.
Analytics & data retention
facts from the current product
What is true today
In Klipo’s current configuration, individual visit records are deleted in monthly batches once they are more than 90 days old; daily totals per link are kept longer.
Links are kept for about 10 years under the current configuration.
Self-hosted installations can set both periods themselves.
Short-link redirect pages carry no ads and no third-party trackers.
Service status
not published yet
There is no public status page yet. Klipo will not show uptime figures until real monitoring data is published.
Self-hosting
not published yet
Klipo is built to run on your own server with Docker Compose (the app, PostgreSQL, Redis and nginx). The public setup guide and the source-code location have not been published yet.