Privacy Policy

This page explains what personal data UrlsTree collects, why, and what your choices are. It covers both UrlsTree account holders ("creators") and people who visit a UrlsTree page or short link ("visitors").

1. Data we collect from creators

When you create an UrlsTree account, we collect:

• Name, username, and email address
• Your password, stored hashed — we never see or store it in plain text
• If you sign in with Google: your Google account's unique id, and the name and email address Google shares — nothing else from your Google account is read or stored for sign-in
• Anything you add to your profile: bio, avatar image, links, social icons, and appearance settings
• Billing information, handled entirely by Stripe (see Section 4) — UrlsTree does not store your card details
• Renewal reminders: on a yearly plan we note which renewal we have already emailed you about, so you get one email a week before each renewal.
• Suspension records: if we act on a report about your page, we keep what we found, the message we sent you, the dates of the notice and of any suspension, and which of our staff acted, so you can appeal and we can show what happened. They are deleted with your account.

Set up with AI. When you describe your business to Set up with AI — on the home page or in the dashboard — the text is sent to Google's Gemini API to draft your page; when you are signed in, the request also carries the titles and web-address domains of the links already on your page and which social icons it has, so the draft does not repeat them. Google processes it under its API terms. We don't log or store the text itself, only its length. What comes back is a draft: nothing is saved to your page until you review and apply it. A draft made on the home page before you have an account (never the description) is kept for 24 hours under a random token, then with your account’s setup until you apply or discard it — at most 7 days.

2. Data we collect from visitors

When someone visits your UrlsTree page, clicks a link, or uses one of your short links, we record a page view or click event containing:

• The referring website's domain, if any (e.g. instagram.com)
• Country, derived from the network request when available — we do not store IP addresses
• Device type (mobile, tablet, desktop) for short links, derived from the browser's user agent
• Timestamp

This aggregated data is shown to the page owner as analytics. We don't use it to build advertising profiles or sell it to third parties.

If a creator enables email capture or an email-gated link, and a visitor chooses to submit their email address, that address is stored as a subscriber of that creator's account and is visible to that creator. UrlsTree does not use subscriber email addresses for its own marketing.

If a creator offers bookings and a visitor books a time, we store the visitor's name, email address, optional phone number and notes, chosen timezone, and the appointment time. That information belongs to the creator (the booking is between the visitor and the creator, not UrlsTree), is shown to the creator in their dashboard, and is also added to the creator's subscriber list. We use the visitor's email only to send the confirmation, an optional reminder, and cancellation notices for that booking; each email includes a link the visitor can use to cancel. Booking data is deleted with the creator's account.

Google Calendar (optional, creators only). A creator can connect their Google account so that times they are busy stop being bookable and each booking is added to a calendar UrlsTree creates in their Google account. We request the minimum Google permissions for that: reading free/busy status (whether a time is busy — never event titles, descriptions, guests or locations), reading the list of calendars, and creating and managing events only in the calendar we created. Google access tokens are stored encrypted and used solely to provide this feature. UrlsTree’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Disconnecting in the dashboard revokes our access and deletes the tokens; you can also revoke access from your Google account’s security settings at any time.

3. Cookies

These are the cookies used on our own site and on UrlsTree pages. The essential ones keep the site working and are set without asking; Google Analytics cookies are set only after you accept them in our cookie banner.

