Privacy Policy
Last updated: 2026-04-02 · contact@blinkbeam.one
Use of data
BlinkBeam SQL Academy uses personal data to operate training programs, community access, and billing-related correspondence for Korea-based learners and international attendees. Processing supports scheduling, safety, and quality standards obligations we publish elsewhere. We do not sell personal data, and we do not use it for unrelated advertising profiles. When you contact moderators, message content is stored only as long as needed to resolve the thread or satisfy operational retention rules described below.
Retention
Account data is retained while your membership is active and for a limited cooling period afterward so you can reactivate without losing history. Forum posts remain unless you request removal and removal is compatible with other members’ rights to quoted context. Server logs with technical identifiers are rotated on a short cycle unless a security investigation requires longer retention, in which case access is tightly scoped.
Data collected
We collect identifiers you provide (name, email, company where supplied), technical data from your browser (language, approximate region derived from IP for session routing), and content you submit in forms or forums. Workshop recordings capture voice if you enable your microphone; we never record without explicit session consent banners. Order references processed through external service providers, if ever used, are minimized to reconciliation identifiers rather than full account numbers.
Contact
Questions about this policy should be emailed to contact@blinkbeam.one with the subject line “Privacy inquiry”. We respond within a reasonable period under Korean and applicable cross-border practice. If you prefer postal correspondence, use the mailing address published on the contact page in Seoul. For data rights requests, include enough detail for us to verify your identity without over-collecting sensitive documents.
Third parties
We rely on subprocessors for email delivery, video conferencing, and static hosting. Each subprocessor is bound by contracts requiring confidentiality and purpose limitation. If a vendor changes regions for processing, we update this page and notify active members when the change materially affects risk. We do not allow subprocessors to use your learning content to train public models.
Scope
This policy covers blinkbeam.one and community experiences we operate under the same brand. It does not cover third-party repositories, sponsor tools, or employer systems you choose to connect during labs. Corporate workshop customers may have supplemental data processing agreements that narrow or expand certain articles—those agreements control where they explicitly differ.
Rights
Depending on your residency, you may request access, correction, deletion, restriction, or portability of certain data. Some requests may be limited where we must retain information for security, legal compliance, or contractual reconciliation. You may lodge a concern with a competent supervisory authority where applicable law allows. We will not retaliate against you for exercising privacy rights in good faith.
Policy updates
We revise this policy when our processing activities or vendors change in a meaningful way. Material updates receive a summary at the top for thirty days. Continued use of the community after the effective date constitutes acceptance of reasonable non-material edits. If you disagree with a material change, you may close your account and request deletion subject to retention rules above.
Cookie specifics also appear inside the Cookie Notice on the imprint page.