Skip to content

Stokontrol

Privacy

Clear, limited processing for account data.

This notice explains what the account-registration and paid-purchase flow collects, why it is used and who to contact about your rights.

Controller and contact

The data controller for Stokontrol is Doğuş Sevinç. Privacy and personal-data requests may be sent to info@stokontrol.com or Yakuplu Mahallesi, 176. Sokak No: 6, Daire: 27, Beylikdüzü / Istanbul, Türkiye.

Data and purpose

Full name, individual or organisation name, email, optional phone, selected package and workspace, language preference, optional referral code, billing profile, payment transaction reference, legal-acknowledgement records and account-security data are used to create the account and workspace, preserve the selected package, administer purchasing and invoicing, apply any referral benefit, verify identity, provide support, prevent abuse and protect the account. If you continue with Google, the account identifier, email and basic profile information supplied by Google are also received for these purposes. Card number and CVV are not entered into Stokontrol; passwords are not shown to support in plain text.

Collection and basis

Data is collected electronically through the registration form. Processing is limited to the account request and establishment or operation of the service relationship, applicable legal duties and legitimate interests in essential security. If a separate consent is required, it will be requested independently; this notice is not consent.

Service-provider groups

Data may be shared, only as necessary to operate and secure the service, with authentication, cloud-hosting, email, payment and technical-support providers. Card data is processed in PayTR's secure payment area and is not stored in Stokontrol's database. Regional availability and required transfer safeguards are assessed before the relevant feature is enabled; no unverified country or transfer status is promised.

Retention and rights

Registration data is kept while the account is active and for the period required by security or applicable legal duties. You may ask whether and why data is processed, request information about recipients, correction, deletion or destruction where conditions apply, notification of those changes to recipients, object to an adverse result produced solely by automated analysis, and seek compensation for unlawful processing. Use the application procedure below to exercise these rights.

Application procedure and response time

You may write to info@stokontrol.com from the email address registered with your account or apply to Yakuplu Mahallesi, 176. Sokak No: 6, Daire: 27, Beylikdüzü / Istanbul, Türkiye. State your full name, relationship with Stokontrol, the specific request under Article 11 of Turkish Law No. 6698 and your response address; proof of authority is required when acting for another person. Identity is checked only as necessary to match the request securely; do not send a password, card data or unnecessary health information. A procedurally valid request is concluded as soon as possible and no later than 30 days, according to its nature; where processing creates an additional cost, only the tariff set by the Turkish authority may apply. No KEP channel is promised because no KEP address has been published.

Roles for clinical data

The clinic is controller where it determines purposes, lawful basis, access and retention for patients and staff. The Stokontrol operator processes clinic data on the clinic's documented instructions. Stokontrol may separately be controller for limited account security, support, legal duties and consented product measurement. The Data Processing Terms describe the detailed allocation.

Clinical and special-category data

Once a clinical workspace is activated, data may include patient identity and contact, birth and address, appointments, dental charts, diagnosis- or treatment-related records, allergies, chronic conditions, medicines, blood group, images, documents, lab jobs, communication preferences and finance summaries. Health data is specially protected; a notice, explicit consent, treatment consent and marketing preference are separate evidence.

Verified patient message replies

If the clinic enables the SMS or WhatsApp reply inbox, Stokontrol processes the sender number, message text, channel, provider message identifier and time received through a signed Twilio or Meta webhook to match the reply to exactly one active patient in that clinic and present it for human review. The raw reply copy in the Stokontrol application database is retained for 90 days from provider receipt and erased by the first daily cleanup after that boundary; this 90-day boundary does not erase copies held in Twilio or Meta systems. Provider-side message, log and backup copies are subject to the provider settings, contract and subprocessor retention terms verified by the clinic before activation. Intent, channel, last four digits, opaque provider reference, time and handling evidence remain subject to the clinic's wider verified retention or erasure policy. An authorised permanent patient or clinic deletion removes linked reply records in Stokontrol; provider-side deletion is handled separately under the relevant provider terms and verified account settings. Only explicit STOP equivalents or a signed Twilio OptOutType=STOP signal withdraw communication consent; bare RET is a free reply and bare İPTAL is an appointment-cancellation request for human review, and neither changes an appointment or consent automatically.

Public questions and product feedback

If public question submission is enabled, Stokontrol processes the email, category, raw title and question, locale, request identifier and timestamps to verify the email, prevent abuse, review the question in private moderation and publish only a reviewed card stripped of personal data. Cloudflare Turnstile processes client IP address, TLS fingerprint, User-Agent, sitekey and origin plus browser-security signals to distinguish bots; it does not receive form entries. Resend processes the recipient email and the message containing the single-use verification link; the verified stokontrol.com sender routes and sends email from Tokyo (ap-northeast-1), but that choice does not change data residency and account metadata, logs and API records are stored in the United States under the provider's terms. The link expires after 30 minutes; an unverified record is deleted by the next daily cleanup after a 24-hour grace period. Verification immediately erases the encrypted email envelope, email and submission-edge HMACs, and token digest; separate rate-limit digests are removed by daily cleanup after their two-hour or two-day expiry. A pending raw question is scrubbed after at most 90 days; published, privately answered, rejected or withdrawn raw questions are scrubbed after at most 30 days. The sanitized public card and moderation evidence remain until a reviewed withdrawal or retention decision. Submission stays off until the applicable lawful basis, provider contract, region/transfer safeguard, sender domain and retention evidence are verified; this notice is not consent.

