Privacy Policy

Effective date: October 26, 2026
Last updated: October 30, 2026

This Privacy Policy explains how dhailabs collects, uses, stores, shares, and deletes information when you use our websites, products, and services. It is the single privacy policy for all of dhailabs. There is no separate policy for any product. It covers:

• dhailabs.com, our company website.
• Kin, a private family whiteboard for mapping your family, at kin.dhailabs.com.
• Work, software for managing the full lifecycle of a company's people and teams. Work is in early access.
• Any other product or service we offer in the future. Before a new product collects information in ways not described here, we will add a section for it to this policy.

dhailabs ("dhailabs", "we", "us") is the controller of the personal information described in this policy (Section 14 has our contact details). If you have questions, email [email protected].

The short version

• Kin uses Google Sign-In. From Google we receive only your name, email address, and whether that email is verified. We use them to create your account, sign you in, and match you to boards you were invited to.
• We do not receive your Google password, contacts, files, calendar, or any other Google data. We do not keep Google access tokens.
• What you put on a Kin board (names, birth years, notes, relationships, and dates of birth) is visible only to the board's host and the people the host invites. Birth years are hidden by default. A date of birth or birth year on a card someone has claimed is visible only to that person, unless they are 18 or older and choose to show it to their board.
• Starting a board makes you its host, not its owner. A board brings together information from many people. Each person keeps their own rights in their personal information and in what they contribute.
• Kin hosts must be 18 or older and members 13 or older. Children under 13 cannot use Kin (Section 12).
• Kin data is stored with Cloudflare. We do not sell personal information, and we do not use it for advertising.
• You can download a printable copy of a board, leave a board, pause or delete your account, and ask us for a copy of your data at [email protected]. We handle email requests within 30 days.

1. Information we collect

1.1 dhailabs.com

• No account, no cookies. dhailabs.com is a static website. It does not ask you to sign up and does not set cookies.
• Last product viewed. The site saves one value, dhailabs.lastProduct (kin or work), in your browser's local storage so a return visit can show that product first. It stays on your device and is never sent to us. Clearing your browser's site data removes it.
• Email you send us. The Work early-access button and our contact links open your own email app addressed to [email protected]. We receive only what you choose to send: your email address, your name if your email app includes it, and your message.
• Analytics. See Section 6.

1.2 Kin: information from Google Sign-In

When you choose "Sign in with Google", Kin asks Google for the openid, email, and profile scopes. These are Google's basic sign-in permissions. After you agree, Google tells us:

Kin uses the one-time access token from Google only to read the information above, right after you sign in. We do not store Google access or refresh tokens, and we cannot access your Google account afterwards. Kin does not ask for, and cannot read, your Gmail messages, contacts, Drive files, calendar, or any other Google data.

1.3 Kin: account information

For each account we store an internal account id, your email address (and a normalized form of it used for matching invites; for Gmail addresses, dots and "+tags" are ignored), your name, the list of boards you belong to, when the account was created, your age confirmations (that you confirmed you are 13 or older, or 18 or older, and when), and, if you pause your account, when you paused and whether you chose to hide your card.

1.4 Kin: board content

A board contains what you and the other people on it add:

• Board name.
• Person cards: name, birth year (optional, hidden by default; see below), gender (optional: male or female, used only to word relationships, such as mother or father), notes (optional, up to 500 characters), a color, and the card's position on the board.
• Relationships between cards and their labels (parent, child, spouse, partner, sibling, grandparent, grandchild, or a short custom label).
• Date of birth (optional). Who can see and change a full date of birth depends on whether the card has been claimed, meaning a person has connected their Google account to it:
  • Cards that have never been claimed: only the board host can add, change, or see the date of birth.
  • Claimed cards: only the person who claimed the card can change its date of birth. It is hidden from everyone else on the board, including the host, unless that person turns on "Show my date of birth to my family on this board". This setting is off by default and is available only to people 18 or older. When it is on, the host and members can see the date of birth but cannot change it, and it can be turned off at any time.
  • After a card is unclaimed: once a card has been claimed, its date of birth stays private to that person even if the card later becomes unclaimed (for example, because they are unlinked or removed). The host cannot see or change it. If the person had chosen to show it, it stays shown, but nobody can change it. If they claim the card again, they get control of it back. If they delete their account and keep their card, its date of birth, age, and birth year are deleted and locked (Section 9). The card stays on the board, locked, with no date of birth or birth year: the host cannot attach a new invite to it or link it to anyone, nobody can claim it, and nobody can add the old values back.
  • A member who has no card can add their own card with their name and date of birth.
