Privacy Policy

01What we store and why

• Ticket payloads: Titles, links, code snippets, notes, expiration timestamps, and read counters. Stored in relational MySQL storage solely to fulfill temporary retrieval by holders of the pickup code.
• Password hashes: When you optionally protect a ticket with a password, a salted scrypt hash (N=16384, r=8, p=1) is stored with a 16-byte random salt. The plaintext password is never saved or logged.
• Transient abuse-prevention keys: Coarse request timestamps derived from client IP addresses, held in transient Node process memory for at most 15 minutes to prevent denial-of-service and brute-force attacks.
• Administrative session tokens: Authorized administrators who sign in to the private management portal receive an essential, signed HMAC-SHA256 session cookie. Public visitors browsing or retrieving tickets do not receive session cookies.

02What we do not collect from public users

• No public accounts: We do not require or collect your name, phone number, physical address, or account credentials to create or retrieve tickets.
• No cross-site tracking tags: We do not embed session-replay tools, invasive analytics tags, or behavioral trackers in the ticket composer or retrieval interface.
• No permanent logs of ticket contents: Once a ticket expires or is burned early, its payload is deleted from our database tables.

03Data retention and deletion schedules

Tickets are purged at their expiration timestamp (1 hour, 24 hours, 7 days, or 30 days). Subsequent retrieval requests receive an explicit 410 Gone status.

Password-protected tickets can be burned early by anyone possessing the valid ticket password, emptying the payload immediately prior to row expiration.

Infrastructure database backups rotate on a 7-day rolling window, ensuring residual backup copies of expired payloads are systematically overwritten.

04Third-party advertising & Google AdSense

When advertising is enabled on public sections of Sharelinknow, third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites on the Internet.

Google's use of advertising cookies enables it and its partners to serve ads to users based on their visits to this site and/or other sites across the web.

Users may opt out of personalized advertising by visiting Google Ads Settings (https://www.google.com/settings/ads) or by visiting http://www.aboutads.info/choices/ to opt out of a third-party vendor's use of cookies for personalized advertising.

For detailed information on cookie categories and consent frameworks in the European Economic Area (EEA), UK, and Switzerland, please review our Cookie Policy at /legal/cookies.

05External links and third-party infrastructure

We do not sell, rent, or trade user data. Infrastructure hosting providers process data solely under data-processing agreements to deliver server execution and database persistence.

Links bundled inside tickets are displayed to recipients; clicking an external link directs you to a third-party destination governed by that third party's own privacy policy.

06Your rights and contact procedures

Because Sharelinknow operates without accounts, ticket data is not linked to personal identity profiles. To remove a password-protected ticket early, open the ticket using your code and use the 'Burn' action.

For emergency data removal requests, privacy inquiries, or questions regarding endpoint logging, please submit an inquiry via our Contact page at /contact under the 'Privacy & Data Removal' category.