プライバシーポリシー
バージョン2026-11-15、2026/11/15から有効
Controller
Nadeem Ahmad, 50825 Köln, Germany.
Contact: legal@mygritwall.com.
Google user data
This section describes how MyGritWall accesses, uses, shares, protects, keeps and deletes data it receives from Google when you choose "Continue with Google".
Data we access: we request only the Google sign-in scopes "openid", "email" and "profile". With them Google sends us your name, your email address, the address of your profile picture and a stable identifier of your Google account. We do not request or access any other Google data: not your Gmail, Drive, Contacts, Calendar, Photos or any other Google service.
How we use it: only to create your MyGritWall account, to sign you in to it and to set the email address of your account. We do not use Google user data for any other purpose.
Sharing, transfer and disclosure: we do not sell Google user data and do not share, transfer or disclose it to anyone, except to Amazon Web Services, which runs our sign-in service and database on our behalf under a data processing agreement, and where the law requires us to disclose it.
Protection: Google user data is transmitted only over encrypted connections (TLS) and stored in Amazon Web Services in the EU region Frankfurt, encrypted at rest. Only the operator has access to the systems that hold it.
Retention and deletion: we keep Google user data for as long as your MyGritWall account exists. You can delete your account at any time in Settings, Privacy, or ask us to delete it by writing to legal@mygritwall.com; the Google user data is deleted with the account. You can also remove MyGritWall's access at any time on your Google account's security page (Third-party apps and services).
Limited use: our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the sign-in feature you see. We never use it for advertising, never sell it to data brokers or information resellers, never use it to determine creditworthiness or for lending, and never use it to develop, improve or train artificial intelligence or machine learning models. Google user data is never sent to an artificial intelligence model.
What this website does and does not do
The pages of MyGritWall you are reading are served without cookies and without analytics or advertising trackers. Fonts and images are served from the same origin, so your browser contacts no third-party servers while loading these pages.
If you save a choice in the cookie settings, it is kept in your browser's local storage on your device only. The cookie policy lists everything the application keeps on your device and why.
Public challenge, community and recap pages show only information that its owners chose to make public.
Server logs and hosting
The website runs on infrastructure of Amazon Web Services in the EU region Frankfurt, delivered through a content delivery network. When a page is requested, technical data such as IP address, requested URL, time and user agent is processed to deliver the page, keep it secure and find faults. The legal basis is our legitimate interest in a secure and functioning website (Art. 6 (1) (f) GDPR). Server logs are kept for 90 days.
The application and your account
Buttons such as "Open in app" lead to the MyGritWall application. The application is where you create an account, run or join challenges, check in, post and message the people in your challenges. This policy covers the application as well as this website.
You must be at least 16 years old to use MyGritWall, and you confirm this when you sign up.
Your account holds your email address, your name, the display name and username you choose, your profile picture if you add one, your language and time zone, your confirmation that you are old enough to use MyGritWall, and the versions of the Terms of Use and this policy you accepted and when. We process this data to provide the service you signed up for (Art. 6 (1) (b) GDPR).
Everything you create in the application (challenges, check-ins, logged values, proof, posts, comments, reactions, messages, notifications) is stored to provide the service and shown to other people only as described under "What is shared". Organizations you belong to see what their challenges allow, never your personal challenges.
Signing in, and sign-in with Apple, Google, Microsoft or LinkedIn
You can sign in with a code we email you, with a password, with a passkey, or, where offered, with your Apple, Google, Microsoft or LinkedIn account. Sign-in is operated by Amazon Web Services (Amazon Cognito) in the EU region Frankfurt. A password is stored only there, in hashed form; we never see it.
When you sign in with Apple, Google, Microsoft or LinkedIn, that provider sends us your name, your email address, your profile picture where you have one, a stable identifier for your account with the provider and, from Google, Microsoft and LinkedIn, whether the provider has verified that email address. We ask the provider for nothing else: we do not read your contacts, calendar, files, photos or any other data of your account there.
We use what the provider sends only to create your MyGritWall account or to sign you in to it; your email address from the provider becomes the address of your account. We do not sell it, do not share it with anyone else, do not use it for advertising and do not use it to build a profile of you. The legal basis is the provision of the service you asked for (Art. 6 (1) (b) GDPR). Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can withdraw the permission at any time in your account at the provider; you then sign in to MyGritWall another way. The data the provider sent is deleted with your account.
If your organization sets up single sign-on, you sign in through your organization's identity provider, which sends us your name and work email address. Your organization decides how that provider handles your data.
To keep automated sign-ups out, signing up and signing in run a short proof-of-work check in your browser. It uses no cookies and does not track you. We also keep a list of the devices you are signed in on, so you can see them and sign them out in Settings.
Where your data is stored and who helps us process it
Your data is stored on infrastructure of Amazon Web Services in the EU region Frankfurt: the database, the storage for photos and videos and the sign-in service. The emails we send you, including sign-in codes, are sent through Amazon's email service in its US region (North Virginia); replies to our emails are received in Frankfurt. Pages and media are delivered through Amazon CloudFront, which serves copies from locations in Europe and North America. Amazon Web Services processes all of this only on our instructions under a data processing agreement (Art. 28 GDPR).
Payments are handled by Stripe. Card details are entered on Stripe's pages and never reach us; we receive confirmation of the payment and the records described under "Records of ticket sales". Organizers who sell tickets set up their payouts with Stripe, which checks their identity as the law requires; we see the status of that check, not the documents.
If you connect a Slack workspace, we send the reminders and updates you chose to that workspace, and the token for it is sealed with a dedicated key, never logged and deleted when you disconnect. What arrives in Slack is then handled under the terms of the workspace.
Push notifications you turn on are delivered through the push service of your browser or phone (Google, Apple, Mozilla or Microsoft). A push message carries only what is needed to show the notice; it never carries health values or proof, and you can hide challenge names from the lock screen in Settings.
Amazon Web Services for email and content delivery, Stripe, the sign-in providers named above, Slack and the push services may process data outside the European Economic Area. Where they do, the transfer rests on the safeguards of Chapter V GDPR, such as the EU standard contractual clauses or an adequacy decision for the provider.
How we protect your data
All connections to MyGritWall are encrypted (TLS). Your data is stored in Amazon Web Services in the EU region Frankfurt and encrypted at rest. Passwords are stored only by the sign-in service, in hashed form, and are never visible to us. Photos and other private media are reachable only through short-lived signed links. Access to the systems is limited to the operator, through a separate administration console that requires a second factor and an allow-listed network and records every view of personal data and every action in an audit log.
Export, deletion and retention
In Settings, under Privacy, you can request an export of your data and delete your account. The export is one file with your account, your participation and everything you created; photos and videos are not included as files. Its download link works for one hour, and the file is kept for seven days.
Deleting your account ends all your sessions at once and removes or anonymises your personal data across the service: your account, profile, challenges, check-ins, proof, posts, comments, messages, notifications, sign-in methods and push devices. Content you added to other people's challenges is removed or shown without your name. Records that the law requires us to keep are described under "Records of ticket sales". Before you can delete your account, you hand over or close what others depend on: an organization you own alone, a paid organization plan, a paid challenge with open money, a running group challenge or a community you own. The application tells you exactly what is left.
We keep your data for as long as your account exists, unless a shorter period is stated in this policy. We delete it when you delete your account, except where a period under "Retention" applies.
Health-related tracking in the application
Some challenges are about health, for example weight, sleep, fitness, sobriety or mood. Where the MyGritWall application treats a challenge as health-related, its check-ins, logged values, proof and posts are data concerning health. We process them only with your explicit consent (Art. 9 (2) (a) GDPR), which the application asks for once, in plain words, before you first create, join or log in a health-related challenge. While this handling is switched off, the application does not ask and no challenge is treated as health-related.
You can say no and still use MyGritWall; you only cannot log in health-related challenges. You can withdraw your consent at any time in Settings, Privacy, and choose to delete your health-related data or keep it only for you. We never sell this data and never use it for advertising. Organization admins never see your logged values.
What is shared
Only me: only you see your check-ins, values, proof and posts.
Invite only: the people invited to the challenge see your posts and your place in its progress. Designated verifiers see proof.
Organization only: members of the organization see your posts as the challenge allows. Organization admins see counts and completion rates only, never logged values. Joining an organization challenge is always voluntary, and nothing reports who did not join.
Public: anyone can see public posts, unless the owner of the challenge limits its posts to its members. Logged health values and proof are never put on a public share card unless you choose that card yourself.
You can always make one post more private than its challenge, never more public.
Joining a challenge and its rules
Some challenges ask the people who run them to approve each join. Your request (your name, profile picture, the time of the request and, if the challenge has rules, the version you accepted) is then shown to the challenge owner and its admins, and for a community or organization challenge also to the people who manage it there. They decide whether you join. You can cancel a request at any time.
When a challenge has rules, we record which version of the rules you accepted and when. The challenge owner and its admins can see this record. We process it to let you take part under the rules you accepted (Art. 6 (1) (b) GDPR). It is part of your participation: it is included in your data export and deleted with your account.
Notifications in the application
The MyGritWall application keeps a list of your notifications so you can see what happened while you were away. A notification records what happened (for example a comment on your post, a cheer, a reminder or a change to a challenge you take part in), the challenge, community or post it is about, the account that caused it where there is one, when it happened and whether you have read it. Where several people did the same thing, it keeps a count and at most two of their accounts.
We process notifications to provide the service you use (Art. 6 (1) (b) GDPR). We keep them until your account is deleted; they do not expire on their own. When the account that caused a notification is deleted, its name no longer shows.
You choose which notifications you get, and on which channel, in Settings, and you can turn off activity notifications for a single challenge or post. There is no button to delete single notifications today. Deleting your account deletes all of them; you can also ask us at support@mygritwall.com to delete them. Your notifications are included in the export of your data.
Records of ticket sales
When you buy a ticket to a paid challenge, or sell tickets as an organizer, we keep a record of each sale: the challenge, the price, tax and fees, the payment, any refund and the payout to the organizer. Tax and accounting law requires us to keep these records (Art. 6 (1) (c) GDPR).
When your account or the challenge is deleted, the sale records are kept for 10 years from then, linked only to internal ids and no longer to your name or profile, and are then deleted. A record whose money is still open (a refund or payout not yet settled) is kept at least until it settles. Until your account is deleted, your tickets and earnings are included in the export of your data.
Messages in a challenge
Members of a challenge can write to each other inside it. We store the messages, their attachments, who sent them, when, and when they were read. The members of the challenge see them; its owner, admins and editors can read the challenge chat as part of running it.
Messages and their attachments are deleted 183 days after the challenge ends. We process them to provide the service (Art. 6 (1) (b) GDPR). Messages are encrypted on the way and at rest, but not end to end.
Photos and videos
When you upload a photo or video, we remove the location and other embedded camera data before it is stored. Private media is reachable only through signed links that expire after a few minutes. Automatic screening of media is switched off; content is reviewed when someone reports it.
Organizations
If you join an organization, it sees the organization profile you keep there (name, photo and job title if you add them), your role, your seat and your activity in the organization's challenges. It never sees your personal challenges.
Reports for organization admins show counts and completion rates for groups of at least three people and never name a person. The organization's own administrators see an audit log of changes made in it. The organization is responsible for how it uses what it sees.
Public pages and sharing
A public Grit Wall and indexing of your public pages by search engines are off until you turn them on, and you can turn them off again at any time; the legal basis is your consent (Art. 6 (1) (a) GDPR).
When you share a recap, a milestone card or a certificate, the page shows what you chose to share. A certificate page shows that the certificate is valid, the challenge, the outcome and the date, and never your name.
Reports, decisions and appeals
When content or an account is reported, we store the report, the reason, an optional note, the decision, its reasons and any appeal. Reporting is limited to 20 reports a day. A report is never decided by the person it is about. You receive a statement of reasons for decisions about your content or account and can appeal within 180 days.
We process this to keep the service safe and to meet our legal obligations for online platforms (Art. 6 (1) (c) and (f) GDPR). Records of a case are kept for two years after it is closed; your own reports are included in your data export.
Paid challenges: making sure they are run
Members who hold a ticket to a paid challenge are asked a short "How's it going?" check at a few set points of the challenge: how the challenge is going for them, on a scale of five steps, and whether the organizer is there for them as promised. Answering is optional; you can dismiss the check and it is not asked again. We use the answers to protect buyers and to pay organizers only for challenges they ran. The legal basis is our legitimate interest in that protection (Art. 6 (1) (f) GDPR); you can object at any time by writing to support@mygritwall.com.
Your answers are never shown to the organizer, the challenge's admins, other members or the public, and never appear in an organizer's data export. Our operators see only counts per answer for a challenge, never who answered what. Each answer is stored without your account. A separate note that you answered or dismissed a check, with a copy of your answers, is kept for 90 days after the answer, so the check is not asked twice and your answers are in your own data export; it is then deleted, and the answer stays anonymous: the challenge, the check point and the two answers. Anonymous answers are kept as long as the organizer's account exists, as part of the history of their paid challenges, and are deleted with the challenge or the organizer's account. If you delete your account, your notes are deleted and the anonymous answers stay.
If you run a paid challenge that has sold a ticket, as its owner or an admin, we record for each day the kinds of your own activity in it, for example that you opened it, posted, decided a join request or a proof, or held a live session. We use these facts for the same purpose and on the same basis (Art. 6 (1) (f) GDPR): to remind you of what is waiting and, if the challenge needs a review, so that a person on our team can decide about the organizer's payout with the facts in front of them. No decision about a payout is taken by automated means alone; the organizer is told the reason and can reply through Help and feedback. Only our operators see these facts; your reminders name only what is waiting. They are deleted with the challenge or with your account.
A buyer holding a ticket to a paid challenge can report it with the reason "The organizer is absent", once per challenge. These reports are handled only by our own moderators, never by the moderators of a challenge or community, and the organizer's reminders and warnings never mention them. They are kept as described under "Reports, decisions and appeals".
Product metrics
The application sends no data to analytics or advertising services. On our own servers we count how features are used with pseudonymous events, and we only look at groups of at least five people. The legal basis is our legitimate interest in improving the service (Art. 6 (1) (f) GDPR); you can object at any time by writing to support@mygritwall.com.
Subscriptions and invoices
If you pay for Pro or for an organization's seats, Stripe handles the subscription and we keep the invoice records that tax and accounting law requires (Art. 6 (1) (c) GDPR). When your account is deleted, these records are kept for the legal period linked only to internal ids, not to your name or profile.
Retention
Most data is deleted when you delete your account. These records are kept longer: proof of a deletion for 90 days, proof of your consents for three years, records of reports and decisions for two years after a case is closed, and records of ticket sales for 10 years (see "Records of ticket sales").
Shorter periods: challenge messages are deleted 183 days after the challenge ends, a data export file after seven days, push devices after 90 days without use, the note of who answered a "How's it going?" check 90 days after the answer, server logs after 90 days, and check-ins waiting on your device without a connection after 14 days. Backup copies of deleted photos and videos are removed within 30 days.
Your rights
You have the right of access, rectification, erasure, restriction of processing, data portability and objection under Articles 15 to 21 GDPR. You can export and delete your data yourself in Settings, Privacy; for everything else, contact us at support@mygritwall.com.
Where we process data on the basis of your consent, you can withdraw it at any time, without affecting what happened before. Where we rely on our legitimate interest, you can object to the processing on grounds relating to your situation.
You may lodge a complaint with a supervisory authority: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany.