Tirly Privacy Policy
Effective date: November 5, 2026
Tirly ("the app," "we," "us") is developed by Raye Technology LLC. There
is an Android app and an iPhone app, and this policy covers both. It
explains what information Tirly collects, what stays on your phone, what
reaches our servers, who else processes it, and how to delete it. Where
the two apps differ, this policy says "Android" or "iPhone"; everything
else is true of both.
Summary
Tirly blocks apps you choose according to rules you write: while a
friend is nearby, at certain times, after a number of opens or minutes,
or at a place you name. Whether a friend is nearby is decided between the
two phones over Bluetooth and a short high-pitched chirp, never by our
servers. Your account holds your phone number, the name you give
yourself, who your friends are, a copy of your rules so they survive a
reinstall, your Tirly Pro standing and, if you share a Pro plan, who you
shared it with. On Android it also holds your daily screen-time totals
for the friends leaderboard and whether you have chosen to be on it; on
iPhone no screen-time figure leaves the phone. We show no ads, use no
analytics or crash-reporting SDKs, and never sell your information.
Information We Collect
Account
- Phone number. You sign in with a one-time code sent
by SMS through Twilio. Your number, as you typed it, goes to our server
and to Twilio to send that code, and we store it on your account. It is
your account: it is how you sign back in, how friends find you, and how
we identify you when you contact support. We also keep a hashed form of
it, which is what the app compares your contacts against. On Android,
Google Play services reads the sign-in text message on your phone so the
code fills itself; for that, the app sends our server a short code
identifying its own build, which Twilio appends to the message.
- Name. Tirly asks for a name at sign-in and requires
one. It is sent to our servers and shown to people you have sent a
friend request to, people you are friends with, everyone in a Tirly
with you (including someone waiting to be let in, whether or not you
are friends), friends told that you started a Tirly nearby, the people
you seat on a shared Pro plan and the owner of a plan you are seated
on, and the friend who earns a reward because you subscribed. Nobody
else can read it. You can change it from the Account tab. It stays on
the account when you sign out, so you are not asked again; deleting the
account deletes it.
- Sign-in token. A random credential that keeps the
app signed in. Signing out or signing in on another phone revokes it.
On iPhone it is kept in the Keychain on that phone only and is never
synced to iCloud.
- Friend code. A random code of your own that your
friend link and its QR code carry, so that somebody who scans or taps
it can send you a friend request. It names nobody on its own.
- The date you signed up, and the platform your phone
runs, Android or iPhone. The platform decides the shape of a
push message and which features your account is offered; nothing else
about the handset is stored.
- Whether you have taken the in-app tour, one yes or
no, so a new phone does not walk you through the app a second time.
- Who invited you, if you signed up through a
friend's invite link or a Tirly affiliate's code (see Invites and Tirly
Pro).
Contacts
- With your permission, the app reads your address book to show you
which contacts already use Tirly and to put names on your friends. It
sends a hashed form of each phone number to our server for matching. We
match those against our accounts and do not keep them. Contact names
never leave your phone. The app keeps a copy of your address book on
the phone as hashed numbers with the names beside them, marked with
which ones are on Tirly, so the list does not have to be rebuilt each
time you open the app; it is excluded from backup on both
platforms.
- One exception: when you pick a contact to share a Tirly Pro plan
with, that person's phone number itself is sent to us, so we can seat
them; we store only its hashed form (see Tirly Pro).
- Inviting a contact who is not on Tirly prepares a text message for
you to send from your own messaging app. Nothing about that person is
sent to us. The message carries an invite link; when somebody signs up
through it, our server adds one to your invite count and records that
the new account claimed an invite. When you sign up through a friend's
invite, Tirly remembers who invited you so they can be rewarded when
you subscribe, and when you do, they are told the name you gave Tirly
and nothing else about you; the link between you is deleted with your
account.
Friends
- A friendship is a row on our server holding the two accounts, its
status (pending, active or removed), timestamps, and one random key
from each phone. The two phones use those keys to recognise each
other's Bluetooth signal. The keys are held so a reinstalled phone can
recognise its friends again.
- Either person can remove a friendship at any time. The row is kept
marked as removed, with its keys cleared, so that the two of you can
become friends again later. Once removed, neither of you can read the
other's name or keys.
- A friend request by phone reveals your name to the person asked. It
reveals nothing about them to you until they accept.
Rules
- The rules you write are evaluated on your phone. A copy of them is
also saved to your account so they come back after a reinstall or a new
phone. That copy contains everything a rule is: the name you gave it,
what triggers it, the friend it names (as the hashed number their phone
is recognised by), the schedule, the allowance, how long an unlock
opens it for, and, for a location rule, the address you typed and the
coordinates and radius of that place. Which apps it covers is recorded
differently on the two platforms. On Android the copy
lists the apps by their package names. On iPhone the
apps and websites you pick come from Apple's own picker as opaque
tokens, which the copy stores exactly as Apple hands them, with a count
of apps, categories and websites; they name no app to us, and we could
not read them if we tried.
- Our server stores that document as a whole and does not read or act
on it while the app runs. It is replaced each time your phone saves.
Once, in October 2026, we rewrote every stored document to add a
default for a new setting; nothing was read out of them.
- Asking a friend's permission to open a blocked app sends our server
what the app is, how many minutes you asked for, which of your own
rules asked (a number that means something only on your phone), who you
asked, and their answer, so the request can reach them and their answer
can reach you. On Android the app is named by its
package name and its label. On iPhone Apple's tokens
cannot be turned into a name, so what is sent is a code derived from
the token that names no app, together with the name you gave the rule,
or nothing. A request stops counting for anything after five minutes:
it is kept until it expires, then deleted.
- Whether a block is in force, and which apps you open, stays on your
phone. The two places an app is named to us are the ones above: an app
you ask a friend's permission to open (on Android), and the apps a rule
covers in the copy of your rules (on Android).
How blocking works on each platform
- Android. Tirly reads which app is in the
foreground through Android's Usage Access and draws its block screen
over it with the "Display over other apps" permission. Neither reading
is sent anywhere. Tirly can also block a rule's websites in your
browser and count time on them toward a time or open limit. That uses
an Android accessibility service which reads only the address bar of
the browser in front, only while one of your rules covers a website,
and compares it with the rule on your phone. No address or browsing
history is stored or sent anywhere; the only record kept is the minutes
and visits counted against your own limits, on the phone and excluded
from backup.
- iPhone. Tirly blocks apps with Apple's Screen Time
frameworks (Family Controls, Managed Settings and Device Activity). You
pick the apps and websites in Apple's picker, Apple draws the block
screen, and Tirly's extensions put a quote and Tirly's buttons on it.
Tirly never learns the names of the apps you pick: Apple hands the app
an opaque token for each one, and only Apple's own screens can turn it
into a name. Your screen time (the score on Home, the History page and
the Account tab's screen-time tile) is calculated and drawn inside a
Device Activity Report extension that Apple runs in its own sandbox.
Apple keeps every usage figure inside that extension: it cannot reach
the rest of the app, let alone our servers. A rule that applies at
certain times or after a limit is scheduled through Apple's Device
Activity, on the phone.
Bluetooth and the microphone
- Friends' phones find each other over Bluetooth Low Energy using the
keys above. What is on the air is Tirly's own service identifier and,
from an Android phone, a short identifier derived from those keys that
changes every hour, how strongly it hears its friend, whether it is
hosting an open Tirly, which platform it runs, and whether it can
listen for the chirp. Android versions before 1.12.4 also put the air
pressure the phone reads on the air, for a survey of telling floors
apart; from 1.12.4 that is off, and only a developer build has the
switch that turns it on. It goes to your friends' phones and nowhere
else and decides nothing. An iPhone puts only the service identifier on
the air and exchanges the same card over a direct Bluetooth link. No
name, number or location is broadcast, and none of it passes through
our servers.
- To tell a friend in the room from a friend behind a wall, one phone
plays a short high-pitched chirp and the other listens for it.
This opens your microphone for about a second and a half at a
time. It happens only when you open an app that one of your
own presence rules blocks, and only while Tirly's own screen is
showing: on Android under the block screen, on iPhone after you tap the
check on Apple's block screen and Tirly opens. Your phone never listens
at a friend's request, and the app runs no background service with
microphone access. Your phone may play the chirp, from a pocket too,
when a friend beside you opens an app one of their rules blocks. The
microphone permission is needed only for a rule of your own that
applies when a friend is with you. The sound is checked on your phone
and deleted right away. It is never saved or sent: not to the other
phone, and not to us. The only thing the check produces is whether, and
how loudly, the chirp arrived, and a few numbers describing the shape
of that arrival, which go to the friend's phone over Bluetooth so the
two phones agree. On Android, playing the chirp briefly raises the
alarm volume and restores it afterwards. On iPhone the app changes no
volume; if your iPhone's volume is at zero it cannot play the chirp,
tells your friend's phone so, and that phone opens the app.
Location
- Tirly asks for location permission only when you create a rule
that applies at a place: on Android the precise, approximate and
background permissions, on iPhone "While Using" and then "Always".
Without a location rule, Tirly never asks for or reads your location.
Bluetooth scanning is declared as never used for location.
- With a location rule, your phone compares its position with the
place in the rule, on the phone. Where you are now is never sent
to us and is never written to disk; on iPhone the one thing
recorded is whether the phone was last inside or outside the place,
with the time. The place itself, as typed and as coordinates, is part
of the rule copy saved to your account (see Rules).
- Background ("Always") location lets the rule keep working while
Tirly is not on screen. Declining it keeps the rule from working and
changes nothing else.
- The address you type while making a location rule goes to a
geocoding service to become a place and to suggest completions as you
type: on Android to the phone's geocoder (Google's service on most
phones), on iPhone to Apple Maps. The map drawn around the place comes
from OpenStreetMap on Android and from Apple Maps on iPhone (see Third
Parties).
Tirly sessions
- Opening a Tirly creates a record on our server of who hosted it,
who joined, when, and when it was locked or ended. Joining one makes
you and the host friends immediately. Locking one keeps every phone in
it, the host's included, out of every app but Tirly for the length the
host chooses, from ten minutes to twenty-four hours (thirty by
default); the end of that lock is kept on each phone so it expires even
offline. The Android lock also leaves the phone app, the home screen
and Tirly reachable; on iPhone, Apple's block screen covers every app
and Apple itself keeps Phone, Tirly and the home screen reachable.
- Members are identified to each other by account and by the name
they gave themselves.
- The session record also holds two random secrets our server makes
for it, one the host's phone mints the rotating join code from, one
that carries a join through an app install, and, while somebody is
waiting to be let in, the key their phone will be recognised by once
they are. Past sessions are kept as they were; nothing reads them once
the session is over.
- Each Tirly that locked while you were in it is drawn as a star on
your Home screen. The record behind it (the session, when it locked,
and the other people in it, as the hashed numbers their phones are
recognised by and the names your phone knew them by) is a file on your
phone. It is never sent to us, it is kept when you sign out, and it is
included in your phone's backup.
Notifications
- To reach your phone while Tirly is closed, the app registers a push
address with our server, together with the platform it is for so the
message is built in the right shape. The address is a Firebase Cloud
Messaging token on both platforms; on iPhone, Google delivers the
message through Apple's push service. A push carries only a kind and an
id (on iPhone also a category and a generic title, in case the words
cannot be fetched); the words come from our server when the app, or on
iPhone its notification extension, wakes. Google and Apple learn that a
message was sent to your device and nothing about its subject. To
deliver pushes, Google assigns your installation an identifier of its
own and holds it.
Screen time
- Android. Your screen time and pickups are measured
on your phone with Usage Access. So that you and your friends can
compare, the app uploads one figure per day to our server: your total
screen time for each of the last seven complete days, with your phone's
time zone so the days line up. Nothing finer leaves the phone: no app
names, no times of day, no pickups. The board shows the last seven
days, but our server keeps every day you have ever
uploaded, one total per date; there is no schedule that
removes older ones. Only people you have accepted as friends see your
daily average, and you see theirs. You are on the board until you turn
off Show me on the leaderboard on the Account tab: that choice
is stored on your account, every total you have uploaded is deleted at
once, nothing more is uploaded, and you and your friends stop seeing
each other's figures until you turn it back on. Removing a friend
removes you from each other's board at once, and the totals are deleted
with your account.
- iPhone. No screen-time figure leaves the phone.
Apple keeps every usage figure inside the report extension described
above, the app has no way to read one, and our server refuses an upload
from an iPhone account. An iPhone account is on no leaderboard, its own
or its friends'.
Tirly Pro
- Tirly Pro is bought through the App Store on iPhone and Google Play
on Android. Apple or Google handles payment and holds your payment
details; we never see them. Purchases are managed for us by RevenueCat,
which receives your purchase from the store under a random billing
identifier we create for your account, not your phone number, name or
any identifier of the phone.
- Our server keeps your subscription standing: the plan, whether it
renews, when it expires, the store it came from, why it lapsed if it
did, any introductory offer you took, and any Pro credit a referral
reward has given you. It also keeps each purchase event
RevenueCat reports, as RevenueCat sends it: the product, the
price and currency, the store and the country the store reported,
whether it was a sandbox or a real purchase, the dates, the store's
transaction or order identifier, and the other fields RevenueCat puts
in its event. We use them to decide what the app unlocks, to share a
yearly or lifetime plan with the people you seat on your pass, and to
reward the friend who invited you. After a purchase, and from time to
time while you use the app, our server asks RevenueCat for your current
purchases under that identifier so the account and the store
agree.
- The free trial. A new account is offered three
days of Tirly Pro once. Taking it records on your account when the
trial started and ends and whether you have been told it ended. It also
writes the hashed form of your number to a record that is kept after
the account is deleted, so that deleting and re-creating an account on
the same number does not start a second free trial; that record holds
the hash and the date and nothing else, and is read for nothing
else.
- Pro codes. If you enter a code (a discount or a
gift of Pro, for example an affiliate's code), our server keeps the
code you redeemed on your account, when you redeemed it, what it gave
you and when it was used up or removed, and, if the code belongs to an
affiliate or a referrer, records them as the person who referred you,
in place of any invite link. A discount is a set of store prices, so
the store learns only which price you bought at.
- Sharing a plan. A yearly or lifetime plan can be
shared with up to five people, chosen from your friends and your
contacts. For a contact, you send us their number to seat them; for a
friend who is not in your address book, the hashed form their phone is
recognised by. We keep each seat as the hashed form, with the date you
seated them and the date you removed them. Your pass names a seat from
that person's own Tirly name, or from your address book on your own
phone. If they have a Tirly account they are told by a notification
that you seated them, with your name. A removed seat is kept, marked
removed, because it goes on counting against your five for seven days.
Seats are deleted with your account, and you can remove any of them
from the pass screen at any time. A seat that names you on
somebody else's pass is theirs: it is a hash on their pass and stays
there until they remove it, even after you delete your account.
- When a friend you invited pays for Pro, you earn a point; the first,
tenth and fiftieth points are Pro credit. Each point is a row on our
server naming you, the account whose payment earned it, when it was
earned, whether a refund took it back, which reward it was, and when and
how we applied it. If that person deletes their account the point stays
but no longer names them. For a renewing Google Play plan we apply the
reward by asking Google Play, through its developer API, to defer your
next charge; that request carries your Google purchase token and
nothing else about you. For an App Store plan, and for anyone else, the
reward is credit on your account; we make no request to Apple.
Affiliate program
If you apply to be a Tirly affiliate, from the Account tab or at
/affiliates/, you sign in on our website with
your Tirly phone number and we store on your account: the name and email
you give us, the PayPal email you want to be paid at and every change to
it, where you plan to share Tirly and to how many people, how you plan to
share it, the code you asked for, that you confirmed you are in the
United States, whether you came from the app, the version of the
affiliate agreement you accepted and when, and our decision with any note
we made on it. If we do not accept you we delete your email, PayPal
email, channels, audience, plan and requested code at once and keep your
name, the dates, the reason and the agreement you accepted, so that you
can apply again after ninety days; those are deleted with your account.
If we approve you we create your code, and from then on we store each
account whose first affiliate code was yours, one commission line per
such account (the store's event id, the plan, the price paid, the store's
share, your rate and amount, the payment and release dates, and whether
it was refunded or paid), each payout we send you (the date, the amount,
PayPal's fee, the email we sent to and PayPal's transaction id), and a
daily count of how many times your link was opened. The account that
used your code is never named to you: your dashboard shows counts, dates,
plans and amounts. We send your PayPal email and the payout amount to
PayPal when we pay you, by hand, and nothing about the people you
referred. We collect no tax form. Approval, decline and payout emails go
to the email you gave us through our email provider. The affiliate
website sets a sign-in cookie that lasts two weeks and a security cookie
that lasts a year; the sign-in record behind the cookie holds your number
and, until you finish applying, the application you have typed so
far.
Information We Do Not Collect
- Your current location, or any location history
- Audio recordings, or any audio at all
- Contact names. Your address book reaches us as hashed numbers for
matching, and we keep none of them. The one number we receive in the
clear is a contact's when you seat them on a shared Pro plan, and we
keep only its hash
- Which apps you open, or when a block engages or lifts, with two
exceptions on Android, both above: an app you ask a friend's permission
to open is named to us with the time you asked, and the apps your rules
cover are listed in the rule copy saved to your account. On iPhone
neither names an app to us
- Any screen-time figure from an iPhone
- Browsing history, message content, or the content of any app
- Advertising identifiers, analytics or crash-reporting data. Neither
app includes an analytics, crash-reporting or advertising SDK, and the
iPhone app does not ask to track you
- Your IP address. Nothing Tirly writes down holds one: our rate
limits are counted per account, and our web server keeps no access log.
Render, which hosts the servers, sees the connections to them as any
host does
What Your Phone Holds
The app keeps on the phone: your sign-in token; your friends and the
keys their phones are recognised by; your address book as hashed numbers
with names, marked with which ones are on Tirly; your rules; the time and
visits counted against a limit; your Tirly Pro standing; badges; the
current Tirly and the lock's end; the stars of past Tirlys; and, on
Android, your screen-time history, including time by app. Uninstalling
Tirly removes all of it; it does not delete your account.
- Android. Your sign-in token, your friends and
their keys, the contact list, the current Tirly, every rule and limit
record, your Pro standing, the leaderboard record, time by app and the
push registration are excluded from Android's cloud backup and
device-to-device transfer. Your screen-time history (the daily totals,
pickups and quiet stretches, and the app that was in front when it was
last measured, but not the time by app), the name you gave yourself,
your badges, the stars of past Tirlys, the count of blocks held, the
barometer readings compared with each friend on a version before
1.12.4, and whether you have asked to be an affiliate are included in
your phone's Google backup, so they are restored to a new phone.
- iPhone. Your sign-in token and number live in the
Keychain on that phone only. Your rules and everything the block screen
needs, your friends and their keys, the contact list, your Pro
standing, the current Tirly and the list of friends the notification
extension names from are excluded from iCloud and computer backups. The
name you gave yourself, your badges, the stars of past Tirlys, the push
address and a pending invite or friend code ride your backup.
Signing out forgets, on the phone, your sign-in token, your rules,
your friends and the contact list, and on Android the screen-time
history; it keeps the stars, and it keeps the fact that you have seen the
introduction, so a returning user is not walked through it again.
Links, invites and the clipboard
A friend link, a Tirly join link, an invite link and an affiliate link
open in the app when it is installed. When it is not, the page that opens
offers the store. On Android the Play Store carries the
code in the link through the install, and the app reads it once, the
first time it runs, from Google's install-referrer service; nothing else
is read from it. On iPhone the page copies a short
tirly: line to your clipboard, and the app reads your
clipboard once, the first time it runs while signed out; it accepts only
a line that starts with tirly: and clears it, and it never
reads the clipboard again.
How We Use Information
| Data | Used for |
| Phone number and its hash | Identifying your account; signing you in; letting your contacts find you; answering support requests; remembering that the free Pro trial has been used |
| Name | Naming you to friends, people you ask, people in a Tirly with you, and the people on a shared plan |
| Contact hashes | Telling you which contacts use Tirly; discarded after matching |
| Friend code | Letting somebody who scans or taps your link send you a request |
| Friendships and keys | Letting friends' phones recognise each other, and restoring that after a reinstall |
| Rules document | Restoring your rules on a new install |
| Permission asks | Carrying a question to a friend and their answer back |
| Tirly sessions | Keeping everyone in a session in agreement about who is in it |
| Push address and platform | Waking the app when something is waiting for you, in the shape your phone reads |
| Invite count | Showing you how many people joined through your link |
| Who invited you, or whose code you used | Rewarding the friend or affiliate whose invite you signed up through |
| Daily screen-time totals (Android) | Ranking you and your friends by average screen time |
| Purchase standing and events | Unlocking Tirly Pro, sharing a pass, rewarding the friend who invited you, paying an affiliate |
| Pro codes you redeemed | Giving you the discount or gift once, and restoring it on another phone |
| The people you seat on a shared Pro plan | Giving those people Pro, and showing you who is on your pass |
| Referral points | Counting what you have earned and applying it once |
| The date you joined, and your platform | Building a push message in the right shape; knowing which features your account is offered |
| Whether you have taken the in-app tour | Not playing it again on a new phone |
| Affiliate application and ledger | Deciding your application, counting what you have earned, and paying you |
We use nothing for advertising, profiling, or sale, and we do not
share information with anyone for those purposes.
Third Parties
- Twilio receives your phone number to send and
check the SMS sign-in code.
- Google Firebase Cloud Messaging delivers push
wake-ups to both apps. Google holds your device's push token and an
installation identifier of its own, and sees that a message was sent,
not what it concerns.
- Apple Push Notification service carries those
wake-ups to an iPhone. Apple sees that a message was sent, not what it
concerns.
- Google Play services (Android) reads the sign-in
text message so the code fills itself, and runs the install-referrer
and in-app review services described above.
- Android's geocoder (Google's service on most
phones) receives the address text you type while making a location
rule, to turn it into a place and to suggest completions as you
type.
- Apple Maps (iPhone) receives that address text for
the same purpose, and draws the map around the place you chose, so
Apple sees the place a rule is about.
- OpenStreetMap (Android) serves the map tiles drawn
around a place you chose, so the OpenStreetMap Foundation sees requests
for the map squares around that place, with the app's name, version and
package in the request. The squares are kept on your phone for a
week.
- App Store and Google Play process payments for
Tirly Pro and hold your payment details; we receive only the purchase
and its transaction or order identifier. For a referral reward on a
renewing Google Play plan we ask Google Play to defer your next charge.
We make no request to Apple about your account.
- RevenueCat manages Tirly Pro purchases on both
platforms. It holds your purchases under a random billing identifier
and reports them to our server; our server also asks it for your
purchases after a purchase and periodically. It never receives your
phone number or name.
- Render hosts our servers and database.
- Our email provider sends affiliate approval,
decline and payout emails to the address an affiliate gave us.
- PayPal receives an affiliate's PayPal email and
the payout amount when we pay them.
Each of these processes data to provide the service described and
under its own privacy policy. None of them receives your contacts, your
friends, your rules, or your current location.
Who Can See Your Data
- We can. Raye Technology staff with an administrator
account can read and search the database through Django's admin pages:
accounts, which they find and identify by phone number or by the name
you chose, friendships, sessions, permission asks with the app they
named, daily totals, purchase events, the seats on a pass, Pro codes
and their redemptions, affiliate applications and ledgers, and the
rules document as it is stored. We use it to run the service and to
answer support requests, and there is no other route in: the app's own
interface only ever shows an account its own data and what a friend is
meant to see.
- A change made through those pages is written to an audit log that
records what was changed and how the record was named, which for an
account is an internal identifier that names nobody. Records written
before 17 September 2026 name the account by its phone number instead.
That log has no link to the account, so deleting the account
does not delete it.
- Server logs. Our servers log faults, not traffic.
There is no request log, no analytics and no crash reporting. Three
kinds of fault can put something personal in a log line: when the SMS
provider rejects a sign-in, its error message can quote the number we
asked it to text; when Google Play rejects a referral deferral or a
cancellation, its error can quote your purchase token; and when an
affiliate email cannot be sent, the line names the address it was going
to. Render, which hosts the servers, holds those logs for a short period
under its own policy.
Data Retention & Deletion
- Your account and everything attached to it is kept while the
account exists. We run nothing that deletes old records on a
schedule, so there is no retention period to quote: a row is there until
you delete your account, or until something described below deletes
it.
- Permission asks are kept until they expire, then
deleted: five minutes after you ask, the record goes the next
time your phone or your friend's phone talks to us about asks. Friend
requests stop appearing after fourteen days; their records are
not deleted, the request is simply never shown again. Removed
friendships are likewise kept as removed, with their keys cleared. Past
Tirly sessions and, on Android, every daily total you have uploaded are
kept the same way, except that turning off Show me on the
leaderboard deletes every daily total.
- Our rate limits are enforced with a short-lived count of your recent
requests, kept for the hour it covers and keyed by your account.
- Signing out revokes your sign-in token and forgets your phone's
push address; it leaves the account, and the name on it, for your next
sign-in.
- Deleting your account, from the Account tab or as described at
/delete-account/, immediately and
permanently deletes your phone number and, unless you took the free Pro
trial, its hash, your name, the date you joined, your friendships and
keys, your rules document, asks you sent or received, push addresses,
your invite link and the record of any invite you claimed, any Pro code
you redeemed, sessions you hosted and your membership of any you
joined, every daily total and your leaderboard choice, your
subscription standing and any Pro credit, your pass and the seats on
it, your purchase record at RevenueCat, and, if you are an affiliate,
your application, code, commission lines, payouts and link counts. Your
friends' phones stop recognising yours, any rule they wrote that named
you is removed from their phone, and they are told that you deleted
Tirly.
- Seven things survive a deletion, and none of them can be used to
reach you: the count on other people's invite links,
which names nobody; purchase event records, which we
keep for our accounts and which no longer name any account; a
referral point a friend earned because you subscribed,
with your account no longer named on it; an affiliate's
commission line earned because you subscribed through
their code, likewise no longer naming you; a seat
somebody else gave you on their shared Pro plan, which is a hash on
their pass until they remove it; the administrator audit
log described above, which keeps the record of any change we
made to your account; and, if you took the free Pro trial or your
account was made before it existed, the hashed form of your
number on the record that the trial has been used, described
under Tirly Pro, so a new account on the same number is not offered
another. Accounts deleted before that record existed left none. An
affiliate's code also keeps a note of the affiliate's name after the
account is gone, so that we know whose code it was.
Children's Privacy
Tirly is not directed at children under 13 (or the relevant minimum
age in your jurisdiction), and we do not knowingly collect information
from them.
Changes to This Policy
We may update this policy as Tirly evolves. Material changes will be
reflected here with an updated effective date.
Contact
Questions about this policy or your data:
info@rayetechnology.com. The
Account tab's Feedback row opens your own email app addressed to
support@rayetechnology.com
with the app version and your phone's make, model and operating-system
version filled in; you can edit or delete any of it before sending, and
nothing is sent unless you send it. We keep support emails to answer them
and for as long as the matter is open.