This policy explains what personal data My Lineage Trees collects, why, who it is shared with, how long it is kept, and the choices and rights you have. It covers the website at mylineagetrees.com and everything you do on it (the "Service").
We wrote it in plain language. If anything is unclear, write to privacy@mylineagetrees.com.
1. Who we are
My Lineage Trees is run by SivaKumaran Murugesa Pillai, a sole proprietor based in India ("My Lineage Trees", "we", "us", "our").
| Postal address | R 206, Purva Bluemont Apartment, Singanallur, Coimbatore 641005, Tamil Nadu, India |
| Privacy questions | privacy@mylineagetrees.com |
| General support | support@mylineagetrees.com |
| Phone | +91 88259 96373 |
For personal data you give us about yourself, we are the data fiduciary under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"), and the controller under the EU and UK General Data Protection Regulation ("GDPR"). Section 6 explains the special position of information that members add about their relatives.
2. The short version
- We collect what we need to run your family tree, take payment and keep the Service safe. Nothing more.
- Family trees are private. Only people invited to a tree can see it. We never make your tree public, and we never let anyone else do so.
- We never sell your data, never use your family tree content or names for advertising, and never use it to train AI or machine-learning models.
- We never see or store your full card number, CVV, UPI PIN or bank login. Razorpay handles payment details.
- We use Google Analytics only if you agree to analytics cookies, and advertising cookies only if you also agree to those. We send marketing emails only if you opt in.
- You can see, correct, download or delete your data, and you can withdraw consent at any time.
3. What we collect
3.1 Information you give us about yourself
| Data | When | Required? |
|---|---|---|
| Name and email address | When you sign up | Yes |
| Password | Email sign-up. Google's Firebase Authentication stores it in hashed form; we never see it. | Yes, unless you use Google sign-in |
| Google profile (name, email, profile photo) | When you sign in with Google | Only if you choose Google sign-in |
| Country of residence | When you choose it in Settings → Profile | No |
| Profile photo | When you upload one | No |
| Your agreement to our Terms and this policy (version, date and time) | When you sign up, and when these documents change | Yes |
| Marketing email preference | When you choose to subscribe | No |
| Messages you send us | When you email support, privacy or the Grievance Officer | No |
3.2 Information you and other members add to family trees
Family trees hold information about people other than the account holder: living and deceased relatives, most of whom never have an account. A tree can contain:
- names, maiden names and nicknames
- gender, and whether the person is living or deceased
- birth and death dates and places
- ancestral or family place of origin
- relationships: parents, children, marriages, partnerships, separations and divorces
- photos, captions and the year a photo was taken
- biographies, written stories and life milestones (education, career, homes, migration, achievements, remembrance)
- the name of the member who added each photo or story
Some of this may reveal sensitive things, such as ethnic or regional origin, religion mentioned in a story, or health mentioned in a biography. You decide what goes in. Please add only what the family would be comfortable sharing with the tree's members. Section 6 has the rules for information about living relatives.
3.3 Information created when you use the Service
Tree membership and roles. Which trees you own or belong to, and whether you are an owner, editor or viewer.
Invitations. When you invite someone, we store:
- the recipient's email address
- your name, email address and profile photo (shown to the recipient on the invitation)
- the role offered
- any personal note
- the invitation's status and expiry date
We email the invitation to the recipient.
Activity feed. A record of changes in a tree, such as "Asha added Meena to the tree", showing the member's name.
Notifications. In-app notices about invitations, role changes and membership, and whether you have read them.
Tree positions and display settings. Where each relative sits on the canvas, and the visual theme chosen.
3.4 Payment information
Payments are processed by Razorpay Software Private Limited ("Razorpay"). You enter card, UPI or bank details directly into Razorpay's secure checkout, and they never pass through our servers. From Razorpay we receive and keep:
- your plan, its status, trial and renewal dates
- Razorpay customer and subscription identifiers
- a short label for your payment method (for example "UPI" with your UPI handle, or a card network with its last four digits)
- a record of each payment: amount, method, date, and payment and invoice identifiers
Razorpay's own privacy policy (razorpay.com/privacy) covers what Razorpay does with your payment details.
3.5 Technical information
- IP address. We use it briefly, in memory, to limit how often a request can be made (to stop abuse), and do not store it ourselves. Our hosting provider records it in server logs.
- Server logs. Google Cloud records requests and errors (time, address requested, IP address, browser type) to keep the Service running and secure.
- Analytics, only if you agree. Google Analytics 4 collects how pages are used: pages viewed, buttons used, approximate location (city or country), device and browser type, and errors seen in the app. Section 9 explains how to say yes or no.
- Advertising signals, only if you agree. A separate choice from analytics. If you turn it on, Google receives a cookie identifier along with the pages and actions above, to measure and target our own Google Ads. If you're signed in to a Google account and have allowed it in your Google settings, Google may associate this activity with that account. You can see and delete that activity in Google's My Activity. Family tree content and names are never included.
4. Why we use it, and on what legal basis
| Purpose | Data used | Legal basis (DPDP Act) | Legal basis (GDPR) |
|---|---|---|---|
| Create and secure your account, sign you in | 3.1 account data | Your consent | Performance of our contract with you |
| Run family trees: show, edit and share them with members you invite | 3.2, 3.3 | Your consent, and the instructions of the member who added the data | Contract; our legitimate interest in providing a family-history service |
| Send invitations and in-app notifications | 3.3 | Your consent | Contract |
| Take payment, run trials and renewals, keep billing records | 3.4 | Your consent; legal obligation for tax records | Contract; legal obligation |
| Send service emails: invitations, password resets, billing and renewal notices, important changes to these policies | Email, name, plan | Your consent; legitimate use | Contract; legal obligation |
| Keep the Service safe: prevent fraud and abuse, fix errors, defend legal claims | 3.5, account data | Legitimate use (s.7 DPDP Act) | Legitimate interests |
| Understand and improve the Service with analytics | 3.5 analytics data | Your consent (cookie banner) | Consent |
| Measure and target our own ads | 3.5 advertising signals | Your consent (cookie banner) | Consent |
| Marketing emails about new features and offers | Name, email | Your consent (opt-in) | Consent |
| Answer requests, complaints and legal demands | Your messages, account data | Legal obligation; legitimate use | Legal obligation; legitimate interests |
Where we rely on consent, you can withdraw it at any time (section 11). Withdrawing does not affect processing that already happened.
5. What we never do
- We never sell or rent personal data.
- The Service shows no ads. We share data for advertising only if you turn on advertising cookies: Google then receives a cookie identifier and the pages and actions described in 3.5, so we can measure and target our own Google Ads. Family tree content and names are never included.
- We never use your trees, photos or stories to train AI or machine-learning models, and we never allow anyone else to.
- We never make a member's family tree public. Only admin-curated trees in the Explore gallery are public; section 7 describes them.
6. Information about your relatives
Most people in a family tree have no account. If you add information about a living person, you must have their permission, or for a child, a parent's or guardian's, or a genuine family reason to record it. The Terms & Conditions set out this rule.
If you are in someone's tree, with or without an account, you can ask for two things:
- A correction. If something about you is wrong, we pass your request to the tree's owner, who decides whether to change it. We don't edit family details ourselves, because we can't check them and relatives sometimes remember things differently.
- Removal (living people). If you are alive and don't want to be in the tree, or you are the parent or guardian of a child in it, we first ask the tree's owner to remove or change the entry, and give them 7 days to do so. If they don't, we remove it ourselves: we delete the photos and every detail about that person, and either delete the entry or leave it as "Removed relative" so the rest of the family still connects. We tell the owner when we do.
If you have a My Lineage Trees account, sign in and send the request from our Support page, so you can follow it there. Otherwise, write to privacy@mylineagetrees.com with:
- your full name, and whether the request is about you or your child (for a child, you must be their parent or guardian)
- how you appear in the tree: the name shown (which may be a maiden name or nickname) and, if you know it, your birth year
- which tree: its name, and the owner's name or email address if you know them. A screenshot or an invite link helps us find it quickly.
- what you'd like: a correction (what is wrong and the correct details), or to be removed
We may ask you to confirm your identity before we act, so that no one can remove someone else's information. The owner can also tell us if they believe the request isn't from the person it's about. Section 12 gives our response times. We tell the tree's owner about every correction or removal request, but we share your name and email with them only if you agree.
Deceased people. Data protection laws such as the DPDP Act and GDPR protect living people, so requests about deceased relatives are passed to the tree's owner, who decides. We step in ourselves only when content breaks the law or our Terms, for example if it is defamatory or infringes someone's copyright.
Unlawful content. When content is unlawful, such as an intimate image, impersonation, defamation or a copyright infringement, we remove it without waiting for the owner, within the time the law sets (24 hours for intimate images and impersonation), whether the person is living or deceased. We tell the owner afterwards.
Children. Children can appear in a tree when an adult relative adds them. Only add a living child's details and photos if you are the child's parent or guardian, or have their permission.
7. Who can see your information
Members of the same tree. Everyone who joins a tree, whoever invited them, can see that tree's relatives, photos, stories, activity feed and member list. Editors and owners can change them. What a member can do depends on their role:
| Role | Can see the tree | Can add and edit | Can invite people | Can change roles and remove members |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes, as editors or viewers, by email or invite link | Yes |
| Editor | Yes | Yes | Yes, as editors or viewers, by email or invite link | No |
| Viewer | Yes | No | Only as viewers, by email or by sharing the tree's view-only invite link | No |
Other members can also see your name, email address and profile photo in the member list and on invitations you send.
Explore gallery. The public Explore gallery shows example trees of royal families, film dynasties and fictional or literary families. Our team curates them from publicly available sources. Members' trees never appear there.
Our team. Our team looks at your account or a tree's content only when we need to: to answer a support request you've made, to handle a complaint about a tree, to act on unlawful content, or when the law requires it. Each look is recorded.
Our service providers. We share data only as needed for them to provide their service to us, under contracts that require them to protect it:
| Provider | What they do for us | Where the data is held |
|---|---|---|
| Google (Firebase, Google Cloud) | Sign-in, database, photo storage, website hosting, server logs | Database: Mumbai, India. Photos and other uploads: Iowa, USA. Website servers: Taiwan. Sign-in and logs: Google's global infrastructure, mainly the USA. |
| Razorpay | Payments, UPI Autopay and card mandates | India |
| Amazon Web Services (Amazon SES) | Sending emails: invitations, password resets, billing and marketing emails | Sydney, Australia |
| Hostinger | Domain name, and the support and privacy mailboxes that receive your emails to us | Hostinger's data centres; Hostinger is based in the EU |
| Google Analytics (only with your consent) | Usage statistics and error reports | USA |
| Google Ads (only with your consent) | Advertising cookie identifiers and measurement of our ads | USA |
Legal reasons. We disclose information if the law, a court order or a government authority requires it. We also disclose it to protect someone's safety or to enforce our Terms.
Change of ownership. If My Lineage Trees is sold or transferred, your data moves to the new owner under this policy. We will tell you before that happens.
8. International transfers
My Lineage Trees is run from India and serves families worldwide. As the table in section 7 shows, your data is stored and processed in India, the USA, Taiwan, Australia and the EU.
Transfers out of India are allowed under section 16 of the DPDP Act. For people in the EU, UK or Switzerland, our providers protect transfers with the safeguards their laws require, such as the European Commission's Standard Contractual Clauses in Google's and Amazon's data processing terms.
9. Cookies and similar technologies
| Type | What it is | Why | Can you turn it off? |
|---|---|---|---|
| Sign-in storage | Google's Firebase Authentication saves your sign-in in your browser (IndexedDB / local storage) | Keeps you signed in | No: the Service needs it. Signing out removes it. |
| Session storage | Small notes kept only while your browser tab is open, such as a message to show after a page change or a banner you closed | Makes the app work smoothly | No; cleared when you close the tab |
| Razorpay checkout cookies | Set by Razorpay when you open the payment window | Secure payment and fraud prevention | Needed only to pay |
| Google sign-in cookies | Set by Google when you choose "Sign up with Google" | Signing in with your Google account | Needed only for Google sign-in |
Analytics cookies (_ga, _ga_*) |
Set by Google Analytics | Counting visits and understanding how the Service is used | Yes: off unless you accept them in our cookie banner. Change your choice any time from "Cookie settings" in the site footer, your account menu or Settings. |
Advertising cookies (_gcl_* and other Google advertising cookies) |
Set by Google | Measuring and targeting our own Google Ads | Yes: off unless you accept them. They need analytics on as well. Change your choice any time from "Cookie settings". |
| Firebase installation ID | Saved in your browser's storage (IndexedDB) by Google Analytics | Lets Analytics recognise the same browser | Only created if you accept analytics. Turning analytics off stops it being used, but it stays in your browser and links your activity again if you turn analytics back on. Clearing this site's data removes it. |
| Your cookie choice | Saved in your browser's local storage | Remembers what you chose, for 12 months | No: it holds only your choice |
Advertising cookies stay off unless you turn them on. Our fonts are hosted on our own servers, so loading a page doesn't contact a font provider.
10. How long we keep data
| Data | How long |
|---|---|
| Your account and profile | Until you delete your account, then deleted within 30 days |
| Trees you own | Until you delete the tree or your account (then deleted within 30 days), unless you first hand ownership to another member |
| What you added to trees owned by others | Stays in the tree as part of the shared family record, shown as from a "Former member" after you delete your account. You can ask us to remove your photos and stories. |
| Trees locked because a plan ended or lapsed | Kept, locked (nobody can open it until the plan is renewed), for as long as the owner's account exists. We never delete a tree just because a plan ended. |
| Invitations | Until accepted, declined, revoked or expired (invitations expire after 14 days), then deleted within 90 days |
| Notifications and activity feed | While the tree or account exists |
| Payment and billing records | 8 years from the end of the financial year of the payment, as Indian tax and accounting law requires, even after you delete your account |
| Server logs | About 30 days |
| Analytics data | 14 months, then deleted by Google Analytics automatically |
| Advertising cookies | Up to 90 days in your browser, or until you turn them off |
| Emails with support or the Grievance Officer | Until resolved, then up to 2 years |
| Records of your consent | While your account exists, then for as long as we might need to show the consent was given |
| Backups | Data deleted from the Service is gone from all backups within 90 days |
11. Your choices and rights
Everyone has these rights:
- Access and a copy. Ask for a summary of the personal data we hold about you and how we use it. You can download a copy yourself in Settings → Security → "Download your data": a JSON file with your account, your agreements, your plan and payments, your notifications and support requests, the stories and photos you added to other people's trees, and the trees you own. Photos are included as links rather than image files.
- Correction and completion. Fix your profile in Settings, or ask us to correct other account information. For information about you in someone's family tree, see section 6.
- Erasure. Delete your account in Settings → Security, or ask us. Some billing records are kept for the time the law requires (section 10).
- Withdraw consent. Unsubscribe from marketing emails with the link in any of them, or turn analytics or advertising off in "Cookie settings". Withdrawing consent to the Service as a whole means closing your account.
- Grievance. Complain to our Grievance Officer (section 12).
- Nominate (India). Name someone to exercise your rights if you die or can no longer act yourself.
If you are in the EU, UK or EEA, you also have the rights to:
- restrict or object to processing based on legitimate interests
- data portability
- complain to your local data protection authority
If you are in California or another US state with a privacy law, you have the right to know, access, correct and delete your personal information, and to opt out of its sale or sharing. We don't sell or share personal information, so there is nothing to opt out of. We will never treat you differently for using these rights.
How to use your rights. Use the controls in Settings, or email privacy@mylineagetrees.com from the email address on your account. We may ask you to confirm your identity. We answer within 30 days, and sooner where the law requires it. If you are in India and not satisfied with our answer, you can complain to the Data Protection Board of India.
12. Grievance Officer
Under the Information Technology Act, 2000 and its rules, and the DPDP Act, our Grievance Officer is:
| Name | SivaKumaran Murugesa Pillai |
| privacy@mylineagetrees.com | |
| Phone | +91 88259 96373 |
| Address | R 206, Purva Bluemont Apartment, Singanallur, Coimbatore 641005, Tamil Nadu, India |
We acknowledge every complaint within 24 hours and resolve it within 15 days. This includes privacy requests, requests from people in a tree without an account, and reports of content that breaks our Terms. Account holders can also send a complaint from the Support page.
13. Security
We protect your data with:
- encryption in transit (HTTPS) and at rest (Google Cloud's encryption)
- database security rules that let only a tree's members read it
- server-only control of membership and billing records
- passwords stored only in hashed form by Firebase Authentication
- payments handled by Razorpay, which is certified to the PCI DSS card-security standard
No system is perfectly secure. Keep your password private and tell us at once if you think your account has been misused.
If a breach affects your personal data, we will tell you and the authorities as the DPDP Act, GDPR and other applicable laws require.
14. Children
Accounts are for people 18 or older. We don't knowingly let anyone younger create an account. If we learn that a child has an account, we will close it and delete its data. Children may appear in family trees as described in section 6, and parents or guardians can ask us at any time to remove a child's entry (section 6).
15. Changes to this policy
When we change this policy, we update the effective date and version at the top. For important changes, we tell you by email and in the app at least 30 days before they take effect, and we ask for your agreement again where the law requires it. We also remind members of this policy and our Terms at least once a year.
16. Contact
| Privacy questions or requests | privacy@mylineagetrees.com |
| Everything else | support@mylineagetrees.com |
| Phone | +91 88259 96373 |
| Post | My Lineage Trees, R 206, Purva Bluemont Apartment, Singanallur, Coimbatore 641005, Tamil Nadu, India |