Kinswap

Privacy notice

Preview. Kinswap is running as a trial. This notice was written by the operator and has not yet been reviewed by a lawyer.

Kinswap is made and operated by Tallship s.r.o. in Prague (the operator); contact: ahoy@tallship.cz.

The operator's interim notice, in force until the legal review.

What is stored

Where

With Cloudflare, in its EU jurisdiction: the databases and storage keep data durably only in the European Union. Requests are handled by the Cloudflare data centre nearest to you, which may be outside the EU, and sign-in and connected-app records may be cached there briefly. Messages between the parts of Kinswap (keys and ids, never names) travel through Cloudflare queues created in the same jurisdiction. Emails with codes and match notices are sent through Cloudflare's email service. Error logs hold no names, addresses or tree contents; Cloudflare keeps them for 7 days and may store them outside the EU.

Who sees it

The operator has access to the data to run the service. Cloudflare processes it as the infrastructure provider.

Deleting your account

Ask your agent to delete the account (the delete_account tool); you confirm with a fresh code from your email. It first offers you an export of your tree as JSON (the export_tree tool). Deleted are: your tree (including the people you received from others), email address, display handle, contact line, connected apps, offers and matches, and your points. Nobody is notified. You can disconnect single apps yourself at /connections. If a deletion gets stuck, write to ahoy@tallship.cz: the operator can finish a deletion you started, but cannot start one for you.

Copies of people you gave to others stay with them; their origin, and every pass through your account, then reads "a deleted user". Points others earned through your account stay with them.

Afterwards your account id is left only in the index (the keys Kinswap compares trees by): on blanked entries (no name, year or place, only the entry's own id) and in one record that the account was erased, so that a delayed update cannot bring anything back. It is a random string that no longer resolves to anything: no account, tree, email address or handle belongs to it. For now these entries are kept; removing them after a retention period is planned.

Also after a deletion: the operator could still restore earlier states of the databases and trees, with your account in them, for up to 30 days (Cloudflare's point-in-time recovery). Messages already under way inside Kinswap when you delete are finished or dropped within minutes; one that failed again and again waits in an internal error queue (with ids and keys, never an email address) until the operator deals with it or the queue drops it. The sign-in counter for your address, kept as a hash of it, expires after about an hour; until then a new account with the same address shares it.

Objections and contact

A copy belongs to its recipient: nothing is removed from someone's tree because another user asks or leaves. The exception is a living person who was shared as deceased. In that case write to ahoy@tallship.cz and the operator deletes the person from every tree that holds a copy, one tree at a time, as its owner would delete them. Nobody is notified: the owners see the person gone. Kinswap keeps only when each removal happened and why, with no names or ids. Questions and other objections go to the same address.

How a swap works

  1. Your agent stores people, relationships and sources (transcriptions of entries and links to archives) in your tree. No other user sees your tree; what they can learn from it is listed under "Who sees it".
  2. Deceased people (by the rules below) go into an index as keys: phonetic codes of the surname, a key of the given name, a birth-year range, the place of birth or baptism (as a key, with its OpenStreetMap id and house number when given), the keys of their parents and partners, and whether a record documents them. Kinswap looks for matches of the documented ones with other people's trees in that index.
  3. Both sides learn about a match: from the agent (the list_matches tool) and by email, at most once a day, with counts only and without names. Email notices can be switched off through the agent (the set_profile tool, field match_notices); sign-in codes still arrive.
  4. Before an offer, each side sees how many people per generation the other could give, but no names, years or places.
  5. The giver chooses which people to offer. Only the offer shows the recipient the names, years and places of the offered people, and only theirs, and for people the giver received from someone else, who first contributed them and when. While the offer is open the giver can withdraw it, and the recipient then sees nothing of it. Transcriptions and links come with acceptance.
  6. The recipient accepts all of them or some. The copies go into the recipient's tree with their sources and a record of who first contributed each person and when it passed through each swap. Sources that also concern a living or recently deceased person in the giver's tree are not copied.
  7. A copy belongs to the recipient. It stays even if the giver deletes the person or the account. Received people can be offered onward; the origin stays and each further pass adds a dated entry. A person never goes back to its contributor.
  8. For each accepted person the giver earns points, and on a reshare the original contributor earns too. Each person counts once per recipient, however often it reaches them. The points per person may be changed later; the change then counts for earlier shares too. Other users' points show how much they have given.
  9. Your agent can put a contact line in your profile (the set_profile tool, field contact): one line of up to 200 characters, such as an email address or a phone number. The other side sees it in its list of matches (the list_matches tool) only after a share between you has been accepted, in either direction, and always as it is now: a change or a clearing applies to everyone at once. There is no messaging inside Kinswap.
  10. While an account has given nothing, it gets a limited number of new matches a day and in total; the rest wait.

Rules

Licence

What you share in an accepted offer is licensed under CC BY 4.0: the recipient may keep, edit and pass it on, crediting the original contributor, which is what the origin record does. When an account is deleted, its credit is removed.

Your private tree is licensed to nobody. Kinswap may only store and process it to run the service.