• Birth year (optional). Birth years are hidden by default:
  • Claimed cards: the birth year is visible only to the person who claimed the card. Only they can change it, and only if they are 18 or older can they choose to show it to their board. Showing their full date of birth also shows their birth year.
  • Cards that have never been claimed: the host can add, change, and see the birth year. The host can choose to show it to the family only if the card is an adult's: 18 or older by exact age when the card has a full date of birth, or at least 19 years since the birth year when it has only a year. If a card stops meeting this rule (for example, its date of birth is changed), the birth year is hidden again automatically. When someone claims the card, the host's choice no longer applies, and the person's own setting (off by default) takes over.
  • After a card is unclaimed: a previously claimed card's birth year stays visible only if the person had chosen to show it, and nobody can change it. On a card kept after its person deleted their account, the birth year is deleted (Section 9).
  • Our server enforces these rules: a date of birth or birth year is only ever sent to people allowed to see it. We also keep a keyed one-way hash of each date of birth so a member can prove which card is theirs by entering their name and date of birth. The server checks the match and never reveals what is on file.
• Save history: when the board was last saved and the email address of the person who saved it.

Kin does not have fields for photos, addresses, or phone numbers on cards. Kin shows initials, not photos. Notes are free text, so please do not put sensitive information in them (see Section 1.5).

1.5 Information about other people, including children

Kin is for mapping a family, so boards usually include information about people other than the account holder: relatives, people who have passed away, and often children. That information is entered by the board host or members, not by the people themselves.

If you add someone to a board, you are responsible for making sure you are allowed to share that information with the people on the board. Add only what the family is comfortable sharing, and avoid sensitive details (such as health, religion, or immigration status) in notes. A person who is on a board, or a parent or guardian of a child on a board, can ask the board host to change or remove the card, or contact us at [email protected] and we will help. See also Section 12.

1.6 Kin: members and invites

• Host invitations. On a board without a host (Section 4), a member aged 13 or older can invite an adult to become host. We store the invitee's email address, who sent the invitation, and when, just as for other invites. Host invitations are never accepted automatically and become void once the board has a host.
• Invites. When a host invites people, we store the email addresses they enter, when each invite was created, who sent it, and (optionally) which card the invite is for. Kin does not send invitation emails. The host copies an invite link or message, or opens a draft in their own email app, and sends it themselves.
• Members. For each board we store its host, its members (account id, email address, and the date they joined), and which member is linked to which card, with how and when the link was made.

1.7 Kin: security and technical information

• Security records. To stop people from guessing which card belongs to whom, we keep short-lived counters of card-confirmation attempts (they expire within 24 hours) and a log of the last 50 card-link events for each board (account id, time, and outcome, with no names or dates of birth).
• Service logs. Our server records minimal operational events (for example "board deleted", with board and account ids, but no names or board content).
• Request data. Like any website, our hosting provider, Cloudflare, processes technical data such as IP addresses, browser type, and request times to deliver and protect the service.

1.8 Kin: phone sign-in (not currently offered)

Kin's code includes an optional phone sign-in that is turned off. If we turn it on, you could add a phone number to your profile. We would then store the verified number (a number, once used, stays reserved to your account so no one else can take it over), store one-time codes only as hashes for 10 minutes, use your IP address and phone number in rate-limit counters that expire within an hour, and send text messages through Twilio. We will update this policy before turning it on.

1.9 Work

Work has no app yet and collects no data through a product. If you email us about early access, we keep your email so we can reply and tell you when Work is available. We keep it until Work launches and we have told you, or for 24 months, whichever is sooner, unless you ask us to delete it earlier. When Work launches, we will update this policy to describe what it processes before it collects any data.

Data companies put into Work. When a company uses Work, the information it puts into Work (for example, about its people and teams) is handled as follows:

