Privacy Policy
Last updated: 20 November 2026
This policy describes how ICLICS SRL processes the personal data of users of the TeeConnect and PopConnect applications, of the teeconnect.io and PopConnect websites, and of people who respond to an invitation without creating an account (hereinafter "the Service"). Both applications share the same infrastructure and the same rules.
It has been drawn up in accordance with Regulation (EU) 2016/679 ("GDPR") and the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data.
It also applies to people who receive a personal invitation by email because the organiser of an event has entered their address on the guest list: this case is described in point 2.6.
It also applies to people whom a participant registers as a companion (section 2.14) and to visitors who write to an organiser from the public page of their community (section 2.10).
1. Data controller
The data controller is:
- ICLICS SRL, a private limited liability company under Belgian law
- Registered office: Chemin du Beau Vallon 42, 5100 Wépion (Namur), Belgium
- Company number (CBE) / VAT: BE 0548.813.132
- Contact for your data: info@teeconnect.io
ICLICS SRL has not appointed a data protection officer, as such an appointment is not mandatory for its activities. Requests are handled directly by its manager.
Two specific situations: the contacts you record in your logbook and the notes a coach takes about their students are data that you decide to record; you are responsible for them and we process them on your behalf (see the terms of use, article "Third-party data"). Likewise, the organiser of a community is responsible for the use they make, outside the Service, of their members' information.
When an organiser asks the people registered for their event for information (company, job title, VAT number, diet…), asks them to accept the organiser's own terms, or receives messages from visitors to their public page, the organiser decides on this information and its use: the organiser is the controller, and ICLICS SRL acts on their behalf as a processor. We use this information for nothing other than what is described here.
2. Data collected and purposes
We only collect what is needed for the Service to work. Data marked "optional" is only collected if you provide it.
2.1. Account and profile
| Data | Purpose |
|---|---|
| Email address, password (stored in irreversibly encrypted form) or Google or Apple identifier | Creating the account, signing in, account-related messages |
| First name, last name, nickname, photo | Identification between members (you can choose to display only your nickname) |
| Sports played, level, handicap, club, licence, years of practice, availability, playing preferences (asked only in the spaces that use them, for example the handicap in the golf space and the level in the padel space) | Suggesting suitable partners and games |
| Country, region, languages | Finding nearby partners, clubs and communities; language of the app and emails |
| Occupation, company, company size, sector, networking goals, LinkedIn profile, introduction text (optional) | Professional networking between members |
| Date of birth, gender, phone number (optional) | Completing the profile; they are not shown to other members |
| Acceptance of the terms of use (date and version) | Proof of your consent |
The profile information you provide is visible to other members, according to your visibility settings. Your email address, date of birth, phone number and location are never displayed.
2.2. Location
If you allow access to your phone's location, the app records your location each time it is opened, rounded to about one kilometre. It is used to calculate distances: members, clubs, communities and partner offers near you. It is never shown to other members. Each new location replaces the previous one, and it is deleted along with your account. You can withdraw permission at any time in your phone's settings.
2.3. Activity in the Service
| Data | Purpose |
|---|---|
| Private messages, community messages, polls, reactions, shared documents | Enabling exchanges between members |
| Games, matches, tournaments, scores, invitations, requests to join | Organising games and keeping their history |
| Communities: membership, role, events, responses, lists, proposals | Running communities and their events |
| Coaching: bookings, assessments, the coach's notes on the student | Running lesson bookings |
| Logbook: contacts, games, reminders you record | Letting you keep track of the people you meet; this data is visible only to you |
| Favourites, blocks, reports | Personalising your experience and keeping members safe |
| Feedback and problem reports (text, optional screenshot, phone model, system and app version, language) | Handling your request and fixing defects |
2.4. Matchmaking and automatic summaries
To suggest partners who share your interests, part of your profile (level, club, country, region, sector, occupation, company, availability, preferences and introduction text, without your name or email address) is turned into a numerical representation by an artificial intelligence model, through our provider OpenRouter. Each week, we may present your first name, occupation and region to other members with a similar profile, and vice versa.
In a community, when a member has many unread messages, and for the community's weekly newsletter, the messages concerned and their authors' first names are sent to the same provider to write a short summary, shown only to members of the community.
None of these operations produces a decision that has legal effects on you: they are suggestions.
2.5. Notifications and emails
| Data | Purpose |
|---|---|
| Your device's notification identifier, language | Sending you the notifications you have accepted |
| Email address, email delivery events (delivered, rejected, unsubscribed) | Sending emails relating to your account, communities and weekly introductions, and no longer writing to an address that refuses them |
| Email address | Informing you of news about the Service; each email contains an unsubscribe link |
2.6. Responding to an invitation without an account
If you respond to an event from a link, without creating an account, we record your first name, email address, response, the number of people accompanying you and your language. The address is used only to confirm your response and to let you change or withdraw it. An unconfirmed response is deleted after 72 hours; a confirmed response is deleted six months after the date of the event, or as soon as you withdraw it. If you later create an account with the same address, the response is linked to it.
Personal invitation sent by an organiser. The organiser of an event may draw up a guest list. They enter your email address and, if they wish, your first name, last name and company. They are responsible for this list and declare that they know you and are inviting you in a personal capacity. ICLICS SRL acts on their behalf, as a processor: we send the invitation, at most two reminders at least three days apart if you have not responded and, if you sign up, the messages needed for your attendance (confirmation, change, cancellation, reminder the day before, message from the organiser). We use your address only for this event and to invite you to use the app that handles its registrations: no third-party advertising, no resale, no other use. We pass it on only to our email delivery provider (point 4).
The organiser sees whether the invitation was sent to you, whether you opened your personal link and the response you give. For the link, we record only the date it was first opened: no IP address, no browser, and the email contains no tracking image. When you respond, the page asks for your first name and, if you wish, your last name and company; they are used for the list of participants and for the badge the organiser may print.
If you answer "yes", you receive an entry ticket: a code calculated from the event and your address, which contains neither your name nor your address and which we do not store. At the entrance, the organiser or the person they have put in charge of the door reads it to record your attendance; they then see your name, your company and the number of people accompanying you.
The app and your invitation. The Service is an app that handles registration for events: the invitation therefore suggests that you download it and sign up with the invited email address. The invitation states whether you can also respond without the app; you can always decline without installing it. If you create an account with the invited address, as soon as that address is confirmed, the invitation is attached to your account: you become a member of the organiser's community and you find the event in the app. We never respond on your behalf; a response already given on the invitation page is attached to the account in the same way. If your account existed before the invitation, the app shows it to you and you join the community only if you accept it. The organiser sees that you have joined their community. This attachment is based on the organiser's legitimate interest, and ours, in your finding your invitation without having to enter it again (Art. 6.1.f). You can object to it: by not creating an account with this address, by using the "Stop receiving" link before creating your account, or by leaving the community in the app, at any time.
Every invitation contains a "Stop receiving" link. You can refuse invitations from this organiser, or from all organisers who use the Service. This refusal stops invitations, reminders, the reminder the day before and messages from the organiser; it does not stop the messages essential to a current registration (confirmation, change, cancellation, a place becoming available): to stop receiving those, withdraw your response. To apply your refusal without keeping your address in clear text, we keep for three years a fingerprint of it, calculated with a secret key (pseudonymised data). The organiser only sees that the email could not be sent to you, without knowing why. A refusal is lifted on written request to info@teeconnect.io.
This processing is based on the organiser's legitimate interest in inviting people they know (Art. 6.1.f); you can object to it as described above. The invitation, whether or not you responded to it, is deleted 30 days after the end of the event, or 90 days after it was created if the event has no date. Your response is kept for six months after the event, as stated above. The sending log, which contains neither address nor link, is kept for six months after the event. The delivery events of these emails (sent, delivered, bounced) are emptied of their content after 30 days and deleted after 90 days, except those of the email confirming your response, kept for 12 months at most (point 6); an address that bounces our emails stays for 12 months on the list of addresses we no longer write to.
You can request access to this data, its rectification or its erasure: through the management link received with your confirmation, which lets you withdraw your response and erase your address, from the organiser, or by writing to us at info@teeconnect.io from the invited address; we help the organiser respond. If that address belongs to an account, the invitations received appear in the export of your data; they are not erased with the account, but within the 30-day period above. You can also lodge a complaint with the Data Protection Authority (point 7).
2.7. Event payments
When an organiser enables online payment for an event, the payment is processed by Stripe. We send Stripe your email address and the name of the event; your card or bank account details never reach us. We keep the amount, date and status of the payment.
To receive payments, an organiser opens an account with Stripe, which asks them directly for the information required by anti-fraud and anti-money-laundering regulations: identity, date of birth, address, national identification number (in Belgium, the national register number), bank details and, where applicable, an identity document. Stripe processes this data as a separate data controller, under its own privacy policy. We neither receive nor keep this information: only the status of the account and the list of items still required by Stripe.
2.8. Audience measurement and advertising
The app uses Google Firebase Analytics to measure its use (screens opened, steps completed such as signing up or creating a game, device model, version, country), linked to a technical identifier of your account, without your name or email address.
It also uses the Meta App Events kit to measure the effectiveness of our advertising campaigns on Facebook and Instagram: installation, opening of the app, sign-up and a few key steps are sent to Meta. The app does not access your phone's advertising identifier.
You can object to these measurements by writing to us. A future version of the app will offer you a setting to refuse them directly.
2.9. Websites, maps and weather
The teeconnect.io and popconnect.netlify.app websites use neither advertising cookies nor audience measurement tools; the popway.app website is described in section 2.16. They store in your browser the language you chose and, for the organiser and administration areas, your session. The websites' host keeps technical logs (IP address, page requested, date).
The club map displays OpenStreetMap base maps: your device requests them directly from the OpenStreetMap Foundation, which receives your IP address and the area displayed. A club's weather is requested by your device from the OpenWeather service, with the club's coordinates (not yours) and your IP address.
2.10. Support, partnerships and messages to organisers
When you write to us, or fill in the partnership form on the website (name, email address, company, country, message), we use this information to reply to you.
Writing to an organiser from their public page. If the organiser has enabled it, their public page offers a "Contact the organiser" form. You enter your name, your email address and your message (2,000 characters at most). We send you a single email containing a link to confirm your address; this link is valid for 72 hours. Your message is passed on to the organiser only after this click: they receive it in the "Messages received" box of their community, with a notification, and can reply to your address. Only the organisers and co-organisers of the community have access to it. You receive no other email from us.
To prevent abuse, the number of requests is limited per address, per community and per day. To apply this limit without keeping your IP address, we compute a fingerprint of it with a key that changes every day; the fingerprint, the key and the counters are deleted the next day. Legal basis: the legitimate interest of the organiser in receiving requests that concern them, and ours in preventing abuse (Art. 6.1.f).
Messages received are deleted 12 months after receipt. If you do not confirm your request, your name and your message are deleted when the link expires; only your address and the date of the request remain, which are used for the limits and are deleted 30 days later, as for a confirmed request.
2.11. Attendance at events
The organiser of a community event may record who attended. For each person and each day, the organiser records one of these statuses: present, late, excused, absent or absent without notice, together with the number of accompanying guests who attended. The organiser may also add, by first name, a person who came without having registered. No reason for absence and no comment is recorded.
Only the organisers of the community can see this attendance and export it with the list of participants; other members cannot see it. The organiser decides whether or not to record attendance: we keep this data on the organiser's behalf. This processing is based on the organiser's legitimate interest in running their events (Art. 6(1)(f)); you may object by contacting the organiser or us. Your attendance is included in the export of your data and is deleted with your account.
2.12. Registering for an event: information, programme and terms
The organiser of an event may ask the people who register for additional information, chosen from a fixed list: company, job title, mobile number, sector, address, VAT number, size, diet (section 2.13). The organiser indicates which ones are mandatory; diet never is. This information is used only for this event and is visible only to the organisers.
The organiser may also offer a programme in several parts and ask you to choose those you will attend, and ask you to accept the organiser's own terms (a text or a PDF document). We record the version accepted, the date and a fingerprint of the accepted text, so that what you accepted can be proven. If the organiser changes their terms, you are asked to accept them again. The PDF document of the terms is published at an address that cannot be guessed, which only registered people receive.
The organiser may decide to approve each registration personally. We then record your request, the organiser's decision and, if they cancel a registration, the reason they give; this reason is included in the export of your data. Legal basis: the performance of your registration (Art. 6.1.b).
This information, the programme choices, the acceptances of terms, the registration requests and the cancellations are deleted six months after the event.
Receiving a community's next invitations. The registration form may offer a "Receive the next invitations from this community" box, unticked by default. Your consent (Art. 6.1.a) counts only once your email address has been verified. You can withdraw it at any time through the link in each invitation; a refusal always prevails over a consent. The consent is kept three years after the last invitation received from this community, or three years after the consent if it has not been used; a consent whose address was never verified is deleted after 30 days, and a withdrawn consent 30 days after its withdrawal.
2.13. Diet
A diet or dietary restriction may reveal information about your health (an allergy, for example). It is therefore recorded only if you tick the box "I agree that the organiser receives this information, for the meal only": this is your explicit consent (Art. 9.2.a GDPR). It is optional, it is visible only to the organisers of the event, it appears in no notification and it is not included in exports of the participant list.
For a companion who has no email address (a child, for example), the person who registers them may indicate their diet at their request. As soon as an address is given for them, the companion indicates it themselves on their personal page, and the information given by the person who registered them is deleted.
You withdraw your consent by unticking the box and saving, or, for a companion, with the "Delete my information" button on their personal page: the information is then deleted. In all cases, it is deleted 30 days after the event (30 days after its last change if the event has no date).
2.14. Named companions
When the organiser asks for it, the person who registers with companions gives the first name and last name of each one and, if they wish, their email address; the organiser may also ask for the information in section 2.12 for them. Each companion receives their own entry ticket: a code computed from their record, which contains neither their name nor their address. At the entrance, the organiser or the person in charge of reception scans it to record their attendance.
If an address is given, we send the companion their ticket and a link to a personal page, where they can complete or delete their information and refuse the community's emails; we also notify them if their place is cancelled or put on hold. Each of these emails names ICLICS SRL and refers to this policy. Without an address, their ticket is given to the person who registered them. We use this address for nothing else.
The person who registers a companion undertakes to inform them (see the terms of use, "Third-party data" article). This processing is based on the legitimate interest of the organiser and of that person in organising the reception of participants (Art. 6.1.f).
A companion's record, their choices and their attendance are deleted six months after the event; their diet, 30 days after it (section 2.13). Emails intended for them leave our sending queue 30 days after being sent, and the link to their personal page stops working 30 days after the event.
2.15. Photos of an event
The participants of an event may add photos to its album, after accepting the "Photos of an event" clause of the terms of use. We record the photo, who added it and when. Before upload, the app removes the hidden information from the photo: where and when it was taken, and the device model.
By default, only the participants and the organisers of the event can see the album; the organiser may open it to the whole community as long as no photo has been added. The album is never public: photos are kept in private storage, hosted in the European Union (Frankfurt) by Supabase, and are displayed only through temporary addresses. We use these photos only to display them in the album: no facial recognition, no identification of people, no transfer to an artificial intelligence provider or to a partner.
If you appear in a photo, you can have it removed yourself from within the app: it is hidden immediately for everyone, then permanently deleted after seven days unless you cancel your request. If you do not have access to the album, contact the organiser or us. The author of a photo and the organiser may delete it at any time, and any participant may report it. Our team does not browse albums: it can only display a photo that has been reported, and each display is recorded in the audit log.
Photos are deleted twelve months after the end of the event; participants are notified thirty days beforehand so that they can save the ones they want to keep. The photos you have added are also deleted with your account, and they are included in the export of your data. Legal basis: performance of the contract for the person who adds a photo (Art. 6(1)(b)); for the people photographed, the legitimate interest of the participants in sharing memories of the event (Art. 6(1)(f)), to which you may object at any time through the removal described above.
2.16. The popway.app website: waiting list, audience measurement and advertising
popway.app presents Popway, the new name of the app. It counts visits with Umami, a free tool run by iClics that stores no cookie and no data at all on your device: pages viewed, clicks, language, device type, country derived from the IP address and the campaign the visit came from. This count relies on our legitimate interest in knowing how the site is used (Art. 6(1)(f)).
Only with your consent, given in the site's banner and purpose by purpose: Google Analytics (audience measurement) and Google Ads, the Meta Pixel and the LinkedIn Insight Tag (knowing whether an ad led to a waiting-list sign-up or a click to an app store). These tools set the cookies listed, with their duration, on the popway.app cookie page. Legal basis: your consent (Art. 6(1)(a)). Your choice is kept for six months in your browser; you can withdraw it at any time through the “Manage cookies” link at the bottom of every page, and the cookies concerned are then deleted.
The “Notify me at launch” form collects your first name, your e-mail address, the type and size of your group, the tools you use, an optional message, the page language and the campaign the visit came from. It is used only to let you know when Popway opens and to understand what groups need. Legal basis: your consent (tick box). Answers are kept until Popway opens to everyone, then for twelve months at most; write to contact@popway.app to see them or have them deleted.
2.17. Children's profiles
Children's profiles. A parent or legal guardian may create, from their own account, the profile of a minor child in order to register them in a club's teams. The child has no account and does not use Popway: the parent replies on their behalf. By creating this profile, you confirm that you are the child's parent or legal guardian. A second parent may be linked to the same profile.
Data stored. The first name (or a nickname), optionally the initial of the surname and the year of birth, the child's teams, and their replies, call-ups and attendance. We never ask for the full date of birth, address, health data or a photo.
Who sees it. The parents linked to the child; the managers, coaches and team officials of the child's teams; and, for the first name and initial only, the other families of those teams in the attendance list and the call-up. A child's data is never visible outside their teams, nor suggested in any search. For this data, the club is the controller and iClics SRL acts as processor.
Photos. A child's profile has no photo. A team's album, if enabled, only shows a child's picture with the consent given by their parent.
Retention. The profile is kept as long as a parent keeps it. A child's replies and attendance are erased 24 months after the event; the link to an archived team is removed 12 months after archiving.
Parents' rights. At any time you can view, correct, export or erase your child's profile from "My children", or remove them from a team. Questions: info@teeconnect.io. You may lodge a complaint with the Belgian Data Protection Authority.
2.18. Phone calendar and imported tickets
Add to my calendar. The “Add to my calendar” button opens your phone's calendar, pre-filled with the name, date, time and place of the event. You confirm the addition yourself, and we receive nothing in return.
Clash warning. If you turn on this option in the settings (it is off by default) and allow access to your phone's calendar, the app compares Popway events with your appointments to warn you of an overlap. This comparison takes place on your phone: your appointments are not sent to us.
“Only when I'm free”. If you turn on this option in the player call settings (it is off by default), the app sends us, when it is opened and at most once an hour, the start and end of the busy periods in your calendar for the next 30 days. Never the title, place, attendees or notes of your appointments; all-day events and appointments marked “free” are not sent. These periods are used solely to avoid alerting you to a search for a player at a time when you are busy, and are never shown to another member. Each upload replaces the previous one; everything is erased when you turn off the option or delete your account. You can also withdraw access to the calendar in your phone's settings.
Imported tickets and Apple Wallet. Tickets bought elsewhere that you import into your wallet (photo, image or PDF) stay on your phone: they are not sent to us. When you add a Popway ticket to Apple Wallet, our servers produce this ticket from the information on your Popway ticket, and it is then kept by Apple Wallet on your phone.
3. Legal bases
- Performance of the contract (Art. 6(1)(b)): account, profile, messaging, games, communities, coaching, logbook, matchmaking, notifications and emails relating to the Service, responses to invitations, payments.
- Consent (Art. 6(1)(a)): location, device notifications, the "Partner events" option, phone calendar (clash warning and the “only when I'm free” option, section 2.18), optional profile data. You can withdraw it at any time.
- Legitimate interest (Art. 6(1)(f)): security and abuse prevention, weekly summaries and introductions, informational emails to members, audience measurement and measurement of our campaigns, handling of support and partnership requests. You can object to it.
- Legal obligation (Art. 6(1)(c)): retention of accounting records relating to payments, responses to the authorities.
The legal bases for attendance at events and for the photo album of an event are set out in sections 2.11 and 2.15.
The legal basis for personal invitations sent by an organiser is set out in point 2.6.
The legal bases for the information requested at registration, for diets, for named companions and for messages to organisers are set out in sections 2.10, 2.12, 2.13 and 2.14.
4. Who receives your data
We never sell your data. It is visible to other members to the extent described in section 2, and to the organiser of a community as regards its members and events. We use the following providers, each bound by contractual commitments in accordance with Article 28 of the GDPR:
| Provider | Role | Location |
|---|---|---|
| Supabase, Inc. | Database, authentication, photo storage, server functions | European Union (Frankfurt); US company |
| Netlify, Inc. | Website hosting | United States, global network |
| Resend, Inc. | Sending emails | United States |
| Google (Firebase) | Notifications on Android and iPhone, audience measurement | United States and European Union |
| Google and Apple | Sign-in with a Google or Apple account (if you choose it), notifications on iPhone | United States |
| Meta Platforms Ireland Ltd | Measurement of advertising campaigns | Ireland and United States |
| OpenRouter, Inc. and the model provider (OpenAI) | Numerical representation of the profile, discussion summaries | United States |
| Stripe Payments Europe, Ltd | Event payments (when enabled) | Ireland and United States |
| OpenStreetMap Foundation | Base maps | United Kingdom |
| OpenWeather Ltd | Club weather | United Kingdom |
| Shorebird, Inc. | Corrective updates of the app (IP address, app version, anonymous installation identifier) | United States |
| Google Ireland Ltd | Audience measurement (Google Analytics) and ad measurement (Google Ads) on popway.app, with your consent | Ireland and United States |
| LinkedIn Ireland Unlimited Company | Measurement of LinkedIn ads on popway.app, with your consent | Ireland and United States |
| Vercel, Inc. and Neon, Inc. | Hosting of iClics' Umami measurement tool (popway.app) | United States |
We may also disclose data to an authority that legally requires it.
5. Transfers outside the European Union
Our database is hosted in the European Union. Some of the providers listed above are established in the United States or process data there. These transfers are governed by the standard contractual clauses adopted by the European Commission and, where the provider is certified under it, by the EU-US Data Privacy Framework. The United Kingdom benefits from an adequacy decision of the European Commission.
6. Retention periods
- Account, profile, activity and messages sent: for as long as your account exists. When you delete your account, this data is erased immediately; the host's backup copies then disappear through rotation, within 30 days at most.
- Location: replaced at each update, erased with the account.
- Calendar busy periods: replaced at each upload, limited to the next 30 days, erased when you turn off the option or delete your account.
- Responses to an invitation without an account: 72 hours if they are not confirmed; six months after the date of the event if they are.
- Attendance at events: twelve months after the end of the event; six months for people added on site by their first name and for guests without an account.
- Photos of an event: twelve months after the end of the event, with a notice thirty days beforehand; seven days after a removal request; deleted with the account of the person who added them.
- Reports and moderation decisions (warning, suspension): a report is kept until the account of the person who made it, or of the person reported, is deleted; a moderation decision is kept until the account concerned is deleted.
- Payments: for the period required by Belgian accounting and tax legislation.
- Technical logs, sign-in log and audit log: 12 months at most.
- Audience measurement: 14 months at most at Google Firebase; at Meta, according to its own retention rules.
- Exchanges with support and partnership requests: the time needed to handle the request, then 3 years at most.
- Personal invitation sent by an organiser: 30 days after the end of the event, or 90 days after it was created if the event has no date; sending log, without address: six months after the event; delivery events of these emails: content erased after 30 days, deleted after 90 days (email confirming a response: 12 months at most); address that bounces our emails: 12 months.
- Refusal to receive invitations: three years, in pseudonymised form.
- Information requested at registration, programme choices, acceptances of terms, registration requests and cancellations: six months after the event.
- Diet: 30 days after the event, or as soon as consent is withdrawn.
- Named companions: six months after the event; emails in the sending queue: 30 days.
- Messages to organisers: 12 months after receipt; name and message of an unconfirmed request: when the link expires (72 hours); address and date of the request: 30 days; fingerprint of the IP address: deleted the next day.
- Consent to receive a community's next invitations: three years after the last invitation received (or after the consent if it has not been used); 30 days if it was never confirmed, or after its withdrawal.
- popway.app website: cookie choice, six months; Google Analytics cookies, thirteen months; Google Ads and Meta, ninety days; LinkedIn, one year at most. Umami keeps no identifier that recognises you from one month to the next. Waiting-list sign-ups: until Popway opens to everyone, then twelve months at most.
7. Your rights
You have the following rights:
- Access and portability (Art. 15 and 20): on simple request to info@teeconnect.io, from your account's address, we provide you with all your data in a structured, reusable file (JSON). The export also includes the information you gave when registering for an event, the terms you accepted, your consents to receive invitations, and the records of the companions you registered or who designate you by your address.
- Rectification (Art. 16): directly from your profile, or by writing to us.
- Erasure (Art. 17): from the app (Profile, then "Delete my account"), from the page teeconnect.io/en/delete-account, or by writing to us.
- Objection (Art. 21): to processing based on our legitimate interest, including audience measurement and informational emails (unsubscribe link in each email).
- Restriction (Art. 18): in the cases provided for by the GDPR.
- Withdrawal of consent: at any time, in your phone's settings (location, notifications) or in your profile, without affecting what was done before.
We reply within one month. If your data appears in a member's logbook or in a community, you can contact that member or the organiser, or us directly: we will help them handle your request.
You can lodge a complaint with the Data Protection Authority, Rue de la Presse 35, 1000 Brussels (www.dataprotectionauthority.be), or with the authority of your country of residence.
8. Our team's access to your data
Our team only accesses your data to run the Service, handle a request you send us, moderate reported content or ensure security. Sensitive operations (change of rights, assignment of a moderator or administrator role, data export, account deletion, changes to the legal texts) are recorded in an audit log, without your name or address. Tests are carried out on test accounts, never on yours.
9. Security
- Encryption of exchanges (TLS) and of stored data
- Passwords stored in irreversibly encrypted form
- Access rules in the database: each member only accesses what concerns them
- Limited and logged administrative access
- Hosting with Supabase on SOC 2 certified infrastructure
In the event of a data breach posing a risk to you, we notify the Data Protection Authority within 72 hours and, if the risk is high, the people concerned. Any breach discovered is recorded in our incident register, even if it has no consequences.
10. Minimum age
The Service is reserved for people aged 16 or over. If we learn that an account belongs to a younger person, we delete it.
11. Changes
We may change this policy to reflect changes to the Service or to regulations. The date of the last update appears at the top of the page. Any significant change will be announced to you in the app or by email.
12. Contact
- Email: info@teeconnect.io
- Post: ICLICS SRL, Chemin du Beau Vallon 42, 5100 Wépion, Belgium
- Subject: "Data protection — [your request]"