Skip to the page
Tieloom

Privacy policy

Last updated 18 October 2026.

Tieloom keeps what an office needs to know its people and follow them up, and nothing for advertising. It does not sell personal information or use anything an office keeps to train AI models, and an office can delete any record, or everything, at any time.

1. Who we are

Tieloom is made by 4UGUSTA Systems Private Limited (CIN U62011BR2026PTC084868), A.P. Colony, Gaya, Bihar 823001, India. Write to augusta@4ugusta.agency about anything in this policy; Augusta Bhardwaj, our director, answers privacy questions and complaints himself.

2. Two kinds of people, two roles

Offices that use Tieloom, and the people they sign in: for this information we decide what is collected and why, and this policy describes it.

The people an office keeps in Tieloom (its callers, clients, patients, tenants and buyers): we hold their records for that office and on its instructions, as its service provider. The office decides what is kept and for how long. If you are in an office's Tieloom, ask that office first; if you ask us, we pass your request to it and help it answer.

3. What we collect

  • From the people who sign in: your email address, and your name and Google account number if you sign in with Google. If you sign in with a code, we keep a fingerprint of the code (never the code), a fingerprint of the browser that asked for it, and the internet address it was asked from, for two days.
  • What an office keeps: the people in its workspace (names, phone numbers, email addresses, companies, stages), their timelines (calls, notes, messages and changes, with who made them), tasks, the members it adds and their roles, and fingerprints of the API keys it makes (never the keys).
  • What our products and an office's own code send in with its key: for a call answered by Damaruka, the caller's number and name if given, a summary, what was written down, the call's length and a link to the call in Damaruka. Recordings stay in Damaruka.
  • From visitors to this site: nothing for analytics or advertising.

4. Cookies

One cookie keeps you signed in, and a second lasts a few minutes while you sign in with a code, so the code works only in the browser that asked for it. We use no advertising, analytics or tracking cookies, so there is nothing to opt out of; we treat a Global Privacy Control or Do Not Track signal as the choice it expresses.

5. How we use it

  • To show an office its people, timelines and tasks, and nobody else.
  • To turn what our products send in into people, timeline entries and tasks for the office that connected them.
  • To send sign-in codes, keep accounts secure (limits on codes and on wrong tries) and answer support requests.
  • To meet legal duties.

We do not sell personal information, share it for targeted advertising, or use anything an office keeps in Tieloom to train AI models.

6. Who else handles it

Only the service providers we need to run Tieloom, each bound by contract to use the information only for us:

  • Microsoft Azure, which hosts Tieloom and its database in the United States (Central US).
  • Resend, in the United States, which delivers sign-in codes by email.
  • Google, when you choose to sign in with Google.
  • The products an office connects (Damaruka now), which send in what that office's settings allow.
  • Professional advisers, authorities when the law requires it, and a buyer if the company is ever sold (with notice to you first).

7. How long we keep it

  • People, timelines, tasks and members: until the office deletes them. Anyone with staff access can delete a person, which takes their whole timeline with them; an owner can delete the workspace, which deletes everything in it at once.
  • Sign-in codes and the address they were asked from: two days.
  • Your account: until you ask us to delete it. Backups of deleted information expire within 35 days.

8. Health information

Damaruka sends nothing to Tieloom from an office with health privacy on, so what a patient said on a call stays in Damaruka. Tieloom does not claim HIPAA compliance and does not sign business associate agreements; do not keep health information protected by HIPAA in it.

9. What you can ask for

Wherever you live, you can ask us what we hold about you, to correct it, to delete it, or for a copy; and you can withdraw a consent you gave. Write to augusta@4ugusta.agency. We may need to confirm it is you, and we answer within 30 days. We do not treat you differently for asking.

In India, under the Digital Personal Data Protection Act, 2023, you may also nominate someone to act for you, and if we do not resolve a complaint you may take it to the Data Protection Board of India. Our grievance officer is Augusta Bhardwaj, at the address above.

In US states with privacy laws, these are the rights to know, access, correct and delete. We do not sell or share personal information for targeted advertising, so there is nothing to opt out of.

10. How we protect it

A workspace is shown only to the people its owners add. The database has no address on the public internet; API keys and sign-in codes are kept only as fingerprints; and information travels encrypted. No system is perfectly secure. If a breach affects you, we will tell you, or the office that keeps your record, as the law requires.

11. Where it is

We are based in India. Tieloom and its database are hosted in the United States. When information moves between countries, our contracts require the same care.

12. Children

Tieloom accounts are for offices and adults. An office may keep a record of anyone who contacts it, as described above.

13. Changes

When this policy changes, the new version is posted here with its date, and owners are told by email about any change that matters to them before it takes effect.

4UGUSTA Systems Private Limited. Built on templates prepared and made publicly available by General Legal, PC, which are provided for general reference only, are not legal advice, create no attorney client relationship, and which General Legal has not reviewed as modified here.