Trust
What is actually enforced.
This page describes checks in the running app. It is not an audit report. Questions go to hello@ug.uy.
- 01
Destination checks
New links are refused when the URL fails the app safety check. When Google Web Risk is configured, it must also clear the destination for malware, social engineering, and unwanted software. When that check is not configured, creation continues.
- 02
Link passwords
A password is stored as a salted PBKDF2-SHA256 hash (100,000 iterations). The password itself is not stored. Visitors submit it to a public unlock step before the redirect. Remove password deletes the hash.
- 03
API keys
A uguy_ secret is shown once. The database keeps a SHA-256 hash, a prefix, scopes, and whether the key is revoked. Authorization uses Bearer uguy_…
- 04
Click records
Analytics stores country, device class, browser, OS, language, referrer host, UTM fields, variant, click or scan, and a short daily visitor key. That key is an HMAC of the day and IP. The raw IP is not written into the click record. Cloudflare still sees the connection IP while it delivers the redirect.
- 05
Accounts and teams
Sign-in is Firebase Authentication. Team invites are bound to an email address, expire after 14 days, and only work for that email. Roles are owner, admin, editor, and analyst.
- 06
What this page does not claim
ug.uy does not publish a SOC 2 report, an uptime SLA, or a self-serve SSO switch. Enterprise lists SSO as a plan flag. It is not a control you can turn on in the dashboard today.
Collection and retention are in the privacy policy. Rules for destinations are in acceptable use.