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
- Account: your email address, a random account id, when it was created, the display handle others see you by (drawn at random from invented words when the account is created; your agent can change it), your contact line if you set one, whether you want match notices by email, and when the last one was sent.
- Language: English or Czech, the language of the match notices Kinswap emails you;
sign-in codes come in the language of the sign-in page that asked for them. It is set at the
first sign-in to the language of the sign-in page, and your agent can change it (the
set_profiletool, fieldlanguage). The website itself follows your browser's language setting, or the language link at the foot of each page; no cookie is set for that. - Your tree: the people, relationships and sources your agent stores in it, and the people you received from others, with their origin.
- Index: keys of the deceased people in your tree, documented or not, as described below. Even keys are not anonymous (names and years can be guessed), so the index is handled as carefully as the trees.
- Exchange registry: your matches with other users and which of your people each one links; for each match, which of your people the other side lacks, by generation; offers and what became of each offered person; accepted shares and points; and the holder list: which account holds a copy of which person, and who first contributed it. All of it as ids and counts, with no names, years or places.
- Sign-in: the one-time code and attempt counters, kept only as hashes (HMAC) of the address, the IP address and the code. They delete themselves within about an hour.
- Connected apps: the name of each app you allowed, your account id, and access tokens stored as hashes.
- Cookies: signing in sets short-lived cookies needed only for that. Otherwise Kinswap sets no cookies, measures nothing and loads nothing from third parties.
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
- Living and recently deceased people (by the rules below): only you. They never enter the index.
- On a match: the other side sees your display handle, your points, which of their own people the match links to people in your tree, how many people per generation each of you could give the other, and how many you have already exchanged. No names, years or places from your tree.
- After your offer, while it is open: the recipient sees the names, years and places of the offered people, how they are related to each other, and whether they are documented, as your tree holds them at the time.
- After acceptance: the recipient holds copies of those people with their sources and may pass them on, always crediting your display handle as the contributor. A source that also concerns a living or recently deceased person in your tree stays with you (the recipient learns only how many), and so does the partner's name on the marriages of a person with such a partner.
- Your contact line: only users with whom at least one share has been accepted, in either direction (you gave to them or received from them), and always as it is now. Someone who got your people only through another user's reshare does not see it.
- Your display handle also goes with the people you gave, as their contributor. No other user sees your email address.
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
- 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".
- 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.
- Both sides learn about a match: from the agent (the
list_matchestool) and by email, at most once a day, with counts only and without names. Email notices can be switched off through the agent (theset_profiletool, fieldmatch_notices); sign-in codes still arrive. - Before an offer, each side sees how many people per generation the other could give, but no names, years or places.
- 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.
- 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.
- 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.
- 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.
- Your agent can put a contact line in your profile (the
set_profiletool, fieldcontact): 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 (thelist_matchestool) 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. - While an account has given nothing, it gets a limited number of new matches a day and in total; the rest wait.
Rules
- Living people stay private. A person counts as living unless they have a death date or were born more than 110 years ago. People who died less than 30 years ago are treated the same, unless they were born more than 110 years ago. Only you see them; they are never compared or offered.
- Text and links only: transcriptions of entries and permanent links to the images in archive viewers (or the volume and image number), never scans of pages.
- No DNA, ever.
- Kinswap does not take data from other genealogy databases.
- Only documented people are compared: those with a record attached in a role other than witness or godparent. People known only from someone else's online tree are neither compared nor offered.
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.