Training, protected viewing and certificate verification

Training is not a separate membership or sales package; access is provided under the relevant Clinic Pro membership and published programme conditions. When training is used, Stokontrol may process the account and profile identifier, programme and event, educator/training provider, confirmed certificate name, attendance and viewing times, device/IP/User-Agent HMAC digests, short session leases and production-readiness checks. Card number and CVV are not stored by Stokontrol, and patient health data must not be entered into training or playback. These records evidence access, prevent abuse, investigate technical failure and produce the personal certificate issued by the training provider. Every issued private PDF contains a unique QR linked to an unguessable certificate code and a short verification fingerprint. Without separate public-verification consent, no name or training detail is shown publicly; the QR verifies only the current registry state, revocation or replacement with data minimisation. The verified-participant directory is a separate consent from every QR visibility choice; a legacy masked-name choice is never treated as full-name consent. Declining or withdrawing it does not affect the certificate or private PDF; the QR continues to show the current anonymous registry state, including revocation or replacement. Mux broadcasting, recording and the pending international-transfer process are described in the separately versioned Academy notice below. Transfer review and technical tests are tracked separately; technical success is not legal-compliance approval.

Subprocessors, regions and transfers

The current Subprocessors page identifies an active provider, purpose, data category, region and applicable international-transfer mechanism. Supabase, Vercel, Google, Resend, Twilio, Meta, OpenAI or regional payment and fulfilment parties are used only when the relevant feature is enabled. Real clinical processing does not open with unverified operator identity, hosting region or transfer safeguards.

Retention, export and activation

Marking a patient passive is not deletion. Verified contract annexes state retention, legal hold, export, deletion or anonymisation periods. Clinical activation requires an authorised workspace representative to accept the current service and processing terms with their versions and digests, and verification of operator, region and subprocessor evidence. Do not use real patient data before that activation.

English captions · direct Google Cloud processing

ACADEMY-CAPTION-PROVIDER-2026-10-03-V1. The broadcaster's speech audio and derived transcript are processed by Google Cloud Speech-to-Text and Cloud Translation to produce live English captions. The current configuration uses eu-speech.googleapis.com in eu for recognition and translation.googleapis.com with a us-central1 translation resource and dental glossary. The global translation endpoint does not guarantee processing exclusively in one region; we do not claim that all caption data stays within the EU. The account's data-logging preference has not been verified in this test; provider documentation is not account-specific confirmation. AI captions may contain errors; Turkish audio remains authoritative. Viewers' microphones are not activated for captions. This direct flow is separate from Google's role as a Mux subprocessor. Turkey-specific cross-border contractual and legal review is pending. This disclosure does not confirm legal compliance or completed transfer arrangements; technical rehearsal and quality verification remain separate.

Academy broadcast notice

ACADEMY-PROVIDER-2026-10-01-V1 · 1 October 2026. Controller: Doğuş Sevinç; contact: info@stokontrol.com. Academy technical broadcasts use Mux Video for the broadcaster's picture and sound. Recordings may be created at Mux and locally in OBS. Merely watching does not activate a viewer's camera or microphone. Do not include patient or third-party private information.

International transfer · pending

Awaiting Mux response / standard-contract process. Existing DPA and EU/UK/Swiss mechanisms do not establish completion of Stokontrol's Turkish KVKK transfer process. Account-specific steps remain pending separately from technical broadcasting, recording and development tests. Publishing this notice or passing a technical test is not confirmation of legal compliance.

Test broadcast · questions

The operating policy selected for the technical Test broadcast retains questions for 7 days from submission; this is not a statutory minimum or a Mux retention claim. The configured period is shown in the question area. Account-linked questions and timestamps reach moderation; approved questions and answers may be shown to participants. Expired questions become inaccessible and eligible for periodic cleanup. Content-free deletion evidence may remain separately. Provider video/logs are not deleted by this process. Other events use their own published policy.

Viewing, recording and retention

Stokontrol uses participant names, event records and viewing time for access and attendance certificates. Mux may process IP addresses, device/browser information and media requests. The up-to-100-day Mux Data pseudonymous-view period is not a retention promise for video, OBS files, questions or certificates. Account-specific recording/log retention awaits verification. A captured recording is not automatically published.

Attendance and certificates

Monthly Clinic Pro covers one calendar month and annual Clinic Pro covers one calendar year; the event date must fall within the active membership term for live training access. One participant is registered per event; different events may have different participants. The confirmed name appears on the certificate; contact support for spelling corrections. Participants with valid event access, a completed event registration and a confirmed, locked name can receive a personal QR-verifiable certificate after the training ends. A test-broadcast certificate records technical-test participation only. Optional public name visibility is separate from the private certificate. Questions have their own notice and retention configuration.

Optional Meta advertising and sales measurement

With separate permission for Meta measurement, the ad click ID, browser information and a completed Clinic Pro order's amount, currency, time and one-way order digest are sent to Meta to measure ad-driven purchases and improve ad delivery. This integration does not send patient, treatment or clinic content, names, email, telephone, billing details or raw IP addresses. Browser consent and click records are valid for 90 days and cleared on their next read after expiry. A per-tab receipt marker reduces repeat sends for that tab session. Manage preferences lets you choose or withdraw this permission separately from usage analytics; refusal does not affect purchases or service access. Withdrawal stops future sends and deletes the retained ad click. Meta applies its own processing and retention terms to records already received.