• urlstree_session — the session cookie, essential: keeps you signed in and, on public profile pages, remembers which email-gated links you've already unlocked during your visit. It expires 720 hours after your last visit.
• XSRF-TOKEN — essential: protects forms against requests forged by other websites. It expires 720 hours after your last visit.
• remember_web_… — only if you tick “Remember me” when signing in: keeps you signed in on that device for 400 days, or until you log out.
• lang — the language you picked, kept for 1 year.
• sidebar:state — whether the dashboard sidebar is open, kept for 7 days.
• ft When you arrive on our own site from a campaign link or another website, a first-party cookie remembers for 90 days which link or site brought you here (never your IP address or browser details); it is read once if you create an account, so we know which of our channels work, and it is never shared with third parties.
• tz — on booking pages only: the timezone name you picked, so slots keep showing in your local time, kept for 30 days.
• booking_preview — only while a creator previews their own booking page, for 1 hour.
• consent — your Google Analytics choice: kept for 12 months if you accept, 6 months if you decline.
• pixel_consent — on a creator's public page only: whether you allowed that creator's own analytics and ad pixels, kept for 12 months if you allow, 6 months if you decline.
• Cloudflare Turnstile — only when you ask the home page for another AI draft after a first one (in the same visit, or from the same connection within a day): a check that the request comes from a person, which may set Cloudflare’s own cookies. See Cloudflare’s privacy policy.
• crisp-client/… — only when our support chat is switched on: functional cookies set by Crisp's chat script so a conversation carries on across pages and visits. How long they last is set by Crisp; see Crisp's privacy policy.
• _ga, _ga_* — Google Analytics, set by Google only after you accept, for up to 2 years (Google's default). They are used on our own site — the home and other marketing pages, sign-up and sign-in, the dashboard, and the page shown for a name nobody has claimed yet — to see, in aggregate, how people find and use UrlsTree. Google Analytics is not loaded on creators' public pages or booking pages. We don't use advertising cookies, and Google's advertising storage stays denied.

Changing your choice. Use “Cookie settings” at the bottom of our pages, in Settings → Your data, or here: Cookie settings. If you decline after accepting, we stop sending anything to Google Analytics and delete its cookies from your browser where we can. You can also clear cookies in your browser at any time.

If a creator adds their own Meta Pixel, Google Analytics, Google Ads, TikTok or Pinterest ID to their page (a paid feature), those pixels load only after you allow them on the banner shown on that page; until then, nothing is sent to those services. Once allowed, their own cookies and data practices apply — that's between the visitor, the creator, and that third party, not UrlsTree.

We also keep our own log of product events: what happened in the product, such as an account being created, a page going live, a page's link being copied or shared, or a plan being upgraded. It sets no cookies of its own and does not depend on your Google Analytics choice. It holds no IP address, no browser details and nothing you typed. It is kept for 180 days, included in your data export, and deleted with your account.

4. Third parties we use

• Stripe — processes subscription payments; UrlsTree is the seller. Stripe collects and processes your card details directly, under its own privacy policy. Their privacy policy
• Amazon S3 — stores uploaded profile images.
• Our email provider — sends transactional email (password resets, account notifications). We do not send marketing email without your consent.
• Cloudflare (where applicable) — provides network-level security and the country signal described in Section 2.
• Google (Gemini API) (when you use Set up with AI) — drafts a page from the description you type, as described in Section 1.
• Cloudflare Turnstile (when you ask the home page for another AI draft after a first one) — checks that the request comes from a person. Cloudflare receives the signals its check needs, such as your IP address and browser details, under Cloudflare's privacy policy.
• Crisp (when our support chat is switched on) — the support chat on our own site and in the dashboard, never on creators' pages or booking pages. It receives what you write in the chat and, if you are signed in, your name, email address, username and plan, so we can answer you; it sets its own cookies (Section 3). See Crisp's privacy policy.

5. Data retention

We keep account and profile data for as long as your account is active. If you delete your account, your profile and links are removed; aggregated analytics tied to a deleted account are also deleted. For 90 days after deletion we keep only your username and your short-link names, so nobody else can take them, and the address you moved to if you gave one, shown as a link on your old page; then they are deleted too. Suspended accounts are withheld from public view but not deleted, so the action is reversible.

If you used a free month of Pro, we keep a one-way hash of your email after you delete your account, so the free month is only used once.

6. Your rights

You can access, correct, or export your own account data from your dashboard at any time. You can delete your account from account settings, which removes your public page and profile data. To request deletion of visitor-level data we hold about you (for example, as a subscriber on someone else's page), contact us at the address below.

7. Children's privacy

UrlsTree is not directed at children under 13, and we don't knowingly collect personal data from them.

8. Bookings in Thailand: LINE, PromptPay and PDPA

When a visitor books with a creator, that creator is the data controller of the booking under Thailand’s Personal Data Protection Act B.E. 2562 (2019), and UrlsTree is a data processor acting on their instructions. For creators’ own accounts, UrlsTree is the controller.

• LINE: if a visitor signs in or books with LINE, we keep their LINE user id and display name to send that booking’s messages. We do not request their LINE email or phone, and do not keep the sign-in token.
• PromptPay deposits go straight from the visitor to the creator’s bank account. We keep the deposit status and reference — never bank details or transfer slips.
• Orders: when a visitor buys a creator’s product on their page, we keep the buyer’s name, email, optional phone, delivery address and note, what they ordered, the reference and the order’s status. The PromptPay payment goes straight from the buyer to the creator — UrlsTree never receives or processes it. The order belongs to the creator, is kept until they delete their account (or the buyer has their details erased, which keeps only the reference, status and amount), and is in their data export.
• Deposit rules: when a creator uses late and no-show rules, each booking keeps a copy of the rule and deposit the visitor agreed to, when they agreed, and what the creator later decided (kept, refunded or turned into credit).
• Deposit credit: when a deposit is turned into credit, we keep the visitor’s name and the email or LINE account it belongs to, the amount and what is left, when it expires, and a random link token that lets them use it. The creator’s data export includes the credit but never the token; withdrawing consent erases it.
• Reminder delivery: for each booking we record whether its reminder was sent by email or LINE, when, why one failed, and the message id our email provider returned, so the creator can see that it arrived.
• Consent: notes and answers a visitor types may include health details, which are sensitive data. When a creator asks for consent, each booking records when explicit consent was given and which wording version. The visitor can withdraw it from their booking link, which deletes their name, contact details, notes and answers from that creator’s records and cancels their upcoming bookings.
• Sub-processors: LINE Corporation when LINE is used, Google when a creator connects a calendar, Google (Gemini) when you use Set up with AI, and Cloudflare (Turnstile) to check that a home-page draft request comes from a person. Data may be processed outside Thailand under appropriate safeguards (Section 28).
• Your rights: access, rectification, erasure, objection, portability, withdrawal of consent, and the right to complain to the Personal Data Protection Committee (PDPC). For booking data, contact the creator you booked with first, or write to us. We answer within 30 days.
• Breach notification: if a data breach is likely to affect your rights, we notify the creators concerned and the PDPC within 72 hours as the law requires.

9. Changes to this policy

We may update this policy from time to time. We'll update the "Last updated" date above when we do. Material changes will be communicated to account holders by email or an in-app notice.