Privacy policy
Courtesy translation. The German version is the legally authoritative one.
1. Controller#
Vicoli GmbH
Richard-Strauss-Straße 25
81677 München
Deutschland
Email: hello@bagful.app
No data protection officer has been appointed; the threshold in §38 BDSG (generally at least 20 people permanently engaged in automated processing) is not met.
2. What we process#
| Data | Purpose | Legal basis |
|---|---|---|
| Name, email address, password (stored only as a hash), whether the address is confirmed, your language | Creating and running your account, and sending account email in your language. You can sign in with an email address and a password only once you have confirmed the address through the link in our email. Your name is visible to every member of your bags, even before they open a bag you share; it is also in their app's storage and in their data export | Art. 6(1)(b) GDPR |
| Your device's push token, its platform, and when it was last seen | Delivering notifications to that device. The token belongs to the app installation rather than to you: signing into a different account on the same device moves it to that account. It is removed when you sign out and when you delete your account. The data export omits the token itself — it is a key, not a fact about you | Art. 6(1)(b) GDPR |
| Your browser's push subscription, if you turn on notifications in the browser: the address its push service issued for it (the endpoint), two encryption keys, and when it was last seen | Delivering notifications to that browser. The subscription is stored per sign-in and used only while that sign-in lasts: signing into a different account in the same browser moves it to that account. It is deleted when you turn notifications off in Bagful, when you withdraw the browser's permission for notifications, when you sign out, when the browser's push service reports it gone (it answers 404 or 410), and when you delete your account. The data export omits the endpoint and the keys | Art. 6(1)(b) GDPR |
| Profile picture, if you upload one | Making you recognisable in your bags. The picture is served publicly from a random, unguessable address and is shown in the app only to people you share a bag with. Anyone who knows the address can fetch it; replacing or removing the picture retires that address. The public invitation preview never shows pictures, only initials | Art. 6(1)(b) GDPR |
| Guest account: a random identifier and a generated name in your language, which you can change, no email address of yours | Using Bagful without registering, in particular when joining via an invitation link. Section 7 says when a guest account is deleted | Art. 6(1)(b) GDPR |
| Sign-in with Apple, Google or GitHub, if you use it: the identifier of your account there, your email address and whether it is confirmed, your name, and the access tokens the provider issues at sign-in | Signing you in without a password for Bagful. We use the name as your display name; if the provider sends none, the part of your email address before the @. We never store a picture from the provider. We use the access tokens for nothing else, with one exception: with Apple's token, we withdraw your authorisation of Bagful at Apple when you delete your account (section 8). We link such a sign-in to an existing account only when both email addresses are confirmed. The link is deleted with your account. More in section 3 | Art. 6(1)(b) GDPR |
| Session identifier, session IP address and user agent | Keeping you signed in, detecting abuse | Art. 6(1)(b) and (f) GDPR |
| Lists, items, quantities, units, notes, categories, emojis | The service itself | Art. 6(1)(b) GDPR |
| Memberships and roles, invitation tokens and bag codes, expiry and use counters | Sharing bags with other people | Art. 6(1)(b) GDPR |
| Who added or checked off an item, and when | Making collaboration legible — visible to every member of that list | Art. 6(1)(b) GDPR |
| Who has taken on fetching an item, and when | Avoiding duplicate shopping — visible to every member of that list, and readable by a connected AI assistant if you have one. The entry is cleared when the item is checked off or removed, when you leave the list, and when your account is deleted. | Art. 6(1)(b) GDPR |
| Notifications: what happened, who did it and in which bag — stored as a snapshot taken at the time of the event | Telling you about changes in your bags. A notification about you stays in other members' inboxes even if you delete your account — your name is removed, the event itself remains. | Art. 6(1)(b) GDPR |
| Units you create: a short form and a name, both your own words | Your own measures, like "bunch" — visible to every member of a bag where you have used one on an item. They are not translated and stay exactly as you write them. | Art. 6(1)(b) GDPR |
| Your Look: the Base and the Accessories you chose for Checki | Making Checki look the way you chose — visible to every member of a bag you own. We never show it signed out or before someone joins a bag. Only registered accounts can choose a Look. It is in your data export | Art. 6(1)(b) GDPR |
| People you block: whom you blocked, and since when | Making sure the two of you are in no bag together and cannot meet through an invitation either. The blocked person is not told. Your data export holds the Blocks you made | Art. 6(1)(b) GDPR |
| Moderation: when we closed a bag, whom we ejected from a bag, and when we suspended an account | Stopping breaches of the terms, usually after a report (section 9). People decide this, case by case. A closed bag takes no new members, and its members keep using it. Someone ejected cannot come back into that bag. A suspension ends all of the account's sign-ins and disconnects its assistants; its bags and memberships stay. The data export holds only when a bag was closed | Art. 6(1)(b) and (f) GDPR |
| Registered AI clients, consents granted, access tokens | Connecting your own AI assistant over MCP | Art. 6(1)(a) GDPR |
| Newsletter, if you subscribe: your email address, the language of the page you subscribed from, and the time and IP address of your confirmation | Sending you the Bagful newsletter in your language. Subscribing uses double opt-in: you are on the list only once you confirm through the link in the email we send you, and the time and IP address of that confirmation are kept as proof of your consent. We do not track opens or clicks per subscriber. The subscription is not linked to a Bagful account. The list, and the mail server that sends it, are hosted for us by a hosting provider in Germany as our processor, and reached through our network and security provider (section 3). Used until you unsubscribe. After that your address stays on the list marked as unsubscribed, and an address we blocked after delivery failures or a complaint stays on it marked as blocked, so that we send it nothing more. A sign-up that is never confirmed stays on the list unconfirmed and receives no newsletter. The proof of your confirmation is kept as long as we need it to show your consent. The unsubscribe link in every newsletter withdraws your consent at any time | Art. 6(1)(a) GDPR; proof of consent and the blocked marking: Art. 6(1)(f) with Art. 7(1) GDPR |
| Crash reports and performance measurements of the application: error message and stack trace, device model and technical device state, the version of the app and of the operating system, launch and load times, the route visited and the last steps taken before an error — not linked to your account | Finding and fixing faults, keeping the app fast — our legitimate interest in a service that works. Reports carry no account identifier, only a random identifier of the app installation | Art. 6(1)(f) GDPR |
| Protection against abuse: the IP address of every request, your account identifier, the bot check on sign-up, guest access, password reset, the contact form and the newsletter sign-up, and a hash of your email address when someone triggers email to it | Protecting the service from automated sign-ups and floods of requests, and stopping anyone from swamping someone else's inbox with email from us — our legitimate interest in a service that stays available and in protecting third parties. We count requests per IP address or account; those counters live in memory only and run out after a minute. An address gets at most five emails an hour that someone can trigger without signing in, and at most three repeat newsletter confirmations. For that, our network and security provider (section 3) counts under a hash of the address; the address itself is not in the counter, and it is deleted when the hour ends. We keep server log lines for the same purpose (section 7) | Art. 6(1)(f) GDPR |
Usage statistics, unless you switch them off: which pages of the website and screens of the app are visited, as the route pattern with the identifiers of bags, invitations and links taken out; the name of an interaction from a fixed list (such as signing up, creating a bag, adding or checking off items, sharing or accepting an invitation, connecting an assistant) and its properties, each a value from a fixed list, a number or a yes or no; the address of the page you came from and the campaign parameters of the link (utm_* and ref); the website's host name; the platform (web, iOS, Android or assistant); your screen size, language setting and user agent (browser or app, and operating system); and the country, region and city your IP address points to — not linked to your account | Seeing which pages and features are used, where visits come from and where people give up, so we can improve Bagful — our legitimate interest in a service people find useful. The statistics carry no name, no email address, no account or device identifier and nothing from your bags, and nothing is stored on your device to recognise you. Only if you agree to Recognised statistics (the next row) do they carry a code made from your account. Your IP address and user agent reach our statistics server only to work out the country, region and city and an identifier for the visit, a hash whose salt changes every month; the IP address itself is not stored. Our server sends two outcomes itself, without your IP address or user agent, unless your account has statistics switched off: items an AI assistant you connected adds to a bag, and an invitation that made you a member of a bag. Our statistics server is hosted for us by a hosting provider in Germany as our processor, and reached through our network and security provider (section 3). Your browser sends them to bagful.app itself, so it makes no request to a third party for them. A browser that sends Global Privacy Control objects by automated means (Art. 21(5) GDPR), and we honour it: that browser sends no statistics, and the cookie settings show them as off while it does. What you chose there applies again once the signal goes. The two outcomes our server sends itself follow your account's choice, not the browser's signal. You switch statistics off in the cookie notice on the website while you are not signed in, with "Only what's needed" or its switch, on the app's welcome screen, or, signed in, in Settings under Usage statistics, where the choice is kept on your account for every device. Signing out of an account with statistics off keeps that device off | Art. 6(1)(f) GDPR |
| Recognised statistics, only if you say yes: the usage statistics above with a code made from your account added to them, a hash of your account identifier made with a secret key, so that your visits can be counted together across visits and devices | Seeing how Bagful is used over time, what helps and what doesn't, so we can improve it. We ask once, right after you sign up, with Yes and No as equal answers. Nothing is recognised without your yes. With your answer we record when you said yes or withdrew it and which version of the question's wording you answered, so that we can show your consent. Only our server holds the key; no app or browser can make the code, and your app or browser receives it from our server only while you have said yes. The code is not your account identifier itself and carries no name, no email address and nothing from your bags. With it, our statistics server (hosted as for usage statistics) links the visits that carry it to one another, on every device you are signed in on. You can withdraw your consent at any time in Settings under Usage statistics, and withdrawing deletes the visits that carry your code from our statistics server. So does deleting your account, and signing up from a guest account: the guest's code goes with the guest, and your answer moves to the new account. We change the key at least every 25 months and destroy the old one; after that no earlier code can be linked to you or anyone else, by us included, and the visits recorded under it stay, but cannot be linked to any account. A browser that sends Global Privacy Control still sends no statistics, recognised or not | Art. 6(1)(a) GDPR |
| Bagful Plus, if you buy it: that you hold it, which store you bought it in, the purchase's identifier, when the current period ends, whether it renews automatically, and whether and why it ended — a refund, a family share ending, a transfer to another account, or expiry | Giving you the larger allowance you paid for, on every device you sign in on, and letting you restore the purchase after a reinstall or on a new device. The store tells us the purchase and every later change to it through a purchase provider (section 3), which holds your account identifier with us, your purchase history and the store's receipt or token for it. We never learn your payment details: Apple and Google take the payment in their own store, and the renewal and any cancellation happen there too | Art. 6(1)(b) GDPR |
| Transfers of Bagful Plus, if you hold it: a count of how many times your purchase has been seen to move to another Bagful account on the same store account — that count alone, no other accounts and no times | Spotting abuse — our legitimate interest in seeing whether one purchase is being passed around many Bagful accounts. Restoring brings Plus to the account you are signed in with, and it is meant to: we only count it, and look at a count that is implausibly high. The count decides nothing — it never refuses you anything, never takes Plus away and never slows anything down. It sits with your Plus and is deleted with your account | Art. 6(1)(f) GDPR |
| Campaign links, when you click one: the link and the address it leads to, your user agent (and the operating system, browser and device read from it), the address of the page you came from, and the country, region and city your IP address points to — the IP address itself is not stored | Counting which of the campaigns Bagful runs outside its website and apps, such as ads, are used — our legitimate interest in knowing which campaigns reach people. A Campaign link is a link in such a campaign that counts the click on its way to the page it leads to. The count carries no account or other per-person identifier, and nothing is stored on your device. Campaign links are not usage statistics: switching usage statistics off does not stop the count, and neither does Global Privacy Control | Art. 6(1)(f) GDPR |
| Counting pixels, when a page carrying one is viewed: which pixel it was, the country, region and city your IP address points to, your user agent and the address of the page you came from — the IP address itself is not stored | Counting how often pages of ours outside Bagful's website and apps are viewed — our legitimate interest in knowing whether they are read. A Counting pixel is an invisible image on such a page; loading it counts the view. We never put Counting pixels in emails. The count carries no account or other per-person identifier, and nothing is stored on your device. Counting pixels are not usage statistics: switching usage statistics off does not stop the count, and neither does Global Privacy Control | Art. 6(1)(f) GDPR |
We process no special categories of personal data within the meaning of Art. 9 GDPR. The service is not directed at children.
3. Recipients and processors#
Data processing agreements under Art. 28 GDPR are in place with all of the following.
| Provider | Role | Processing location |
|---|---|---|
| A database provider | Database — all account and list data | Germany. The provider is based in the USA: transferred under the EU-U.S. Data Privacy Framework, for which the provider is certified, and the EU Commission's standard contractual clauses |
| A network and security provider | Running the application, caching, storing and serving profile pictures, realtime connections, serving the website, bot protection on sign-up, guest access, password reset, the contact form and the newsletter sign-up, counting requests and emails to protect against abuse, sending verification and password-reset email and the notice to an address's owner that someone tried to sign up with it, sending enquiries from the contact form to us, keeping our server log lines, passing requests on to the servers our hosting provider runs for us, and redirecting clicks on Campaign links. Processes the IP address of every request | EU data centres where possible, global network. The provider is based in the USA: transferred under the EU-U.S. Data Privacy Framework, for which the provider is certified, and the EU Commission's standard contractual clauses |
| An error-diagnostics provider | Error diagnostics in the web application, on our servers and in the mobile app | EU data centres. The provider is based in the USA: transferred under the EU-U.S. Data Privacy Framework, for which the provider is certified, and the EU Commission's standard contractual clauses |
| A hosting provider | Hosting our servers for the newsletter (the list and the mail server that sends it), for usage statistics, Counting pixels and Campaign links | Germany |
| A diagnostics and push provider | Performance diagnostics of the mobile app, and relaying push notifications to Apple's and Google's push services | USA — transferred under the EU-U.S. Data Privacy Framework, for which the provider is certified, and the EU Commission's standard contractual clauses |
| A purchase provider | Delivering and restoring a purchase of Bagful Plus, and telling us when it changes or ends. Holds your account identifier with us, your purchase history and the store's receipt or token for it, the type of device and operating system you bought on, and when you were last seen. Deleted with your account | USA, on the infrastructure of a US cloud provider whose own sub-processors are all in the USA — transferred under the EU Commission's standard contractual clauses in the provider's data processing agreement (August 2026). This provider is not certified under the EU-U.S. Data Privacy Framework |
On request we give you the names of the providers we use; write to us at the address in section 1.
The website's public pages, the legal pages included, make no requests to third parties until you press Subscribe in the newsletter form or Send message in the contact form. Only then does your browser load the bot check of our network and security provider, which checks that a person rather than a bot is subscribing or writing; opening either form loads nothing.
Usage statistics (section 2) do not change this: your browser sends them to bagful.app itself, which passes them on to our statistics server.
On error diagnostics specifically: the error message, stack trace, page or route visited and browser/OS version, or our server's runtime version, are transmitted. The IP address is technically present on receipt but is not stored. There is no session replay and no performance tracing. Invitation tokens and connection tickets are stripped from URLs before transmission.
In the mobile app, error diagnostics run under the same commitments. The app reports crashes and unhandled errors; what is transmitted is the error message and stack trace, the device model, the version of the app and of the operating system, technical facts about the device at the moment of the error (memory, battery level, orientation, time zone and language, for instance) and the last steps before it: the addresses of our API that were called, without tokens, the app's console output, and the controls last touched, with their labels — for an item row, that includes the item's name. So that we can tell how many installations an error affects, the error-diagnostics provider also counts the start and end of each app session under a random identifier the app generates for this installation — it is not an account, cannot be matched to your account, and is issued afresh on a reinstall. No screenshots, no view hierarchy, no session replay, no performance tracing, no profiling; your account is never named to the error-diagnostics provider. Invitation tokens and connection tickets are stripped before transmission here too, and the IP address is not stored, as above.
On performance diagnostics in the mobile app: the app measures how long it takes to launch and how long each screen takes to appear and to become usable, and transmits those timings to our diagnostics and push provider. Each transmission carries the route name — the identifiers of bags, messages and invitations are removed from it first — the device model, the operating system and its version, the version and build of the app, your language setting, and a random identifier of the app installation that is not an account and is issued afresh on a reinstall. The launch timing adds technical facts that explain a slow start: battery level and low-power mode, thermal state, network type (Wi-Fi or cellular) and a summary of the network requests made during launch (count, data volume, duration, slowest server). With these measurements, the contents of your bags, your name and your email address do not leave the device. This applies to the builds we distribute through TestFlight, Google Play or as previews. The development client sends nothing: no measurements, because development builds do not dispatch them, and no error reports, because we give it no access there. Error reports go to the error-diagnostics provider; only an error that occurs while the app is still starting can reach the diagnostics and push provider too.
Push notifications reach your device through the push relay of that same provider: our server hands it your device's push token, the text of the notification — that is, who did what in which bag, as it appears on your lock screen — and the bag's identifier. The provider passes this on to Apple's or Google's push service and, by its own account, does not store it.
Push notifications in the browser go without that relay: our server sends them itself to the push service of your browser's vendor — Apple, Google, Mozilla or another, depending on the browser you use. That service is chosen by your browser, not by us, which is why it is named here and not in the table above. It receives your subscription's endpoint and the notification, which carries the same as in the app: who did what in which bag, and the bag's identifier. The notification is encrypted end to end for your browser (RFC 8291), so the push service cannot read the text; only your browser can decrypt it.
On voice input in the mobile app: dictation is optional and stays off until you tap the microphone in the app. When you do, the recording is handed to your own device's speech recognition (iOS Speech, or Android SpeechRecognizer). On many devices that recognition does not happen on the phone but on Apple's or Google's servers, under those companies' own terms and within your own relationship with your operating system's vendor. We have no control over it and cannot enter into a processing agreement about it — which is exactly why Apple and Google are named here and not in the table above. Bagful itself never receives or stores the recording. All that reaches us is the text that comes back, and even that only once you actually save the item — cancel the dictation and nothing is left behind. On iOS the permission prompt tells you the same thing before speech recognition is used for the first time.
On signing in with Apple, Google or GitHub: for the sign-in at their end, these companies are independent controllers and not our processors, which is why they are named here and not in the table above. If you choose one, it learns that you are signing in to Bagful. The sign-in happens in your device's sign-in sheet or in a browser window. Apple gives us your name only on the first sign-in and lets you share a private relay address instead of your own; Apple forwards our email to that address on to you. At GitHub we ask only for read access to your profile and your email addresses, to find the primary one; we do not store your GitHub username, and without an email address the sign-in is refused and nothing is stored. If you delete an account with an Apple sign-in, we send Apple its token to withdraw your authorisation of Bagful; if that fails, the account is deleted anyway.
On buying Bagful Plus: the purchase is made in Apple's or Google's own store, and for the payment these companies are independent controllers and not our processors, which is why they are named here and not in the table above. They learn what you bought and hold the payment details; we never see them, and we are told only that the purchase exists and what state it is in (section 2). A subscription renews with them until you cancel it, and you cancel it and ask for a refund in your store account, not with us.
4. Disclosure to AI assistants on your instruction#
Bagful exposes an MCP interface that lets you connect your own AI assistant (such as Claude or ChatGPT) to your bags. That connection is created solely by your explicit consent on the consent screen. The connected service receives the bags:read scope (read bags and items) and, where granted, bags:write (create, change, check off and delete items).
The people you share a bag with see that you have connected an assistant, and which of these two scopes it holds: the app draws it under your name in that bag's list of people. They do not see which assistant it is. Nobody outside the bag sees it — the public invite preview never shows it — and it disappears when you withdraw your consent (Art. 6(1)(b) GDPR).
The provider of the assistant you choose is an independent controller for the processing that happens on their side; this is not processing on our behalf.
You may withdraw your consent at any time with effect for the future (Art. 7(3) GDPR): in the app under Account, in the connected-assistants section, or by an email to the address above. Withdrawal ends the assistant's access immediately. It does not affect the lawfulness of the processing carried out until then, and it does not delete the data the assistant has already received — for that, contact the assistant's provider, who is independently responsible for it. Your own data in Bagful, including the local copy on your device (section 6), is unaffected by the withdrawal.
5. Realtime synchronisation#
An open list holds a WebSocket connection so changes appear immediately for every member. The connection is authorised with a short-lived signed ticket. Change events travel over it; nothing is stored there.
7. Retention#
- Account and list data: until the account is deleted.
- Guest accounts: a guest account is deleted after its sign-in has ended, with the same effect as if you had deleted it yourself (section 8). A sign-in ends when you sign out or after 365 days without use. A daily run deletes the guest account once it is more than 30 days old and its last sign-in expired more than 30 days ago, so about 395 days after its last use. After you sign out, only the account's age counts. We cannot warn you first, because a guest account has no address. One run deletes at most 100 accounts, so a backlog spreads over several days.
- Sign-ups with no confirmed address: if the email address is not confirmed after seven days and no sign-in with Apple, Google or GitHub is linked, the same run deletes the account. The confirmation link is valid for 24 hours.
- Sessions: until you sign out, or up to 365 days without use; each use extends this, at most once a day. The next daily run deletes an expired sign-in, with its IP address and user agent. A guest account's expired sign-in stays until the guest account is deleted.
- Deleted items: we remove the name and content at once on deletion. A remainder with no content, which only tells other devices about the deletion, stays for 90 days and is then deleted for good.
- Changes from the app and through assistants: we keep the server's answer to a change, which can hold the names of items and bags, for 30 days, so that sending the change again does not carry it out twice. It is deleted at once with your account.
- Your Look: until you change it or your account is deleted.
- Blocks: until you lift them or either account is deleted. Moderation: an ejection from a bag stays until we lift it or the bag or the account is deleted, the closing of a bag until we lift it or the bag is deleted, a suspension until we lift it or the account is deleted.
- Notifications: 90 days, then deleted — the same window as deleted items, because a notification should not outlive the thing it describes.
- Units you create: until you delete them or your account is deleted. A unit you have already used on an item stays there as text — including in bags you have left, and including after your account is deleted. Deleting the unit removes it from items in bags you belong to; elsewhere the text remains.
- Invitation links: they work until their expiry date or their permitted number of uses is reached. Their entry stays until the first daily run after the expiry date, or until it is revoked, or the bag or the account that created it is deleted. Bag codes have neither an expiry nor a use limit — they are kept until the bag's owner replaces or turns off the code, until the bag is deleted, or until the account that created it is deleted.
- Newsletter: until you unsubscribe; the proof of your confirmation (its time and IP address) as long as we need it to show your consent. An unsubscribed or blocked address and a sign-up never confirmed stay on the list as such; there is currently no period for that.
- Sent emails: our network and security provider retains the message and its content in an activity log for seven days.
- Server log lines: seven days. Our network and security provider keeps the lines our servers write. A line holds, when a rate limit refuses a request, your IP address or your account identifier, and when a new bag or item is refused because the number allowed has been reached, your account identifier (for an item, also the identifier of the account that owns the bag). When your account is deleted, a line can hold your account identifier. When something goes wrong, a line holds the error message; it can include a bag's identifier or details from the request concerned. With every line the provider also stores the method and address of the request it came from, including its parameters. It stores no other details of the request, such as its headers.
- Usage statistics: no fixed period. They cannot be traced to anyone: no IP address and no identifier of you or your device is stored, and the salt of the visit hash changes every month, so visits from different months cannot be joined.
- Recognised statistics: the visits that carry your code are deleted when you withdraw your consent or delete your account. We change the key the code is made with at least every 25 months and destroy the old one, so after 25 months at the latest a code can no longer be linked to anyone. The record of your answer (when, and to which version of the question) is kept until your account is deleted.
- Campaign links: as for usage statistics, no fixed period, for the same reasons.
- Counting pixels: as for usage statistics, no fixed period, for the same reasons.
- Crash reports and performance measurements: the error-diagnostics provider deletes error events after at most 90 days (its default). The diagnostics and push provider keeps measurements for at least 60 days; it names no upper bound, and we cannot set one there.
- After deletion, data may remain in our database's change history for the length of its recovery window — currently seven days — after which it is permanently overwritten.
8. Account deletion#
When an account is deleted, every list owned solely by that account with no other members is permanently deleted along with all its items. Lists that do have other members are automatically transferred to the longest-standing remaining member, so that the other members' data is preserved. Membership is removed from all other bags, and remaining entries are anonymised so they can no longer be attributed to the deleted account. Invitation links and bag codes created by that account stop working — including the code of a bag that was transferred to another member. The new owner can create a fresh code at any time.
The account's profile picture, sign-ins, push tokens and links to Apple, Google or GitHub, its Look, the units it created, and Blocks by it and against it are deleted with it, and so are the visits that carry its Recognised statistics code. We also remove the profile picture from the cache of our network and security provider; copies in a browser's cache are beyond our reach. For a sign-in with Apple, we withdraw the authorisation of Bagful at Apple (section 3).
The same goes for guest accounts and for sign-ups with no confirmed address, which we delete under the rules in section 7.
9. Contact form#
You can send us an enquiry through the contact form ( /contact ). When you do, we process:
- your email address, so we can reply,
- your name, if you give one,
- your message,
- your device's local time and time zone,
- the country our network and security provider places your IP address in (the address itself is not part of the enquiry),
- the language of the page you write from,
- when you write from the app, or signed in from the web app, your account: user ID, display name, account email address and whether it is a guest account. The app hands the page a reference valid for 30 minutes for this, and the page says so before you send.
- when you report something: what you report (a bag, a member, an invitation link or a bag code) and the reason you choose, and for a bag or a member also its name and identifier and whether you have blocked that person. For an invitation link or a bag code, the enquiry also carries the name and identifier of the bag it leads to. The note is optional. The person reported is not told who reported them.
The only purpose is to answer your enquiry. The legal basis is Art. 6(1)(b) GDPR where your enquiry concerns a contract or steps towards one, and otherwise our legitimate interest in answering enquiries (Art. 6(1)(f) GDPR). We also review a report to stop breaches of the terms (Art. 6(1)(f) GDPR). Before it is sent, the bot protection of our network and security provider checks that no bot is writing (section 3). The enquiry is not stored in our database; it is sent through that provider as an email to our inbox, and the provider keeps the sent email in an activity log for seven days (section 7). We keep an enquiry or report in our inbox until it is settled and no claim can arise from it. We send no automatic confirmation to the address given.
10. Your rights#
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interests (Art. 21 GDPR). Consent you have given may be withdrawn at any time with effect for the future (Art. 7(3) GDPR).
The main ones you can exercise directly in the app, under Account:
- Portability (Art. 20): "Download my data" gives you all your bags, items and invitations as a JSON file.
- Erasure (Art. 17): "Delete my account" removes your account and data under the rules in section 8. Before you confirm, you are shown which bags will be deleted and which will be transferred.
- Withdrawing consent (Art. 7(3)): in the connected-assistants section you can cut off any assistant's access at any time (section 4), and under Usage statistics you can withdraw your consent to Recognised statistics, which deletes the visits recognised under it (section 2).
- Objection (Art. 21): under Usage statistics you can switch the statistics off at any time (section 2).
For anything else, send a message to hello@bagful.app.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority competent for us is: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA) (https://www.lda.bayern.de).
11. No automated decision-making#
There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR. We show no advertising in Bagful and sell no data.
12. Changes to this policy#
We update this policy as the service changes. The version published here, with the date shown below, is the applicable one.