Snapshot 45647
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Privacy & Policy We care about your privacy We only save your data for as long as it is needed, and only share it with other parties if this is needed for using the app. Our business model only consists of improving events using our app and therefore we have no commercial interest in the data. Everything is saved securely and sent via a secure SSL connection. Privacy Policy Let's Get Digital B.V., located at Atoomweg 2-H, 9743 AK Groningen, is responsible for the processing of personal data as shown in this privacy statement. Contact details: Let's Get Digital Atoomweg 2-H 9743 AK, Groningen +31502113693 Bas Krijgsman is the Data Protection Officer of Let's Get Digital. He is contactable via +31502113693. Personal data that we may process Let's Get Digital processes your personal data because you use our services and/or because you provide this information to us. Below is an overview of the personal data that we may process: First and last name Date of birth Address details Telephone number Email address IP address Other personal data that you actively provide, for example by creating a profile on this website/app, in correspondence and by telephone Internet browser and type of device Special and/or sensitive personal data that we process Our website/app and/or service does not intend to collect data about website/app visitors who are younger than 16 years of age, unless they have permission from parents or guardians. However, we cannot check if a visitor is older than 16. We encourage parents to be involved in the online activities of their children, to prevent data about children being collected without parental consent. If you are convinced that we have collected personal information about a minor without consent, please contact us via +31502113693, and then we will delete this information. For what purpose and on what basis do we process personal data Let's Get Digital processes your data for the following purposes: To give you the opportunity to create an account in the app and to communicate with other users How long we save personal data for Let's Get Digital does not save your personal data for any longer than strictly necessary to achieve the goals for which your data is collected. Sharing personal data with third parties Let's Get Digital will not sell your information to third parties and will only provide this information if this is necessary for the execution of our agreement with you or to comply with a legal obligation. With companies that process your data in our assignment, we conclude a processor agreement to ensure the same level of security and confidentiality of your data. Let's Get Digital remains responsible for these processing operations such as cookies or similar techniques that we use. Let's Get Digital only uses technical and functional cookies and analytical cookies that do not infringe on your privacy. A cookie is a small text file that is stored on your computer, tablet, or smartphone during your first visit to the website/app. The cookies that we use are necessary for the technical operation of the website/app and your ease of use. They ensure that the website/app works properly, and they remember, for example, your preferences. We can also optimize our website/app with this. You can opt out of cookies by setting your internet browser so that it no longer stores cookies. In addition, you can also delete all the information previously saved via your browser settings. How we secure data Let's Get Digital takes the protection of your data seriously and takes appropriate measures to prevent misuse, loss, unauthorized access, unwanted disclosure, and unauthorized modification. If you feel that your data is not properly secured and/or that there are indications of abuse, please contact us. Third parties Let’s Get Digital aims to protect your privacy by requiring as little data as possible to operate the features of the Let’s Get Digital app and LGD white label apps, in addition to the Let’s Get Digital Virtual Event platform. The primary domain used by Let’s Get Digital to host content is live.letsgetdigital.com. Information sent to this domain is required for the functionality of the respective features of the apps and platforms operated by Let’s Get Digital. Below is a complete overview of all of the data that can be sent to the internet, to operate our platform. Most of the data relating to user customisation and user created content is opt-in (i.e. you do not have to set your profile picture), and users have the right to request that their account (and related data) is destroyed. Hosting & Infrastructure TransIP Legal name: TransIP B.V. Country of HQ: Netherlands Where Data Is Processed: EU data centers Data Categories: All platform data stored/served (user details, content, etc.) When/Why: Continuous hosting Transfer Mechanism: None (remains in the EEA) DigitalOcean Legal name: DigitalOcean Holdings, Inc. Country of HQ: United States Where Data Is Processed: EU data centers Data Categories: All platform data stored/served (user details, content, etc.) When/Why: Continuous hosting Transfer Mechanism: None (remains in the EEA) Amazon Web Services (AWS) Legal name: Amazon Web Services, Inc. Country of HQ: United States Where Data Is Processed: EU data centers Data Categories: All platform data stored/served (user details, content, etc.) When/Why: Continuous hosting, redundancy, backup Transfer Mechanism: None (remains in the EEA) Real-time Database/Chat Google Cloud / Firebase Firestore Legal name: Google LLC Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: Chat message contents and metadata When/Why: Whenever users send/receive chat messages Transfer Mechanism: SCCs Push Notifications Google Cloud / Firebase Cloud Messaging Legal name: Google LLC Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: Push message contents, Device tokens, minimal notification routing data When/Why: Sending push notifications (app updates, reminders) Transfer Mechanism: SCCs Apple Push Notification Service (APNs) Legal name: Apple Inc. Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: Push message contents, Device tokens, minimal routing data When/Why: Sending push notifications to iOS devices Transfer Mechanism: SCCs Media Storage Google Cloud / Firebase Cloud Storage Legal name: Google LLC Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: User-generated content (images, videos, files) When/Why: Whenever users upload media or files Transfer Mechanism: SCCs Backups Amazon S3 (Backups) Legal name: Amazon Web Services, Inc. Country of HQ: United States Where Data Is Processed: EU data centers Data Categories: Database backups (may include all user data) When/Why: Regular backup for data recovery Transfer Mechanism: None (remains in the EEA) Image Optimization ImageKit Legal name: ImageKit Private Limited Country of HQ: India Where Data Is Processed: Global CDN nodes, incl. EU; caching/routing may occur worldwide Data Categories: IP addresses (for optimization), uploaded/served images When/Why: On-demand image resizing, optimization Transfer Mechanism: SCCs Email SendGrid (by Twilio) Legal name: SendGrid, Inc. Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: Email addresses, email content/metadata When/Why: Sending emails (login links, invitations, notifications) Transfer Mechanism: SCCs SendPro (by Spotler) Legal name: Spotler B.V. Country of HQ: Netherlands Where Data Is Processed: EU data centers Data Categories: Email addresses, email content/metadata When/Why: Sending emails (login links, invitations, notifications) Transfer Mechanism: None (remains in the EEA) SMS Twilio SMS Legal name: Twilio Inc. Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: Phone numbers, SMS content, delivery metadata When/Why: Sending SMS (app links, login codes) Transfer Mechanism: SCCs CDN / DDoS Protection Cloudflare Legal name: Cloudflare, Inc. Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: IP addresses, network traffic data When/Why: Website acceleration, DDoS protection Transfer Mechanism: SCCs Streaming Services YouTube (Google LLC) Legal name: Google LLC Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: IP addresses, device info, usage data (playback, etc.) When/Why: Playing embedded videos, live streams Transfer Mechanism: SCCs Vimeo Legal name: Vimeo, Inc. Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: IP addresses, device info, usage data (playback, etc.) When/Why: Viewing embedded Vimeo videos Transfer Mechanism: SCCs Daily.co Legal name: Daily.co Country of HQ: United States Where Data Is Processed: Global infrastructure Data Categories: User details, IP addresses, video/audio streaming data When/Why: If the online platform is used. Real-time video calls / live streams Transfer Mechanism: SCCs Digital Samba Legal name: Digital Samba Country of HQ: Barcelona Where Data Is Processed: EU data centers Data Categories: User details, IP addresses, video/audio streaming data When/Why: If the online platform is used. Real-time video conferencing / streaming Transfer Mechanism: None (remains in the EEA) Error Logging Sentry Legal name: Functional Software, Inc. (dba Sentry) Country of HQ: United States Where Data Is Processed: EU data centers Data Categories: IP address, error logs, stack traces, limited user data if included in logs When/Why: Capturing application/server errors Transfer Mechanism: None (remains in the EEA) Third Parties / Integrations HubSpot Legal name: HubSpot, Inc. Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: Registration details, user data When/Why: If organisation activated this integration. Data sync for CRM, marketing, event follow-up Transfer Mechanism: SCCs Eventbrite Legal name: Eventbrite, Inc. Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: Registration details, user data When/Why: If organisation activated this integration. Event management platform integration Transfer Mechanism: SCCs Aanmelder.nl Legal name: Aanmelder.nl B.V. Country of HQ: Netherlands Where Data Is Processed: EU data centers Data Categories: Registration details, user data When/Why: If organisation activated this integration. Event registration and ticketing Transfer Mechanism: None (remains in the EEA) Summit Legal name: Summit Registration & Services B.V. Country of HQ: Netherlands Where Data Is Processed: EU data centers Data Categories: Registration details, user data When/Why: If organisation activated this integration. Event registration and ticketing Transfer Mechanism: None (remains in the EEA) vivenu Legal name: vivenu GmbH Country of HQ: Germany Where Data Is Processed: EU data centers Data Categories: Registration details, user data When/Why: If organisation activated this integration. Event registration and ticketing Transfer Mechanism: None (remains in the EEA) Zapier Legal name: Zapier, Inc. Country of HQ: United States Where Data Is Processed: Typically EU data centers; Global hosting possible Data Categories: Various user data, depending on workflows When/Why: If organisation activated this integration. Automating data sync between apps Transfer Mechanism: SCCs Weeztix Legal name: Weeztix B.V. Country of HQ: Netherlands Where Data Is Processed: EU data centers Data Categories: Registration details, user data When/Why: If organisation activated this integration. Event registration and ticketing Transfer Mechanism: None (remains in the EEA) Stripe Payments / Stripe Connect Legal name: Stripe Technology Europe,Limited Country of HQ: Ireland (parent company in the United States) Where Data Is Processed: Primarily EU data centers; global processing possible Data Categories: Customer details, payment tokens, transaction data, fraud-prevention metadata When/Why: If organiser use Stripe Connect: Payment processing, account onboarding/KYC, payouts, fraud detection Transfer Mechanism: SCCs (Standard Contractual Clauses) View, modify or delete data You have the right to view, correct or delete your personal data. You can do this yourself through your account settings. You also have the right to withdraw your consent to the data processing or to object to the processing of your personal data by our company and you have the right to data portability. This means that you can submit a request to us to send the personal information we hold to you, or another organization mentioned by you, in a computer file. If you want to use your right of objection and/or right to data portability or if you have other questions or comments about the data processing, please send a specified request to [email protected]. To ensure that the request for access has been made by you, we ask you to send a copy of your identity document with the request. Make your passport photo, MRZ (machine readable zone, the strip with numbers at the bottom of the passport), passport number and Citizen Service Number black in this copy. This is to protect your privacy. Let's Get Digital will respond to your request as soon as possible, always within four weeks. Let's Get Digital also wants to point out that you have the opportunity to file a complaint with the national supervisory authority, the Dutch Data Protection Authority. This can be done via the following link: https://autoriteitpersoonsgegevens.nl/nl/contact-met-de-autoriteit-persoonsgegevens/tip-ons Terms of use / EULA To use our software, you agree to our Terms of use / EULA (https://www.letsgetdigital.com/terms). We maintain a zero-tolerance policy for objectionable content and abusive behavior. Users are expected to act respectfully at all times. Any violations may result in immediate removal of content and suspension or banning of the user. Reports of inappropriate content are reviewed within 24 hours.