Privacy
Last changed on 13 November 2026.
Who is behind Rundling?
Karim Sehili runs the Rundling app and this website, and decides what happens to your data. “We” on this page means Karim Sehili.
Karim Sehilic/o IP-Management #12600Ludwig-Erhard-Str. 1820459 HamburgGermany
Write to contact@sehilistudio.com about anything on this page.
What does Rundling keep?
Rundling asks for no password, phone number or location, and has no advertising. It counts how the app is used in the two ways described under “What does the app count about how it is used?”. An email address is needed only to sign in, which whoever creates a household must do and everyone else may (see “What does signing in with email involve?”), and you may also give one in feedback you choose to send (see “What happens when I send feedback or a crash report?”). It keeps what a household needs to share its chores:
- the household’s name, and the time zone of the phone that set it up;
- each person’s name and colour, whether they are an admin, and when they are away;
- the chores, their descriptions and schedules, and who they are for;
- who did what and when, the points it earned, and thanks;
- the household’s history, a record of what was changed;
- each person’s reminder time, time zone and language;
- which tips each person has seen, closed or used, and in how many openings of the app they saw each. Tips are the short notes beside the controls; this is kept so each shows only while it helps, with the person’s login or, without one, with their phone’s key;
- when somebody last opened the app after a month or more away, and which of What’s new’s entries each person’s app has already carried. This shows each change once and shows the line on Today only to somebody who was away; it is kept with the person’s login or, without one, with their phone’s key, and goes when they do.
That includes anything people type into these, such as a chore’s name.
Your phone holds a random key, and that key is how the server knows the phone is yours. The server keeps three things about it: a fingerprint, which can’t be turned back into the key, the time your phone last synced, and which months you used the app, which gives you points for them. It keeps only the month, never the day.
Someone may add you to their household by name, as a profile for somebody without the app. Everything on this page applies to that profile too.
We keep this to provide the app you use (Art. 6(1)(b) GDPR). For a profile somebody else added, the reason is the household’s legitimate interest in sharing its chores and seeing who did them (Art. 6(1)(f) GDPR).
What does signing in with email involve?
Signing in is how a new phone finds you again if yours is lost or replaced. Whoever creates a household must sign in, because a household should not be lost along with the phone of whoever set it up. Everyone else may, and without a login a lost phone starts as a new person. You sign in with a six-digit code that we send to your email address; there is no password.
We keep your email address as your login’s contact address and as the address you sign in with, and a note of which person in which household the login belongs to. We use the contact address only for service mail: sign-in codes, confirmations, and notices about your account. We never send advertising.
A code is kept with the address it was sent to, and only as a fingerprint made with a secret key, which can’t be turned back into the code. It stops working after 10 minutes. A code that confirms deleting your account by email works for 7 days. When a code proves that your phone controls an address, the server keeps a fingerprint of that proof for an hour, and with it, where no login exists yet, the address, or the Apple or Google id and address if you signed in that way. After you leave a household, the proof that keeps your phone signed in lasts as long as the login itself is kept with no household, 12 months, and ends when you set up or join another household or sign out. Each, with its address, is deleted soon after it has run out, even for somebody who asks for a code and never types it. The address is kept as a login only once you create or join a household, under the rule in “What happens when I leave?”.
To stop codes being guessed and the server being used to flood inboxes, it counts how many codes an address and an IP address have asked for in the last hour, how many codes an IP address has tried, and how many wrong tries an address has had in the last 15 minutes. It counts an address by a fingerprint, never the address itself, and keeps each count for at most a minute longer than its window. The server keeps an IPv4 address whole, and an IPv6 address only by its first half.
The emails themselves are sent by SMTP2GO (see “Who else receives my data?”).
We do this to give you the login you need to create a household or chose to make (Art. 6(1)(b) GDPR), and to count so that nobody can guess codes or misuse the server (Art. 6(1)(f) GDPR). You can unlink your login or delete your account at any time (see “What happens when I leave?” and the page Delete your data).
Who can see it?
Everyone in a household sees its chores, its people and its history. All of it comes from the household’s own people. Outside the household we show only what an invitation shows, and what the companies named below receive.
An invitation shows the household’s name, how many people are in it, and their initials and colours. It also shows the names and points of profiles nobody has claimed yet, so that someone new can find their own (Art. 6(1)(f) GDPR). An invitation works for seven days, and stops working as soon as someone in the household makes a new one.
If you have a login, anyone holding an invitation also sees your name, colour and points, marked as signed in, so that somebody signing in can find their own profile (Art. 6(1)(f) GDPR). Nobody sees your email address.
If a household you’re not in has put your name in, ask someone in it to take it out, or write to us. The household may write what it needs to share its chores (Art. 6(1)(f) GDPR).
What happens when I leave?
Leaving a household deletes your data, and so does being removed by an admin. Your name, colour, points, reminder, the key your phone holds and your phone’s notification address are deleted, and your name is taken out of the household’s history.
What you did stays in that history, as work by “someone who left”. What people typed into chores, such as their names, stays with the household, even where it contains your name; the household can change it. Beyond that, we keep nothing that marks the work as yours. Feedback or a crash report you sent isn’t linked to your profile or your login, so leaving doesn’t delete it (see “What happens when I send feedback or a crash report?”).
Anyone in the household can remove a profile someone added for you. It is deleted for good within two days, and the removal can be undone for the first day.
Leaving does not delete your login, if you have one, so you can join or create another household. A login with no household is deleted 12 months after it lost its last household, or after it was made, if it never had one. You can delete it sooner: “Unlink my login” deletes the login and its email addresses and keeps you in the household, and “Delete my account” does that and also leaves your household. Neither can be undone.
What you have learned from tips stays with your login, if you have one, apart from what belonged to the household you left; without a login it is deleted with the rest, and deleting your account deletes it too. Somebody who comes back with a new account sees the tips again.
If you lose your phone and have a login, sign in on a new phone and you are back in your household. Without a login you can’t get back in, because the key lives only on the phone: ask an admin to remove you.
Backups can hold on to deleted data, email addresses included, for about 70 days (see “What about backups?”). To delete your data, see the page Delete your data.
When is a whole household deleted?
A household ends when its last person with the app leaves. Everything in it, profiles included, is then deleted, usually within minutes and always within 30 days. The logins of the people who were in it are not part of the household; the rule for them is under “What happens when I leave?”.
A household nobody has opened for 24 months is deleted too. It gets two warnings first, 30 days and 3 days before, and opening the app is enough to keep it. The warnings are notifications, so they reach only phones with the reminder on. Without such a phone, nobody can be warned. The household is then deleted 24 months and 30 days after it was last opened (Art. 5(1)(e) GDPR).
How long is everything kept?
A household’s data is kept as long as the household exists, unless the rules above delete it sooner. Some things are kept much shorter:
- a note of each change your phone sent: 90 days. It lets a change sent twice be applied once. A phone that was offline for more than 90 days can’t send its old changes any more;
- which tips you have seen, closed or used, when you last returned after a long absence, and which of What’s new’s entries your app has carried: with your login for as long as the login is kept (see the entry for it), or, without a login, until you leave the household or it ends;
- an invitation: until 30 days after it ran out;
- what is needed to take back a chore marked done by mistake: 30 days;
- your phone’s notification address: until you switch the reminder off or leave;
- your login, its email addresses and the Apple or Google id kept for it: until you unlink it or delete your account, or, once you have no household, 12 months after you lost your last one, or after the login was made, if you never had one (see “What happens when I leave?”);
- the key Apple gives us to end your Apple sign-in: until it has been sent back to Apple, which happens when you delete your account, unlink your login or remove Apple as a way in, and at the latest 30 days after that fails (see “What does signing in with Apple or Google involve?”);
- a sign-in code and the address it went to: 10 minutes; a code for deleting your account by email: 7 days; the proof that your phone controls an address: an hour, or, once you have left a household, up to 12 months while you are in none (see “What does signing in with email involve?”);
- the counts for IP addresses: two minutes for invitations and just over an hour for new households (see “What does the server see when I visit?”), and just over an hour for sign-in codes asked for and tried;
- the counts kept under a fingerprint of an email address: just over an hour for sign-in codes asked for, and just over 15 minutes for wrong tries;
- a crash report: 90 days; the words of your feedback: a year; the address you gave for an answer: 90 days on the server (see “What happens when I send feedback or a crash report?”);
- the count of how much feedback and how many crash reports you sent today: a day;
- the record of an answer to the question at the start: three years (see “What is kept about my answer to the question at the start?”); an event counted for usage figures: 13 months; the count of how many you sent today, and, from a phone with no household yet, the IP address it was counted under: a day (see “What does the app count about how it is used?”);
- an email you send us, or our answer: until your request is settled;
- the log SMTP2GO keeps of each email with a sign-in code or about your account: 35 days (see “Who else receives my data?”);
- the record of a subscription: until you delete your account, or until your login is deleted after 12 months without a household; the purchase token and record left after an Android account is deleted: until Google confirms the cancellation (see “What does buying a subscription involve?”);
- a referral record: until the free month has been earned or has ended, and then only the count of free months remains;
- a snapshot of the whole server taken by hand: at most 60 days;
- the list of ids of deleted people and households: permanently. An id names nobody (see “What about backups?”).
Backups and error messages have their own sections below.
What does signing in with Apple or Google involve?
Where the app offers it, you can sign in with Apple or Google instead of a code. The app opens Apple’s or Google’s own sign-in screen, and what comes back is a token that Apple or Google signed to say who you are to them. Our server checks that signature against the keys Apple or Google publish, and believes nothing the app says about it. We never see your Apple or Google password, and we do not keep the token. On an iPhone, Apple also hands the app a one-time code with it, and the server trades the code at once for a key that lets us end your Apple sign-in. We keep that key only until we have used it: when you delete your account, unlink your login or remove Apple as a way in, we send it back to Apple, which removes Rundling from the apps your Apple ID lists, and delete it. If Apple can’t be reached then, we try again every hour and delete the key after 30 days at the latest.
We keep the id Apple gives you for Rundling or your Google account’s own id, which never change, and your email address as they give it: your Google address, or Apple’s, which is a forwarding address of Apple’s if you choose Hide My Email. On a first sign-in it becomes your login’s contact address, used only for service mail, as under “What does signing in with email involve?”. Apple sends your address only the first time you sign in, so we keep it then. We don’t ask Apple for your name. Google’s sign-in always sends your name and profile picture along with your address; the app and our server ignore them and keep neither. Where Google or Apple vouches for an address that is already a login of yours, the two are the same login; Apple’s forwarding address counts as an address of yours, since a code sent to it reaches you, so signing in with that address and with Apple lead to the same login. An address Google doesn’t vouch for as its own never matches another login. Mail to a forwarding address goes through Apple’s relay. You can also add Apple or Google to a login you already have, under Account; its address is then kept with that way in, and mail still goes to your contact address.
Apple and Google learn that you signed in to Rundling, and your IP address, as in any connection, and each treats that under its own privacy policy (see “Who else receives my data?”). Our server also fetches their public signing keys now and then; that request says nothing about you.
We do this to give you the login you need to create a household or chose to make (Art. 6(1)(b) GDPR). You can unlink your login or delete your account at any time, as described under “What happens when I leave?”; that removes this way in with the rest of the login.
What does buying a subscription involve?
You buy a subscription from the App Store or Google Play, and the store takes the payment. The store keeps your payment details and the invoice. Nothing about your card, your bank or your payment method reaches us. With the purchase the app gives the store a random number that stands for your Rundling account and names nobody, which is how the store’s notices find their way back to the right account.
Our server asks the store about the subscription and keeps what it needs to know whether a household is covered: which store it is with, the store’s own number for the subscription, which of our accounts holds it, whether it is the monthly or the yearly plan, until when it is paid, whether it renews, whether a renewal failed, whether it is in a free period or came from a free-month offer, and when the server last asked. The store tells us again when something changes, such as a renewal, a refund or a cancellation. We keep this to run the subscription you bought (Art. 6(1)(b) GDPR).
The household sees who pays only as a name and the date its cover ends. A failed renewal is shown only to the person who pays.
Everyone with an account has a personal code. When somebody new starts with it, we keep a record of the two accounts until the free month has been earned or has ended. After that only the count of free months is kept, and the link between the two people is erased. Free months a person has added to a household stay with that household. We do this to give the free month you were promised and to give the person who shared it theirs (Art. 6(1)(b) and (f) GDPR). Somebody who used a code is never told whose it was, and the owner of a code never learns who used it.
When you delete your account, the record of your subscription is erased, your code and your unused free months end, and the household keeps only the date its cover ends. On Android, deleting your account also asks Google to switch the renewal off. Until Google confirms that, we keep the subscription’s purchase token and its record, linked to no account, so that the request can be repeated; we erase them as soon as Google confirms. On an iPhone only you can cancel, and the app says so before you delete.
Who else receives my data?
Apart from the provider of our own mailbox (see “What happens when I send feedback or a crash report?”), these companies receive data. Each gets only what is listed here:
- OVH GmbH, with a server in Limburg, Germany: all the data on that server. It processes it only on our instructions, under a data processing agreement.
- Hetzner Online GmbH, with a Storage Box in Helsinki, Finland: the backups, which it can’t read. It also processes them only on our instructions, under a data processing agreement.
- SMTP2GO (Sand Dune Mail Limited, New Zealand), with its data centre in Amsterdam, Netherlands: the email address and the text of each email we send you, that is sign-in codes, confirmations and notices about your account. It sends them on our instructions, under a data processing agreement. It keeps a log of each message, with its address, for 35 days, according to its privacy policy (smtp2go.com/privacy). For some purposes of its own, it also decides for itself what happens to this data, as its data processing agreement says: running and improving its service, resolving technical issues, and investigating fraud and misuse. For those it is a controller in its own right, under its own privacy policy.
- Expo (650 Industries, Inc., USA): the reminders and warnings, which name no chore, person or household, and, when the app checks for updates, your IP address, phone type, app version and a random ID the app made when it was installed. When you switch the reminder on, and each time the app opens while it stays on, Expo also receives your IP address, the address Apple or Google gave your phone for notifications, and a second random ID, made for the reminder. Expo processes them for us under the data processing clauses in its terms of service, and uses some of them, such as the ID made at installation, for its own purposes too, as its privacy policy describes, keeping them as long as those purposes reasonably need (expo.dev/privacy).
- Apple (USA) or Google (USA), whichever runs your phone: the same reminders and warnings, carried to your phone. When an iPhone registers with Apple for the reminder, the app only asks iOS for the phone’s notification address, and iOS gets it from Apple’s notification service. The app sends Apple nothing else with that request, and Apple sees your IP address, as in any connection, and can tell which iPhone and which app it came from. The app doesn’t ask Apple to give the address up again; our server deletes its copy when you switch the reminder off or leave the household. When your phone registers with Google for the reminder, Google also receives your IP address, your phone’s make and model, its Android version, the app version and an installation ID of its own, separate from both of Expo’s. The request goes through Google Play services on your phone, so Google can also tell which phone it came from. When you switch the reminder off or leave the household, or once your phone learns you were removed from the household, the app asks Google to delete your phone’s registration. Google deletes its installation ID after a time without use, currently 270 days according to Firebase’s documentation (firebase.google.com/docs/projects/manage-installations), and says how long it keeps the rest in its privacy policy (policies.google.com/privacy).
- Apple (USA) or Google (USA), whichever store you buy a subscription from: they take the payment and keep your payment details under their own privacy policies. Our server asks them about the subscription, with the store’s own number for it and no name, and they tell it when something about the subscription changes (see “What does buying a subscription involve?”). Each decides for itself what happens to your payment details under its own privacy policy (apple.com/legal/privacy, policies.google.com/privacy).
- Apple (USA) and Google (USA), if you sign in with them: they learn that you sign in to Rundling and see your IP address, and tell the app who you are, which our server checks. They get nothing about your household. Each decides for itself what happens to that under its own privacy policy (apple.com/legal/privacy, policies.google.com/privacy).
Expo, Apple and Google are in the USA. For a copy of the safeguards they rely on, write to contact@sehilistudio.com. These transfers rest on the EU-US Data Privacy Framework, under which Expo and Google are certified, and on the EU’s standard contractual clauses, which Expo and Apple use (Art. 45 and 46 GDPR).
SMTP2GO is a company in New Zealand. The EU has decided that New Zealand protects personal data adequately (Art. 45 GDPR), and SMTP2GO keeps our mail in a data centre in Amsterdam. Where it passes data on to others outside the EU, it does so under the EU’s standard contractual clauses (Art. 46 GDPR). For a copy of the safeguards, write to contact@sehilistudio.com.
How does the reminder work?
The reminder is off until you switch it on. Only then does your phone register with Expo, which delivers the app’s notifications, and with Apple or Google, which carry them to your phone. On Android, the app contacts Google only then, and on an iPhone, Apple. While the reminder is on, the app tells our server your phone’s current notification address whenever it opens.
Each reminder says how many chores are yours today and about how long they take, in rounded time, or, if you have none and a due chore has nobody, that something is still open. It never names a chore, a person or the household. So that count and time, or that something is open, pass through Expo and through Apple or Google in the USA, and Apple or Google may hold them until your phone can be reached.
We keep your phone’s notification address until you switch the reminder off or leave the household. If it stops working, we delete it.
We do this to provide the reminder you switched on (Art. 6(1)(b) GDPR).
Why does the app contact Expo whenever it opens?
Every time you open the app or come back to it, the app asks Expo’s server in the USA whether there is a newer version of its code. That lets us fix mistakes without waiting for the app store.
Expo receives your IP address, whether your phone is an Android phone or an iPhone, which version of the app it runs, and a random ID the app made when it was installed. The ID names no one and stays the same until the app is reinstalled. How long Expo keeps such requests is set out in Expo’s privacy policy (expo.dev/privacy).
We do this because we have a legitimate interest in fixing the app quickly (Art. 6(1)(f) GDPR).
What about backups?
Every five minutes the server copies its database into a backup. The server encrypts the copy before it leaves, so Hetzner, which stores it, can’t read it. The copy leaves out the IP counts and the counts of feedback and crash reports sent.
We keep backups for 60 days, and Hetzner keeps daily snapshots of its storage for ten days more. So data we delete can still sit in a backup for about 70 days, and then it is gone. OVH, which hosts the server, also keeps a backup of it for 24 hours. A snapshot of the whole server that we take by hand is deleted within 60 days.
After a restore, every person and household deleted before the last backup that passed its checks is deleted again, normally within minutes and otherwise once we have confirmed it. For that we keep a list of the ids of deleted people and households. An id carries no name, and we keep the list permanently. Until they are deleted again, phones may show what came back.
Deletions made since the last backup that passed its checks, normally the last five minutes and longer while backups or their checks are failing, can come back for good if the server is lost or restored through OVH. A restore can also bring back other things deleted since the copy it restores was made, such as a reminder you switched off or a login you deleted. A backup made while a deleted person was back keeps that person like any other data in it. Tell us, and we delete it again.
We keep backups to restore the service after a failure (Art. 6(1)(f) GDPR).
What happens when I send feedback or a crash report?
The app can send two things to our own server: feedback and crash reports. No company receives them apart from those hosting the server and its backups and, if we answer you, the provider of our own mailbox. Neither is linked to your profile, your login, your household or your IP address.
A crash report is for people 16 or older, and is sent only if you allow it. The button and the switch that allow it say so, and we keep no age: allowing it is your own statement that you are. The app asks once, and “Crash reports” in Settings changes your answer at any time. If you allow it, an error the app couldn’t handle is kept on your phone and sent with the next sync: the first line of the error’s message, cut off at its first quotation mark, the names of the functions, files and lines of the app’s code it passed through, the app version and update, Android or iOS and its version, your language and the hour it happened. It contains no name, chore, or anything you typed. If you switch it off, reports not yet sent are deleted and nothing more is sent. Reports already sent stay until their 90 days are over, because nothing on the server says which are yours. We use them to find and fix what broke. All this rests on your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR).
“Send feedback” in Settings is open to everyone. It sends what you write, the address you give if you would like an answer, and the same details about the app and your phone. We use them because we have a legitimate interest in fixing what breaks, improving the app and answering people who write to us (Art. 6(1)(f) GDPR). You can object to this (see “What are my rights?”). Please don’t write anything you wouldn’t want us to read.
To send either, your phone proves that it belongs to a household, and the server counts how much you have sent today, at most five pieces of feedback and thirty crash reports. It forgets the count after a day, and what you sent is saved without it, with only the day it arrived and, for a crash, the hour it happened, so that no exact time joins the two. We count so that nobody can fill the server (Art. 6(1)(f) GDPR).
On the server, crash reports are deleted after 90 days, what you wrote and the details sent with it after a year, and the address you gave after 90 days. We delete them rather than anonymise them. Because feedback isn’t linked to your profile or your login, we can find yours only by what it says or, for 90 days, by the address you gave. To have something you wrote deleted sooner, write to contact@sehilistudio.com with its words. If you write to us by email, or we answer you, the message passes through the provider of our own mailbox, and we keep it until your request is settled (Art. 6(1)(f) GDPR; for a request under your rights, Art. 6(1)(c) GDPR).
Google Play and Apple also tell us when the app crashes or freezes, under their own privacy policies.
What is kept about my answer to the question at the start?
The first time the app opens, it asks whether it may send crash reports and count how it is used. Each answer, to either, is also sent to our own server as a record: which of the two it was, allowed or declined, the day, which version of the question’s words you saw, Android or iOS and the app version. It holds nothing that says who answered, not even an address: your phone sends it without proving anything, and the server counts only how many arrive from one address in a day, at most twenty, and forgets that count after the day.
We keep these records to be able to show how the question was answered and to know how far to trust the usage figures. Because they name nobody, they show how a version of the question was answered, not that you in particular consented. We keep them three years, the usual limitation period, and then delete them. We read them only as totals per week, held back below five answers. Changing your answer in Settings sends a record in the same way. All this rests on our duty to be able to show consent (Art. 6(1)(c) GDPR with Art. 7(1) GDPR).
What does the app count about how it is used?
Two things, both counts and neither a record of you. We never call either anonymous.
The first covers every household. The server already holds what it needs to run Rundling, such as which households exist and which chores they marked done. From that it works out how many households got through setup and joining step by step, how many were active in a week and how many of those started a few weeks earlier, and how the app’s tips were used. A count is shown only when five or more households stand behind it, so a small household is not recognisable in one. It is shown to us only, as figures and never as rows about a household. We do this to see whether Rundling works and where it gets in people’s way (Art. 6(1)(f) GDPR). It adds nothing to what the server receives, and you can object to it under “Your rights”.
The second is for people 16 or older, and only if you allow it. The app asks once when it first opens, and “Usage figures” in Settings changes your answer at any time; allowing it, in either place, is your own statement that you are 16 or older; we keep no age. If you allow it, the app keeps a short list on your phone of what you did, as a name from a fixed list and a value from a fixed list, such as that a chore was marked done from the Today screen, and sends it with the next sync. Nothing you typed, no name, no chore and no identifier is in it. With each count go the app version and update, Android or iOS, your language and a random number made when the app opens, kept only in memory and made anew after half an hour in the background, so one visit can be followed and two visits cannot be matched. The server keeps the day and never the time. A phone with no household yet, such as one in setup, sends through a request that proves nothing; the server counts how many arrive from one address in a day, forgets the count after the day, and keeps no address with the count. All this rests on your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR).
On the server the counts are shown to us only as totals, held back below five visits, and deleted after 13 months. They are not linked to your profile, your login or your household, so we cannot find yours. If you switch it off, counts not yet sent are deleted on your phone and nothing more is sent; counts already sent stay until their 13 months are over. The people who allow this are likely those who care most about the app, so these counts describe them more than everyone.
What do the server’s error messages hold?
When something goes wrong, the server writes an error message. It can contain an IP address and, if the error came while handling a change, some of the household’s data, such as a chore’s name, or, while signing in or managing an account, an email address, or, while saving feedback or a crash report, what it said and, for feedback, the address given.
Messages go when newer ones fill the 30 MB each part of the server has, or when an update replaces that part, whichever comes first.
We keep them to find and fix faults (Art. 6(1)(f) GDPR).
What does the server see when I visit?
The website sets no cookies, stores nothing in your browser, and loads nothing from anyone else.
Your browser sends its IP address with every request, as it has to for a page to reach it. The server uses it to answer and keeps no record of visits. Only an error leaves a trace, as described above.
So that the legal notice also works offline, the app fetches it from this website, with or without a login: about once a day, and whenever you open the app or come back to it until it has a fresh copy. The server sees your IP address and nothing about you or your household, and keeps no record of the request.
When you open an invitation, here or in the app, our server is asked which household the code opens. To stop codes being guessed, it counts how often an IP address has asked in the last minute, and keeps that count for two minutes at most.
When a phone sets up a new household, the server counts how many households its IP address has set up in the last hour, so that nobody can fill the server with empty households, and keeps that count for an hour and a minute at most.
The server keeps an IPv4 address whole, and an IPv6 address only by its first half.
We do this to deliver the website, to keep the legal notice available in the app and to keep the service usable and the households safe from guessed invitations (Art. 6(1)(f) GDPR).
Does the app decide anything about me?
If the household lets the app share a chore out, the app picks who gets it, from whose turn it is and how much each person has done that week. This has no legal or similarly significant effect on anyone, and anyone in the household can change it.
What are my rights?
You can ask what we keep about you, have mistakes corrected and have your data deleted. You can ask us to limit how we use it, and get a copy in a common format a computer can read (Art. 15 to 18 and 20 GDPR).
You can object to anything we do out of legitimate interest. Tell us, and we stop unless we have compelling reasons that outweigh yours (Art. 21 GDPR).
You can withdraw your consent to crash reports at any time, under “Crash reports” in Settings. That doesn’t affect what was done with them before (Art. 7(3) GDPR). The same goes for “Usage figures”.
Write to contact@sehilistudio.com. The quickest way to delete your data is to delete your account or leave your household.
You can also complain to a data protection authority, particularly in the EU country where you live or work, or where you think the law was broken (Art. 77 GDPR).
You don’t have to give us anything, except that creating a household needs a login with an email address. Without a name for you, though, your household couldn’t tell who did what.
When does this page change?
This page changes whenever what Rundling does with your data changes. The date at the top says when that last happened. We don’t send notices, so look at the date.