Vriendi Privacy Policy

Archived version. This privacy policy (version dated 30 October 2026) was in force from 30 October 2026 to 2 November 2026 and has been replaced by a newer version. Marketing consents recorded with version "2026-10-30" refer to this version. Current privacy policy: vriendi.com/en/privacy-policy.

Version dated: 30 October 2026

This is an English translation of the Polish privacy policy for convenience only. In case of any discrepancy, the Polish version is legally binding.

§1. Data controller

  1. The controller of personal data processed in connection with the use of the Vriendi service (vriendi.com) is Chillsoft Tomasz Mańka, a Polish sole proprietorship, NIP (tax ID): 8992843377, registered at: Wspólna 53, 42-713 Kochcice, Poland, hereinafter the "Controller".
  2. The Controller can be contacted regarding personal data protection matters at: hello@vriendi.com.

§2. What data we collect

  1. In connection with booking and paying for event participation, we process: first name, email address, age (stored as year of birth), the city, format and date of the event, and the booking's history: its status (including bookings started but not paid), amount, payment identifiers, the version and date of acceptance of the terms, attendance confirmation, notice of absence, date changes, and which email a repeat booking came from. Optionally, we process a senior card number and a discount code, if provided. We collect this data directly from the user in the booking form on the site. Payment card details and other payment details are collected exclusively by the payment processor Stripe.
  2. When a payment is started, we also process the IP address, browser and device information (user agent) and, if available, analytics and advertising identifiers (details in §6). This data is also stored in the payment's metadata in Stripe's system.
  3. We may also process information about unannounced absence or breaches of the terms, and about a temporary participation block (§6 of the Terms).
  4. In connection with the contact form available on the site, we process: first name, email address, and the content of the message sent.
  5. In connection with signing up for the waitlist, we process the data provided in the Tally form: first name, email address, city and any suggestions sent. In connection with Tally surveys, we process the answers given in them.
  6. If the user consents to receiving marketing information, we also record the first name, email address, date, IP address, source of the consent and Privacy Policy version and, if consent is withdrawn, the date of withdrawal.
  7. In connection with sending emails, we process data on their delivery, opening and link clicks.
  8. Automatically, through cookies, similar technologies and cookieless signals, we collect data about how the service is used (including pages visited and events in the booking process) - details in §6.
  9. Providing data is voluntary, but first name, email address and age are necessary to make a booking, and an email address is also necessary to receive a reply to a message or to join the waitlist. A senior card number, a discount code and marketing consent are not required.

