URIlock Back to homepage

Privacy Policy

Last updated: November 5, 2026

This policy describes the information URIlock handles, based on how the service currently works.

Creator account data

When you create an account we handle your email address and password through our authentication provider, PostgreSQL. Content you create, such as lockers, bio pages, landing pages, requirements, and destination links, is stored in our PostgreSQL database.

Plan status emails

When you purchase a one-time paid plan upgrade, you agree to receive email updates about your account and plan status. This may include notices about the upgrade and its 30-day expiry or automatic downgrade. We use your account email address and plan status to provide these updates.

Visitor sessions

When a visitor opens a content locker, URIlock sets a browser cookie containing a random session token. Only a hash of that token is stored on our servers. It is used to remember which unlock requirements that visitor has confirmed for that locker.

Self-confirmed actions

When a visitor confirms an action, the confirmation is saved against their session. URIlock does not independently verify the action on the third-party platform.

Analytics

URIlock records locker activity and public page views so creators can see traffic and engagement in their dashboard.

Third-party services

Visitors who open a creator’s links leave URIlock and are subject to the privacy practices of those sites. Creators may connect a YouTube account for features that use it.

Contact

Privacy questions can be sent to admin@urilock.com.

Owner to confirm

[Owner to confirm: exactly which analytics fields are stored (for example IP address, device, or referrer), data retention periods, how users can request deletion, security and compliance statements (such as GDPR or CCPA), and the data controller’s legal identity.]