• Staff access. Authorized dhailabs staff, limited to our customer care and product teams, may access a company's data in Work only when needed to provide support, keep the Services secure and working, and fix problems.
• Limits on access. Access is limited to people who need it for those purposes, is bound by confidentiality, and is logged.
• Product improvement. To improve our products and services, we use a company's Work data only in aggregated or de-identified form, unless the company agrees otherwise.
• No selling or advertising. We never sell a company's Work data or use it for advertising.
• Who is responsible (EEA, UK, and Switzerland). For personal information about a company's employees and other people that the company puts into Work, the company is the controller and dhailabs acts as its processor, following the company's instructions. Questions or requests about that information should go to the company first; we will help the company respond. For information about the company's own Work account users, such as sign-in details, and for our own records, dhailabs is the controller.

2. How we use Google user data

We use the Google user data described in Section 1.2 (name, email address, and email-verified status) only to:

1. create and identify your Kin account and sign you in;
2. check that your Google email address is verified;
3. match you to boards you were invited to by email address; and
4. show your name and email address to you and to the other members of boards you belong to.

We do not use Google user data for advertising, we do not sell it, we do not use it to build profiles for any other purpose, and we do not use it to develop or train AI or machine learning models. We do not let people read it except (a) the members of your boards, as described above, (b) when you ask for help, (c) when needed for security or to comply with the law, or (d) as part of operating the service through the service providers in Section 7.

dhailabs' use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

3. How we use information, and our legal bases

We use information to:

• provide Kin: store and sync your boards, let you invite people and manage members, and let members confirm which card is theirs;
• keep accounts and boards secure and prevent abuse, such as card-claim guessing;
• answer your messages and support requests;
• for Work customers, provide Work, give support, keep it secure and working, and fix problems, with staff access limited and logged (Section 1.9), and improve our products using only aggregated or de-identified Work data unless the company agrees otherwise;
• keep the service working and fix problems; and
• comply with the law.

We do not use your information for advertising and we do not sell or rent it.

Legal bases (EEA, UK, and Switzerland). If the EU General Data Protection Regulation (GDPR) or the UK GDPR applies to you, we rely on these legal bases:

Where we rely on legitimate interests, we have balanced them against your rights. You can object at any time (Section 10). Where we rely on consent, you can withdraw it at any time; this does not affect processing that already happened.

4. Who can see your information

• People on your board. A board is visible only to its host and the members the host invites. Members can view and edit the board. Dates of birth and birth years follow the rules in Section 1.4: a member sees only their own, any that another adult has chosen to show, and birth years the host has chosen to show on adult cards that have never been claimed. Everyone on a board can see the email addresses of its host and members and who last saved it. The host can also see pending invites.
• What the host can do. The host starts and manages the board. The host can:
  • invite people and revoke invites;
  • remove members;
  • confirm or unlink which card belongs to which member;
  • add, change, and see dates of birth and birth years only on cards that have never been claimed (on any other card, the host sees them only if the person chose to show them, and can never change them), and show the birth year to the family on such a card only if it is an adult's (Section 1.4);
  • edit the board, and download a printable copy;
  • delete the board, or restore it within 30 days.
• Hosting is not ownership. A host can leave a board that has other members, which hands the host role over (Section 9). A host who is the board's only member can delete it instead of leaving. Managing a board does not make the host the owner of information other people contribute, or of information about other people. Each person keeps their rights in their own personal information, and you can use the rights in Section 10 whether or not you are the host.
• Boards without a host. If the host role ends (for example, the host leaves or deletes their account) and no member is eligible to become host, the board is not deleted. It stays as a board without a host. Existing members keep access to the board and to their own information, and can keep viewing and editing it as before. Host-only actions are unavailable until a new host takes over: inviting people, removing members, adding, changing, or seeing dates of birth on cards that have never been claimed, and deleting or restoring the board. The same privacy rules still apply; for example, dates of birth on cards that were claimed stay private to the person who claimed them.
• Inviting a new host. On a board without a host, any member aged 13 or older can invite an adult to become the board's host. Members aged 13 to 17 can send only this host invitation; they cannot invite anyone else. This option exists only while a board has no host. To send it, the member enters the adult's email address, which they share with dhailabs so we can create and match the invitation. Kin does not email the invitee; the member sends them the link. Before accepting, the invitee sees the board's name, the email address of the member who invited them, and that they are being asked to host it. Host invitations are never accepted automatically, and they become void once the board has a host. To accept, they sign in with that email address and confirm they are 18 or older (and their card's date of birth, if they claim one, must not show them as under 18). They then become host and can see the board as any host does, including dates of birth on cards that have never been claimed, but not dates of birth that are kept private.
• dhailabs. As the operator, we can technically access stored data. We access it only to run, secure, and support Kin, when you ask us to, or when the law requires it.
• Nobody else, except the service providers and legal cases in Section 7.

