Rootline Privacy Policy
Rootline is a family tree app made by Devs Gallery (Md. Kabir Uddin, sole proprietor, trading as Devs Gallery; see Contact). This policy explains what happens to the information you put into Rootline, who else handles it, and for how long it is kept.
In short: without an account, your trees stay on your phone and nothing about you or them is sent to us or anyone else. With an account, the trees you share are kept on Rootline's own server so your family can use them, and a few service providers handle what they need to send a code, a message or a payment. Rootline doesn't sell your family's data, shows no ads, and uses no analytics or crash-reporting service.
Part A. On your phone, without an account
This part covers the app without an account, and any tree you keep only on your phone.
What Rootline keeps
What you type or bring in: names, dates, places, relationships, facts, notes, sources, research to-dos, and any photos, scans, recordings or documents you add. Also your settings, such as the app's language and text size.
Where it is kept
- Only on your phone, in Rootline's own private storage, which other apps cannot read.
- Encrypted. Your family tree is kept in an encrypted database, and photos and other files you add are encrypted too. The keys are held in your phone's Android Keystore.
- Not in Android backups. Rootline switches off Android's cloud backup and device-to-device transfer for its data, so your tree does not go into your Google account's backup.
- Hidden from Recents. On Android 13 and later Rootline's card in Recents is blank. On older versions the app also blocks screenshots while a tree is open, unless you allow them in Settings.
- Your keyboard is asked not to learn what you type about people, so it does not suggest a relative's name in another app.
Photos, scans and recordings
- When you add a photo, Rootline takes out its location and other hidden details, keeping only what draws the picture, which way up it goes, and the date it was taken. Sound and video keep only the recording itself.
- A PDF is kept as it is, with anything inside it.
- Rootline asks to use the camera only when you start scanning, and the microphone only when you start recording. It never asks for your location. You can refuse or withdraw these permissions in your phone's settings.
What goes over the network without an account
Rootline has Android's permission to use the internet, which accounts need. Without an account it sends nothing about you or your tree. It only asks Rootline's own server for what every phone gets alike: which ways of signing in are open, the dates of the published Terms and Privacy Policy, the plans' figures, and map tiles while you look at the map (Part B, "The map"). These requests carry no name, tree, account or device identifier. The server sees your network address, uses it in memory to slow down abuse, and does not store it.
Rootline uses no analytics, crash-reporting or advertising service, and no advertising ID. Firebase, which only carries push signals, starts only once you sign in (Part B, "Notifications"). We do not receive a copy of a tree you keep on your phone, and we cannot see, recover or delete it for you. Rootline shows no ads and does not sell your data.
When something leaves your phone
Information leaves your phone only when you choose to send it, for example when you:
- save or share a GEDCOM or GEDZIP file of your tree. It leaves out living people, children, and anyone you made private, so it is not a full copy;
- print a chart, or save or share a chart or a profile card. These leave out living people and children too, apart from a card of yourself;
- print a home poster, which shows only the living adults you choose by name, and never a child;
- share a photo from your tree. Rootline sends a new copy, drawn again with no hidden details;
- save your research log as a spreadsheet file;
- save a full backup of a tree you made. It holds everything, sealed with a recovery key that Rootline shows you once, and it needs your phone's screen lock first. Without the key nobody can open it, us included.
You pick where each file goes, using your phone's own file picker or share sheet. Once a file is in another app or service, that app's or service's own terms and privacy policy apply to it.
While a large import or export runs, Android may show that Rootline is working. That notice names nobody.
Google Play
You install and update Rootline through Google Play, and Google's privacy policy covers that.
- Rootline's plan pages ask the Google Play app on your phone which plans are on sale and at what price; to answer, the Google Play app may contact Google. Buying a plan needs an account (Part B, "Payments").
- Google Play may add a check to the app that confirms it was installed from Google Play. Google runs that check, under Google's privacy policy.
- If you have allowed your phone to share usage and diagnostics information with Google, Android may report app crashes to Google, and Google may show Devs Gallery summaries of them. That is a setting of your phone, covered by Google's privacy policy. Rootline itself sends nothing.
Children
Rootline is made for adults. A family tree can include children that you add. Their details stay on your phone like everything else, and every file, print, card or poster Rootline makes leaves children out, apart from a full backup.
Deleting your information
- Inside the app you can change details and remove facts. A record's History keeps earlier versions for 30 days, and lets you delete them for good sooner.
- You can delete a person. They go to Recently deleted, where you can bring them back for at least 30 days. After that, or once you choose Delete for good, they are gone.
- A tree you just imported can be removed with Undo import. Rootline keeps a sealed copy of the file you imported for 30 days, and deletes it sooner if you delete anything in that tree for good.
- A tree kept only on this phone can be deleted from Me, after you type a word to confirm. It is deleted at once, and cannot be brought back. (A tree kept on the server is deleted as Part B says.)
- To delete everything, uninstall Rootline, or open your phone's Settings, then Apps, then Rootline, then Storage, and clear its storage. This removes your trees, photos and settings from the phone, together with the keys that open them. It cannot be undone, and we cannot recover anything, because we never had a copy.
- Files you saved or shared before (GEDCOM files, charts, cards, posters, backups) are not removed by this. Delete them where you saved them.
Part B. With an account
This part applies once you make an account.
Who runs it, and who else handles your information
Rootline's server is run by Devs Gallery on its own hardware in Bangladesh.
Who is responsible. Devs Gallery is the controller of the information Rootline's server holds: it decides what happens to that information and answers for it. Write to us at rootline@devs.gallery, or to the postal address under Contact.
Your information is kept there and on your own devices, and nowhere else. There are no off-site backups yet. Before there are, this policy will name the provider and the country, and say that those backups are encrypted and kept no longer than the server's own.
These service providers handle only what they need:
| Who | What they receive | Why |
|---|---|---|
| Resend (email) | Your email address and the message: a sign-in code, a security notice, or an invite link (and, once guardian consent opens, a consent request to a parent or guardian) | To deliver email |
| Twilio (text messages), only where sign-in by text is turned on | Your phone number and a sign-in code. Only numbers starting +880 | To deliver sign-in codes |
| Google Firebase Cloud Messaging, from your first sign-in | Your device's push token and a Firebase installation id; a signal that says only "pull", with no content, and when it reached the device; and what Firebase's own requests show (below, "Notifications") | To wake the app so it fetches changes |
| Google Play and Google Cloud Pub/Sub | Google handles your purchases. We receive from Google the subscription's product, state and dates for a purchase token, and Pub/Sub carries Play's notices of a change to us | To sell and check plans |
| Google sign-in, if you choose it | Google tells us an identifier for you and your Google account's email address. We keep only a keyed hash of the identifier; the email address joins your account only after you enter a code we send to it, and then is kept like any email address. We keep no name or picture | To let you sign in |
| Apple sign-in, only where it is turned on | Apple tells us an identifier for you; we keep only a keyed hash of it | To let you sign in |
Messages are in English. They never name a family tree, a person or who invited you. What each provider keeps is set by its own privacy policy, and each handles this for us under its own data-processing terms. Resend, Twilio and Google may process it in the United States and in other countries where they work.
The map's tiles come from Rootline's own server, made from OpenStreetMap data. No other company is asked.
We use no analytics, no advertising and no crash-reporting service, and we do not sell personal data or use family data for ads.
What the server keeps about your account
- Your sign-in ways. Your email address or phone number is kept as a keyed hash, which cannot be read back, and as a short mask such as l•••@example.com or +880••••••78. Each email address is also kept encrypted, only so that security notices can reach it. A phone number is not.
- Passkeys: the public key and dates, and no name. Google or Apple: a keyed hash of their identifier for you.
- Your age group (13 to 17, or adult), and for a teen the date they become an adult. Never your year of birth.
- The terms you agreed to: which version of the Terms of service was in effect when you made your account, and when. Nothing, for an account made while no terms were published.
- Sessions: how you signed in, whether from Android, iOS or the web, and when. No device name, network address or browser details.
- Devices for notifications: each device's push token, encrypted.
- Sign-in events: what was tried, whether it worked, and when, including wrong codes. No network address. Each is kept a year.
- Limits: to slow down guessing, keyed hashes of an address and of your network, deleted within 2 days. Your network address itself is never stored.
- Purchases: a keyed hash and an encrypted copy of Google Play's purchase token, the product, its state and dates, and a random tag we give Google Play in place of your account. No price, card or order number. Each purchase is kept until 30 days after it ends.
- Family seats: for a Family payer and each holder, the seat's start and end and why it ended, and the seat codes' keyed hashes and times. Ids and times only. An ended seat is deleted 30 days after it ended, and a seat code a day after its 7 days end.
- A close you asked for, and the asks before it.
What the server keeps about trees you share
- The tree itself, exactly as your devices send it: records, families, notes and sources, and the history of edits. It is not end-to-end encrypted: it is stored as written, and the server's disk is not encrypted; backups are. The people who run the server can technically read it. Only Devs Gallery's operator does, and only when it is needed to run, repair, secure or restore the service, or to act on a report, an appeal or a request you make; never to browse a family's tree.
- Tree history. At most once a day the server keeps a point of each tree it holds: the records that changed since the last point. Points are kept 30 days, or a year while the tree's Owner is on Plus or Family; past 30 days they go at the first daily clean-up after that plan ends. Only the Owner can restore a point, which makes a new tree that they own with only what they may see now, without files, comments, members or history. What a person removes or replaces in their own record, or a guardian in their ward's, leaves the history at once, and so does a record that a removal request or report holds.
- What a member removes or replaces is kept sealed for 30 days, so a keeper can bring it back, and then deleted, apart from the tree's history above. A removal request inside those days can keep it up to about 60. Nobody else can read it meanwhile.
- Photos and other files. The server keeps only its own clean copy of each upload, and deletes the bytes as sent:
- JPEG and PNG pictures are drawn again, with no hidden details, location or date. Your phone turns WebP, HEIF and AVIF pictures into JPEG before sending.
- Sound and video keep only the recording: their tags are blanked and their dates zeroed. They are not re-encoded, so anything inside the recording itself stays.
- A PDF is kept as you uploaded it, and only you can open it.
- For each file the server also keeps who uploaded it, its type, size and dates, and which records show it. No file name, caption or location.
- A file no record shows any more is sealed at once, so nobody can open it, and deleted 30 days later. Files cannot be brought back.
- Members and their roles, invites, joins, comments, requests for more access, reports, removal requests, and consent for cards.
- A record of acts in the tree (who joined, changed a role, approved a change, added or opened a file), with the account, the kind of device and the app's version, and at most one entry a day for each file a member opens. Never the words of an edit.
Who sees what in a shared tree
- Your role decides. The tree's Owner and Admins (its keepers) see the most. Editors, Branch editors and Contributors see living adults in full. A Viewer sees no more than a name and a birth year of anyone who may be alive.
- Living people are those with no recorded death who were born within the tree's limit (110 years unless the tree says otherwise). Someone with no dates is judged from their relatives, and counted as living when that cannot tell.
- Children under 18 never appear in a view-only link or in search, whoever is signed in, and no export, print, card or poster shows them.
- A privacy setting on a record narrows who sees it to keepers. A lock you put on your own record hides it from everyone else, keepers included.
- To someone not allowed to see a person, that person looks exactly as if they did not exist.
- When you leave, what you added stays in the tree, credited to "A former member". Keepers who can see the person you were linked to see "Name (former member)" for a year.
- Keepers see an activity list of joins, role changes, suggestions and files added, for a year. It holds no one's words.
- Comments are seen only by members who can see the whole record.
- A shared copy on a phone closes (it is hidden, not deleted) if the phone has not reached the server for 90 days. Losing access to a tree deletes your phone's copy of it at the next sync.
Children and teens
- Under 13: no account. If the year you give says under 13, the year you typed never leaves the phone, and the server deletes every code and count for your address at once. Nothing about you stays.
- 13 to 17: the account is made, but it cannot join or see any family tree until a parent or guardian agrees by a link Rootline emails them. Rootline does not send these emails yet, so for now such an account stays shut to every family tree; what follows is how it works once it opens. The guardian's email address is kept encrypted only until the email has gone, and at most 30 days if it cannot be sent. We record the answer and when, never the guardian's name or address. A parent or guardian can withdraw consent, which shuts the account at once and starts closing it.
- Inside a tree, a member aged 13 to 17 only ever has a Viewer's seat, has no tree of their own on the server, cannot ask for more access, is linked to no person in the tree, and is nobody's guardian. They cannot hold or give a Family seat.
- From 1 January of the year you surely turn 18, your account is an adult's.
- These ages are the same in every country. Where a law sets an age between 13 and 16 below which a parent or guardian must agree, as in the European Union and the United Kingdom, the guardian's agreement covers it, because every account under 18 needs it.
View-only links
A keeper can make a link that lets anyone holding it read part of a tree on the web, with no account. A link shows only people who have died, and nobody narrowed or locked: no living person, no child, and no notes, photos or private details. It ends on the day the keeper chose (30 days at most, one at a time, on a tree whose Owner is on Free; 90 days on Plus or Family), or when that keeper leaves the tree or stops being a keeper. Anyone the link is forwarded to can open it. Each day's first view is recorded for keepers, without saying who opened it. Once a link has ended, keepers see it in their list for 30 days, and then it is deleted.
Reporting
- Any member can report a person's record, a memory, a source, a note or someone's comment, for a reason: an incorrect fact, harm, privacy, impersonation or copyright, with optional words of their own.
- Who sent a report is stored but never shown to keepers, support or anyone else. Your own words are shown to the keepers, and may identify you; in a tree with 5 members or fewer, Rootline warns you before you send.
- Keepers see reports from the next day. Reports about harm, impersonation or copyright, and any you choose to send to support, are also seen by Rootline's support, who see the report and the ids of what it is about, and nothing else in the tree.
- How long: an open report ends after about 30 days. Its words are deleted when it closes, and the report itself 90 days after that. Where support hid a record because of a report, the report is kept while the record is, without who sent it after 90 days. The record of decisions on reports is kept for a year.
- Your own reports are in your data download.
Removal requests
- A member can ask the keepers to remove their own record, or someone else's, from a shared tree. While the request waits, the record is private: keepers can still read it, but it leaves by no export, link, card or print, and strangers' search cannot find it.
- Keepers decide: remove the record, keep it private, decline with a reason, or dismiss it as not genuine. If they do not answer in 30 days, it stays private. A removed record is kept sealed for 30 days, and a keeper who brings it back within them brings it back private. A record its person has locked cannot be removed until they open it.
- If your request is declined or dismissed, you can appeal to support within 90 days of the keepers' answer, and support can make that record private for good.
- How long: a request, your words and the keepers' reason are kept 90 days after the keepers answer (or after the 30 days run out), and then deleted. Where the request keeps a record private, that much of it stays as long as the tree keeps that record, without your words, the keepers' reason or who asked.
- Without an account, write to rootline@devs.gallery. Support cannot read or search trees, so it cannot say whether a tree holds you; it tells you how a member of that family can ask the keepers, and answers within one month.
Rootline's support
Support works only from the server's own machine, never through the internet. Through Rootline's own tools, support sees only a report, a removal request or an appeal, the keepers' reason, and the ids of the records concerned, never the rest of the tree or who reported. From the day after a report is made, support can make the reported record private or take down the reported comment, and support can make an appealed record private. Support cannot reopen a closed account or recover what it held. Write to rootline@devs.gallery.
Notifications
When something changes in a tree you share, Rootline's server may send your device a signal through Google Firebase Cloud Messaging. The signal says only "pull": no name, tree or content. Push starts only once you sign in. From then, Google learns your device's push token, a Firebase installation id, when the device was signalled, and what any connection to it shows: your IP address, the app's package and version, your device model, the versions of Android and Google Play services, and the days the app started push. Each signal waits a random few minutes first. Your phone then fetches the change from Rootline directly. The signal itself shows nothing on your phone; what changed appears on the app's own Notifications page. The choices in the app's notification settings decide what that page shows; they do not stop the signal while you are signed in. A device's token is deleted when its session ends, after at most one day more for a last signal, and when you sign out the phone asks the server to forget it at once.
Payments
Plans are sold by Google Play. Google handles the payment, and we never see your card. We check each purchase with Google, and Google tells us when it renews, lapses, is refunded or is cancelled. We keep what is listed above under "Purchases". A free trial is Google Play's: Google decides who may have one.
Family seats. A Family payer sees each seat holder's masked sign-in (such as r•••@gmail.com) and the day the seat began, and a holder sees the payer's. Each sees the storage they share as one total, rounded up to a gibibyte, and never the other's trees, files or own share. A seat gives no access to anyone's trees.
The map
When you place a fact on the map, your phone asks Rootline's server for map tiles. A tile request shows roughly which area you are looking at, together with your network address, which the server uses for a limit in memory and does not store. Tiles are kept on your phone, and deleted when you lose access to the tree, switch accounts, or delete something for good. Rootline never asks for your location; a place is pinned only where you drop the pin.
Web pages
Rootline's own web pages (the public site, guardian consent, closing an account, view-only links, and the pages a join or seat link opens without the app) use no cookies, scripts or anything from another site, and no analytics; their fonts and pictures come from Rootline's server. They are in English and Bangla, by your browser's language or your choice. A page whose address holds a code never reads the code, and is kept out of search engines and caches.
Logs
The server's logs hold codes, route names, results and times: no name, address, network address, account or tree. They are kept up to 8 days. The proxy in front of the server keeps no access log. Its error log holds a line when a request fails or is too slow, with the network address and the address asked for, and is kept about a day, up to 2; it writes no line for view-only links, guardian consent, join and seat links, or map tiles. The database does not log what it is asked.
Backups
The server is backed up every day. Backups are encrypted and kept on the server's own disk for 14 days; each photo or file is copied into them once, encrypted, and leaves them when the last backup that holds it ages out. So anything deleted is gone from them within about 16 days. There are no off-site backups yet; any we add will keep to the same days.
How long things are kept
| What | How long |
|---|---|
| A sign-in code | 15 minutes (email) or 10 minutes (text) |
| Counts used for limits | Up to 2 days |
| A session | Until you sign out, 90 days unused, or a year at most; its record 30 days after it ends |
| A device's push token | Until its session ends, plus up to 1 day |
| Your encrypted email address, for notices | Until you remove that address or close the account |
| Sign-in events | 1 year |
| Your account (with the terms it agreed to), sign-in hashes and masks, and passkeys, after you close the account | 1 year after the close, or until 30 days after its last purchase ends if that is later, and not before the close has finished in every tree it was in; until then the same address or number cannot make a new account |
| Purchase records | Until 30 days after the purchase ends; a refund marker 400 days |
| A guardian's email address | Until the consent email has gone, at most 30 days |
| A guardian's answer | A yes or a withdrawal, while the account's records exist (after a close, as the row above); a no, 30 days; no answer, until the link ends (7 days) |
| A shared tree's records, history and comments | As long as the tree exists, or until deleted |
| What a member removes or replaces | 30 days, sealed (up to about 60 with a removal request), apart from tree history |
| Tree history points | 30 days, or a year while the tree's Owner is on Plus or Family; a person's own removals leave at once |
| A Family seat | While it lasts; 30 days after it ends |
| A Family seat code | Until a day after it ends (it works 7 days at most) |
| A removed file | 30 days, sealed; an upload never finished, 1 day |
| The record of acts in a tree, and keepers' activity list | 1 year |
| A former member's name, shown to keepers | 1 year |
| Reports | About 30 days open, then 90 days closed; words deleted at close |
| A removal request, with its words and the keepers' reason | 90 days after the keepers answer; one that keeps a record private stays as long as the tree keeps that record, without its words, the reason or who asked |
| A request for access (without its words) | 30 days after it is answered, withdrawn or ends |
| A comment that was deleted (without its text) | 1 year after it was deleted |
| A view-only link that ended | 30 days after it ended |
| A card's consent | Until withdrawn; then 30 days |
| Invites | Until they end, 30 days at most |
| A deleted tree | 30 days on hold, then destroyed; gone from backups about 16 days later; a record that it was deleted, 1 year |
| Server logs | Up to 8 days |
| Backups | 14 days |
Your choices
- Download your data. In the app, after a fresh sign-in, you can save a file of what your account holds: your ways of signing in (as masks), passkeys, sessions, devices, purchases, your age group and any guardian's consent, the terms you agreed to, your close, your sign-in events, and for each tree your role, your own acts, your removal requests and your reports. Trees you own leave through the app's own export.
- Close your account. A close waits 7 days, or 14 if your only way in is a mailbox, and any sign-in cancels it. When it runs, your sessions, devices and encrypted addresses are deleted, your invites are revoked, your Family seats end, and your name leaves every tree. What you added to shared trees stays in them. As the server is set now, a closed account's email address or number cannot make a new account for a year after the close, or until 30 days after its last purchase ends if that is later; then the account's last records are deleted, and it can. You need a fresh sign-in that is not a text code: an account with only a phone number must add an email address, a passkey, or Google or Apple first. An email-only account can also be closed from Rootline's website with an emailed code.
- Delete a tree you own. It is held 30 days, every member is told in the app, and you can cancel until it ends. Then it is destroyed, with its files.
- Lock your own record, ask for a removal, or report something, as above.
- Your rights. Wherever you live, you can download, correct and delete what your account holds with the choices above. If you live in the European Union, the European Economic Area or the United Kingdom, data protection law (the GDPR and the UK GDPR) also gives you the right to ask for a copy of your information, to have it corrected or erased, to restrict or object to how we use it, to take it with you, and to withdraw a consent at any time. Other countries' laws may give you rights too, and you keep them. To use a right that the app does not cover, write to us (see Contact); we answer within one month. You can also complain to a data protection supervisory authority, such as the one where you live or work; in the United Kingdom, that is the Information Commissioner's Office (ICO).
- Why we may use it (for the GDPR and the UK GDPR). To run the account and the trees you share, as our agreement with you (the Terms of Use) needs. To keep the service secure and stop abuse, such as the sign-in limits and the security notices, in our legitimate interest and yours. A guardian's consent for a teen, and a living adult's consent for a card, as consent. Purchase records, to give you the plan you paid for, as our agreement needs. What you add about relatives is yours to add; section 4 of the Terms asks you to add only what you have a fair reason to record.
Security
Connections to Rootline's server are encrypted. Each tree's data is kept apart in the database, every read is checked against your role, and sign-in codes, tokens and addresses are kept only as hashes, encrypted, or masked. Backups are encrypted. No system is perfectly secure. If a breach of security puts your information at risk, we tell you by email and in the app without undue delay, and we tell the authorities where a law requires it (for the GDPR, within 72 hours of learning of it).
Information across borders
Rootline's server is in Bangladesh, so when you use an account from another country, what your devices send goes to Bangladesh. If you are in the European Union, the European Economic Area or the United Kingdom, your information is transferred from there to Rootline's server in Bangladesh. Neither the European Commission nor the United Kingdom has found that Bangladesh's law protects personal data to their standard, and we use no other safeguard, such as standard contractual clauses, for this move. It happens because the service you ask for runs there: an account and shared trees cannot work without it. Resend, Twilio and Google handle what the table above says in their own countries, under their own terms. Where the GDPR or the UK GDPR asks for a safeguard when they move information abroad, they use the standard contractual clauses in their data-processing terms.
Changes to this policy
We will update this policy before a version of Rootline changes what happens to your information, and the date above will change. If a change affects account holders, we tell them in the app at least 30 days before it takes effect, unless a law or a security problem needs it sooner, and then the notice says which. While you are signed in, the app shows the day the new version takes effect and a link to it, until you close the notice. Closing it is remembered on that phone, by the version alone.
Contact
Devs Gallery (Md. Kabir Uddin, sole proprietor, trading as Devs Gallery)
Postal address: Sonnasirchok, Kaliganj, Satkhira 9421, Bangladesh
Email: rootline@devs.gallery