§3. Purposes and legal basis for processing

  1. Data is processed for the purpose of:
    • entering into and performing an agreement for participation in an event, including handling payment, forming groups by age, date changes and refunds - based on Art. 6(1)(b) GDPR,
    • responding to a message sent via the contact form or a waitlist sign-up - based on Art. 6(1)(b) and (f) GDPR,
    • organizational communication with participants before and after the event (including reminders, venue information and a link to the meeting's WhatsApp group) - based on Art. 6(1)(b) and (f) GDPR,
    • sending emails about our services to people who have started or made a booking (including reminders about an unfinished booking, invitations to further meetings, invitations to WhatsApp groups and requests for a review) - based on Art. 6(1)(f) GDPR (the Controller's legitimate interest in direct marketing of its own services). These emails can be stopped at any time using the link in the email footer or by writing to hello@vriendi.com,
    • sending the newsletter and information about new events and promotions to people who have consented to it - based on Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law of 12 July 2024, and keeping proof that consent was given and withdrawn - based on Art. 6(1)(f) GDPR,
    • analyzing surveys and feedback and improving our services - based on Art. 6(1)(f) GDPR,
    • keeping meetings orderly, including applying a temporary participation block under the Terms - based on Art. 6(1)(f) GDPR,
    • issuing accounting documents and tax settlements - based on Art. 6(1)(c) GDPR (legal obligation),
    • establishing, pursuing or defending against claims - based on Art. 6(1)(f) GDPR,
    • analyzing site traffic, measuring ad performance and optimizing ad campaigns - based on Art. 6(1)(f) GDPR and, for cookies and similar technologies necessary for this purpose, based on consent given in accordance with Art. 399 of the Polish Electronic Communications Law of 12 July 2024.
  2. We do not make decisions based solely on automated processing that produce legal effects concerning the user or similarly significantly affect them. Decisions on forming groups and on blocks are made by a person.

§4. Recipients of data

  1. Personal data may be shared with entities that support the operation of the service, to the extent necessary:
    • Stripe - online payment processing,
    • Render - hosting of the booking system and database (servers in Frankfurt, EU),
    • Brevo - sending emails and data on their delivery, opening and clicks,
    • Google (Google Analytics) - visit statistics, and Gmail, Google Drive and Google Sheets - handling correspondence and documents,
    • Microsoft (Microsoft Clarity) - analyzing how the site is used,
    • Meta (Meta Pixel, Conversions API) - measuring ad performance and optimizing campaigns,
    • Tally.so - handling the waitlist and survey forms,
    • Netlify - website hosting,
    • Anthropic (Claude) - an AI tool supporting operations and data analysis,
    • Notion - internal organizational notes,
    • the provider of the hello@vriendi.com mailbox - handling correspondence,
    • an accounting firm - bookkeeping and tax settlements.
  2. Data may also be disclosed to public authorities where required by law.
  3. Joining a WhatsApp group or community is voluntary and happens through a link. That service is provided by WhatsApp (part of Meta) under its own terms, and the user's phone number and profile may be visible to other group members and to the group's administrator.
  4. Some of the above entities may process data outside the European Economic Area (including in the USA). In such cases, the transfer relies on mechanisms ensuring an adequate level of data protection, in particular a European Commission adequacy decision or standard contractual clauses approved by the European Commission.
  5. The Controller does not sell personal data or share it with third parties for purposes other than those described in this Policy.

§5. Data retention period

  1. Data related to a paid booking is stored for the duration of the service, and afterwards for the period required by tax and accounting law (generally 5 years, counted from the end of the year in which the transaction took place) and until any claims become time-barred.
  2. Data of a booking that was started but not paid is stored for no longer than 12 months from when it was started.
  3. Data from the contact form, waitlist and surveys is stored for as long as necessary to respond to and handle the inquiry, no longer than 12 months from the last contact, unless an objection or a deletion request is submitted earlier.
  4. Data processed on the basis of consent is stored until consent is withdrawn. Proof that consent was given and withdrawn, and information that someone opted out of emails, is kept until any claims become time-barred, so that we can demonstrate compliance and do not email people who opted out again.
  5. Data processed on the basis of legitimate interest is stored until an effective objection is made, but no longer than the periods indicated above.
  6. Technical system logs, which may contain data sent in forms (including an email address and message content), are stored for the retention period set at the hosting provider, no longer than 90 days.
  7. The storage period of cookies is indicated in §6. Data collected by analytics and advertising tools is stored in line with those tools' settings.

§6. Cookies and analytics tools

  1. The service uses cookies and similar technologies to ensure the site works correctly, to track visit statistics, and to measure the effectiveness of marketing activities.
  2. The service uses, in particular: Google Analytics (visit statistics), Microsoft Clarity (analyzing how the site is used) and Meta Pixel (measuring the performance of ads on Facebook and Instagram). The standard storage period of these tools' cookies is: _ga and _ga_* - up to 2 years, _fbp and _fbc - up to 90 days, _clck - up to 1 year, _clsk - up to 1 day. These tools may receive the address of the page visited, including its parameters.
  3. On their first visit, users can accept or decline analytics and marketing cookies using a banner. The choice is remembered in the browser's storage (localStorage) until the site data is cleared, so the banner is not shown again. Consent can be withdrawn at any time by clearing the vriendi.com site data in the browser settings (the banner will then reappear) or by writing to hello@vriendi.com.
  4. Google Analytics runs in Google Consent Mode (version 2). The Google Analytics script loads on every visit, but until the user gives consent it does not store cookies or any other identifiers on their device and only sends Google cookieless signals about page views and events on the site. Google uses them to estimate statistics in aggregated form. Once consent is given, Google Analytics stores analytics cookies (including _ga).
  5. After a purchase, the Controller sends Google, directly from its server, information about the purchase (payment identifier, value, event, city, booking method) and about the device and browser. Without cookie consent, this information is sent under a one-off, random identifier. Once consent is given, it is linked with Google Analytics identifiers to attribute the purchase to the visit and its source.
  6. Meta Pixel is loaded only after consent is given. Without consent, the Meta script is not loaded and stores no cookies.
  7. Microsoft Clarity is loaded only after consent is given. It records how the site is used (including cursor movements, clicks, scrolling and pages visited), which lets us create heatmaps and session replays used to improve the service. Text typed into form fields is masked and not sent to Microsoft, and payment details are never accessible to this tool (they are handled by Stripe). Session replays may include text visible on the page, e.g. a first name on a booking page opened from a link in an email. Clarity stores analytics cookies (including _clck, _clsk). Without consent, the script is not loaded and stores no cookies.
  8. Regardless of cookie consent, when a payment is started, payment details are provided and a purchase is completed, the Controller sends Meta, directly from its server (Meta Conversions API), information about the event (including its type, the event booked and its value) together with a one-way encrypted (SHA-256) email address, first name and customer identifier, as well as the IP address, browser information (user agent) and, if available, Meta identifiers: _fbp and _fbc (after consent) and the ad click identifier (fbclid) from the page address (also without consent). This data lets Meta match the event to a specific account, so it is personal data. The purpose is measuring ad performance and optimizing campaigns, and the legal basis is the Controller's legitimate interest (Art. 6(1)(f) GDPR). Objections to this processing can be sent to hello@vriendi.com.
  9. Users can manage cookies at any time through their web browser's settings, including deleting stored cookies and blocking future ones. Restricting cookies may affect some of the site's functionality.

§7. User rights

  1. The data subject has the right to: access their data, rectify it, erase it, restrict its processing, transfer it, and object to processing based on the Controller's legitimate interest.
  2. An objection to processing for direct marketing can be made at any time and without giving a reason. Once it is made, the data will no longer be processed for that purpose. Simply click the opt-out link in the email footer or write to hello@vriendi.com.
  3. Where processing is based on consent (e.g. the newsletter, certain cookies), the data subject has the right to withdraw it at any time, without affecting the lawfulness of processing carried out before its withdrawal.
  4. Requests regarding the above rights should be sent to: hello@vriendi.com.
  5. The data subject has the right to lodge a complaint with the President of the Polish Personal Data Protection Office (ul. Stawki 2, 00-193 Warsaw, Poland) if they believe that data processing violates GDPR.

§8. Data security

  1. The Controller applies appropriate technical and organizational measures to protect personal data being processed, including against access by unauthorized persons.
  2. The Controller does not store Participants' card details or other sensitive financial data - this data is processed exclusively by the payment processor Stripe.

§9. Changes to this Privacy Policy

  1. The Controller reserves the right to amend this Privacy Policy, in particular in connection with changes to the law or to how the service operates.
  2. The current version of the Privacy Policy is always available at vriendi.com/polityka-prywatnosci (Polish) and vriendi.com/en/privacy-policy (English).

§10. Contact

  1. Any questions regarding this Privacy Policy and personal data processing should be sent to: hello@vriendi.com.