5. Cookies and browser storage

dhailabs.com sets no cookies. Kin uses only the cookies it needs to sign you in:

These are all strictly necessary for the service you request, or remember a choice you made, so they do not need consent. We do not use advertising or cross-site tracking cookies. On a shared computer, sign out of Kin when you are done.

6. Analytics

Analytics are currently off on dhailabs.com and Kin. If we turn them on, we will use Plausible Analytics and/or Cloudflare Web Analytics, which are cookieless services, and we will update this section to say which one is active. They count page visits and a few events (on dhailabs.com: homepage view and product-tile click; on Kin: intro page viewed, Google sign-in clicked, and board created). We send the page address without query strings, so invite links are never included, and we send no names, email addresses, account ids, or board content.

7. Sharing and service providers

We share information only as described here. Our service providers process information on our behalf, under contracts that limit how they can use it:

• Cloudflare, Inc. (United States) hosts our websites and stores Kin accounts and boards (Cloudflare Pages, Workers, and Workers KV), and processes request data to deliver and protect the service.
• Google LLC (United States) provides Google Sign-In, and Google Workspace hosts our [email protected] mailbox. Google's handling of your own Google account is covered by Google's Privacy Policy.
• Twilio Inc. (United States) would send sign-in codes by text message, only if phone sign-in is turned on (it is off today).
• Analytics providers (Section 6), only if turned on (they are off today).
• Legal and safety. We may disclose information if required by law, or if we believe in good faith it is needed to protect the rights, property, or safety of our users, the public, or dhailabs.
• Business changes. If dhailabs or a product is reorganized, merged, sold, or transferred, information may be transferred to the new owner, who must continue to protect it in line with this policy. We will tell you before that happens.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

8. Where information is stored, international transfers, and security

Kin data is stored in Cloudflare Workers KV, which replicates data across Cloudflare's global network. Our service providers are based in the United States. Information may therefore be stored and processed in the United States and other countries whose data protection laws differ from those where you live.

Transfers from the EEA, UK, and Switzerland. When we transfer personal information out of the EEA, the UK, or Switzerland, we rely on the safeguards our providers offer: the EU-U.S. Data Privacy Framework, its UK Extension, and the Swiss-U.S. Data Privacy Framework, where the provider is certified (Cloudflare and Google are), and/or the European Commission's Standard Contractual Clauses with the UK International Data Transfer Addendum, included in their data processing terms. You can ask us for more information about these safeguards at [email protected].

Security. We protect information with HTTPS for all connections, signed HttpOnly session cookies, access checks on every board request, dates of birth sent only to the people allowed to see them and checked using keyed hashes, and rate limits on sign-in and card-confirmation attempts. No system is perfectly secure. If we learn of a breach that affects your information, we will notify you and the authorities as required by law.

9. How long we keep information, and how to delete it

