Privacy information · Effective 12 July 2026
Privacy Notice
This notice explains what data MyEkran handles, why it is needed, when it may be shared, and how to make a privacy request.
Data controller / service provider
- Brand / business name
- MyEkran
Professional-body information is shown where applicable.
Verified business details will appear here once complete.
Scope and roles
This notice covers the public website, account creation, the management dashboard, screen pairing, playback, and support. A customer may be the data controller for its staff, screen content, and audience-facing material. MyEkran acts as a processor where it handles data on the customer’s instructions. The commercial agreement and, where needed, a data-processing addendum define the parties’ exact roles.
Categories of data
We may process account and contact details; organisation, location, and team membership data; uploaded media and metadata; playlists; screen, session, and pairing records; playback and error events; security and audit logs; support requests; and subscription, billing-profile, transaction, and consent references. MyEkran does not receive or store card numbers, expiry dates, or card security codes; when payments are enabled, those details remain in the payment provider’s hosted flow.
Essential cookies and technical records
Essential HttpOnly cookies maintain management sessions and authorised screen playback. In production they are sent with Secure and SameSite=Lax attributes. This release does not use advertising or behavioural-tracking cookies. IP address, browser or device information, request time and identifier, last-seen screen state, playback events, and error events may be recorded for authorisation, security, audit, support, and abuse prevention. Some authentication and consent records store keyed summaries instead of the original IP or user-agent value.
Billing identity and payment-provider transfers
Billing details link an order to the correct business. A full tax or Turkish identity number entered for a payment request is processed temporarily and is not stored in the platform database; only a masked value may remain. If iyzico customer creation is enabled, the identifier and the required name, contact, and address details are sent to iyzico and are not written permanently to the MyEkran database. Card details are handled in iyzico’s hosted form and do not reach MyEkran servers.
Purposes and legal bases
Data is used to provide the account and service, deliver the right content to authorised screens, enforce access rules, operate security controls, support customers, manage subscription state, and meet legal obligations. Depending on the relationship, the legal basis may be contract formation or performance, a legal obligation, legitimate interests, or consent.
Sharing and service providers
We do not sell personal data. Data is shared only as needed with service providers that have actually been enabled for hosting, email, payments, or monitoring, and where required by a lawful authority request. The current providers and any international-transfer terms are confirmed in the data-processing addendum used for the sale.
Retention and deletion
Workspace data is retained while the account is active and while contractual or legal requirements continue. Expired sessions, invitations, pairing records, verification tokens, and email-operation records follow periodic cleanup rules. Export, closure, and deletion requests require identity and authority checks; backup copies age out through the backup lifecycle. Masked billing identifiers, transaction references, and legal consent records may be retained for the applicable contractual and legal period.
Your rights
Under applicable law, you may have rights to access, correct, or delete personal data; restrict or object to processing; and, where relevant, request portability. Customer data is not disclosed until the requester’s identity and authority for the organisation have been verified.