• Boards. A board host can delete a board in Kin. A deleted board becomes read-only and can be restored for 30 days. After that, a daily cleanup job permanently deletes it, including its cards, relationships, invites, member list, card links, and security records.
• Members and invites. Hosts can remove members and revoke invites at any time.
• Leaving a board. Anyone can leave a board at any time. When you leave, your card and its links are hidden from the board and kept, not deleted, and your date of birth stays private to you. If you are invited again and rejoin, they come back as they were. Hidden cards are kept until you rejoin or delete your account.
• When a host leaves. A host who is the board's only member cannot leave, but can delete the board. Otherwise, the host can name an eligible member as the next host, and that member must accept. If they decline or do not answer within 48 hours, hosting passes to the earliest-joined member who has confirmed they are 18 or older, whose card's date of birth does not show them as under 18, and who has not declined. If the host names no one, this happens immediately. The leaving host is removed from the board at once. While a handover is pending, the board works as usual, but host-only actions wait for the new host. Pending handovers are settled when the board is next opened, and by a daily check. If no member is eligible, the board stays up without a host (Section 4).
• Cards. Hosts and members can edit or delete cards at any time.
• Browser data. Signing out of Kin removes cached boards from your browser.
• Printed and saved copies. Copies of a board that someone has printed or saved with "Download a copy" are outside Kin's control. Deleting a board or your account does not delete them.
• Pausing your account. You can pause your account in Kin instead of deleting it. We recommend this if you might come back: your account and boards are kept, and you can resume later. While paused, you cannot use your boards until you resume. When you pause, you choose whether your card stays visible on the boards you belong to. If you keep it visible, it stays as it is, and a date of birth you chose to show stays shown. If you hide it, your card, including its date of birth, is put aside and comes back unchanged when you resume. Boards you host keep working for their members, but host-only actions wait until you resume.
• Deleting your account. You can delete your account in Kin (you type DELETE to confirm), or email [email protected] from the email address on your account. We complete email requests within 30 days and confirm when it is done. When you delete, you choose whether to keep your card on your boards, as an unclaimed card, or remove it. When your account is deleted:
  • your profile (name, email address, list of boards, and age confirmations), your sessions, any phone number reservations, and your card links are deleted, and you are signed out everywhere;
  • your name and email address are removed from the member list of every board you belong to, your card is unlinked from your account and is either removed or kept, as you chose. If you remove it, the whole card, including its birth year and connections, is hidden from the board and kept for 30 days, then permanently deleted (its date of birth is deleted straight away). If you keep it, it stays on the board as an unclaimed card; its date of birth, age, and birth year are deleted and hidden from everyone, including the host, even if you had chosen to show them, and nobody can add the old values back. The card stays locked, with no date of birth or birth year: the host cannot attach a new invite to it or link it to anyone, and nobody can claim it. If an invite was already linked to the card, the person who accepts it joins the board without the card. Any card you had hidden by leaving a board or pausing is also deleted after 30 days; and your email address is removed from any invites and "last saved by" records;
  • boards you belong to as a member stay with their hosts and members, and cards about you that other people added stay on those boards (you can ask the board host to remove them, or ask us to help);
  • boards you host that have other members are kept for those members, and hosting is handed over in the same way as when a host leaves (above). You can choose a successor for each board; the successor must accept within 48 hours and confirm they are 18 or older. If no member is eligible, the board is not deleted: it stays, without a host (Section 4). The new host has the same permissions as any host, including access to dates of birth only on cards that have never been claimed;
  • boards you host that have no other members move to Recently deleted for 30 days, and are then permanently deleted.
• Deletion is permanent. Deleting your account cannot be undone, and we cannot restore a deleted account.
• Email address after deletion. Your email address is freed straight away, so it can be used to create a new account. For up to 30 days we keep a keyed one-way hash of it (not the address itself), together with your old user id and the time of deletion, and then remove it automatically. It cannot be used to restore your account. Nothing else about your account is kept, apart from the short-lived backups and logs described below.
• Backups. We may keep backup copies of stored data for up to 30 days for disaster recovery. Deleted data is removed from backups as they expire.
• Logs and counters. Security counters expire within 24 hours. Each board keeps a short link history of its last 50 card-claim events (for example, a card being claimed or unlinked, or a failed date-of-birth check), with account ids and times, but no names, email addresses, or dates of birth. Older events drop off as new ones are added, and the history is deleted when the board is permanently deleted. If you delete your account, your earlier entries stay in a board's history, under your old account id, until newer events replace them or the board is deleted. Debug logs on our backup system can contain email addresses; they are deleted once they are older than 30 days, together with backups.
• Email. We keep emails you send us for as long as needed to answer them and for up to 24 months afterwards for our records, unless you ask us to delete them sooner or the law requires us to keep them.

Revoking Google access. You can remove Kin's access at any time at myaccount.google.com/permissions. Because we do not keep Google tokens, this mainly stops Kin from signing you in with Google; it does not delete your Kin data, so email us if you also want your account deleted.

10. Your rights and choices

Everyone can:

• Access and copy: see your profile in Kin, and download a printable copy of any board you belong to. For a full copy of your personal information, email us.
• Correct: edit cards on your boards or ask the board host to change your card; your name comes from Google, and you can ask us to correct it.
• Pause or delete: delete boards you host, leave boards, or pause or delete your account (Section 9).
• Ask us for a copy of your data, or make any other request, at [email protected].

If you are in the EEA, the UK, or Switzerland, you also have the right to:

• access your personal information and get a copy;
• rectify inaccurate information;
• erase your information;
• restrict our processing in certain cases;
• data portability: receive the information you gave us in a structured, machine-readable format and have it sent to another controller. Kin's printable copy is for reading. To get a machine-readable copy, email us and we will provide it within the time limits below;
• object to processing based on legitimate interests;
• withdraw consent at any time where we rely on consent; and
• lodge a complaint with a supervisory authority, in particular where you live or work or where you believe your rights were infringed. In the UK this is the Information Commissioner's Office (ico.org.uk); in the EEA you can find your authority at edpb.europa.eu. We would appreciate the chance to address your concern first.

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

If you are in the United States, residents of some states (such as California) have similar rights to know, access, correct, and delete personal information, and to opt out of its sale or sharing for targeted advertising. We do not sell or share personal information in that way. We will not discriminate against you for using your rights.

How to use your rights. Email [email protected], preferably from the email address on your account. We may need to confirm your identity first. We will respond within one month (or within 30 days for account deletion), and if a request is complex we may extend this by up to two more months where the law allows; we will tell you if we do. Requests are free unless they are clearly unfounded or excessive.

11. Information about people who are not users

If you are on a Kin board but do not have an account (for example, a relative added by a family member), the board host manages the board, but that information is still about you. You can ask the board host to change or remove it, or contact us at [email protected]. We will help, which may include passing your request to the board host or removing the information.

12. Children

Our age rules are:

• dhailabs.com is a general company website. It has no age requirement of its own; it does not ask for your age or collect personal information beyond what is described in Section 1.1.
• Kin: you must be at least 18 to create or host a board, including becoming host when a board is handed over (Section 9). You must be at least 13 to sign in and join a board as a member. Where local law sets a higher age of digital consent (for example, up to 16 in some EU countries), that higher age applies to joining. Members aged 13 to 17 need permission from a parent or guardian where the law requires it. On a board without a host, members aged 13 to 17 can invite an adult to become host, but cannot otherwise invite people (Section 4).
• How Kin checks age. Creating a board requires you to confirm you are 18 or older. Accepting an invite requires you to confirm you are 13 or older. When you claim a card, Kin also checks your age from the date of birth on that card: if it shows you are under 13, the claim is refused, and if it shows you are under 18, you cannot host. Existing hosts are asked to confirm they are 18 or older once, at their next host action. Our server enforces these checks. We keep a record that you confirmed, and when. The date of birth check uses the card's existing date of birth and does not reveal it to anyone.
• Work: you must be at least 18.

Children under 13. Kin is not directed to children under 13, and children under 13 may not sign in, create an account, or claim a card. We do not knowingly collect personal information directly from a child under 13 (or under the higher local age of digital consent). If you believe a child under that age has signed in to Kin, email [email protected] with the board or account details. If we learn that a child under that age has an account, we will delete the account and the information it provided, and unlink it from any card. A card about the child that a host added can stay on the board as information about a non-user (see below), unless a parent or guardian asks us to remove it.

Information about children added by adults. Family boards often include cards about children, such as a name, birth year, or date of birth, entered by a host or member. This is information about people who are not users (Section 11). It is visible only to the board host and invited members, and dates of birth and birth years follow the rules in Section 1.4: they are hidden by default, only people 18 or older can show their own, and a host can show a birth year on an unclaimed card only if it is an adult's, so a child's birth year is not shown to the board. A parent or guardian can ask for a child's information to be changed or removed by asking the board host, or by emailing [email protected]; we will help remove it.

13. Changes to this policy

We may update this policy. We will post the new version on this page with a new effective date. If a change materially affects how we use information we already have, we will tell you in Kin or by email before it takes effect, and where required we will ask for your consent.

14. Contact us

dhailabs
Email: [email protected]