Privacy
Last updated: 30 September 2026
This notice describes the information used by LAKADE to operate public and private takeover screens, process payments, run collaborator accounts, prevent abuse and measure basic service activity.
Takeover information
When you create a takeover, LAKADE processes the display name, message, optional website link, optional phone number, selected visual settings, screen destination, timestamps and technical status needed to publish and manage the takeover. Published takeover content is intentionally visible to people viewing the relevant country-specific public network or private business screen and may also appear in takeover history where that feature applies.
Content and link safety checks
Before payment or publication, the display name and message may be automatically checked by LAKADE for prohibited language. The current text filter runs as part of the LAKADE service and is used to decide whether the message can continue to checkout or publication.
Optional URLs are automatically checked for format, public-network reachability and basic safety. LAKADE may also query external URL-reputation services such as PhishTank or Google Web Risk when configured. In that case, the submitted URL may be sent to the relevant provider for threat checking. A link may be checked again later and disabled if it becomes unsafe.
Payments
Stripe processes takeover payments. LAKADE stores payment references, amounts, currency and payment status needed to match a payment to a takeover and handle accounting or disputes. LAKADE does not store full payment-card numbers.
Visitors and basic analytics
LAKADE uses a random first-party visitor identifier to count monthly website visits for each public country network and private screen. The application stores a one-way hash derived from that identifier in its visitor table rather than storing the visitor's IP address there. LAKADE does not present browser sessions as a measure of how many people are physically watching a TV, and it no longer uses live-watcher or per-message-view counters as product metrics. Hosting, network or security providers may still process normal connection information such as IP addresses in their own server logs.
The visitor identifier cookie can remain on the device for up to one year and is used to avoid counting the same browser repeatedly within the same monthly visitor metric.
Collaborator referrals and accounts
If you arrive through a collaborator link, kiosk QR, widget or other partner source, LAKADE may store a first-party referral cookie for up to 30 days. This allows a successful paid takeover to be attributed to the correct collaborator and source channel. The referral cookie affects attribution, not whether the visitor sees the public or a private screen.
Business collaborator accounts can contain business/contact details, referral code, login credentials in hashed form, screen mode, commission settings, takeover prices, protected times, free-credit usage, referral activity, payout records and account timestamps. Authentication sessions are also used when a collaborator or administrator logs in.
Partner applications
If a business applies to host LAKADE, the service stores the details submitted in the application so the request can be reviewed, the screen can be configured, a collaborator account can be created and the commercial relationship can be managed.
Kiosks and embedded widgets
LAKADE kiosks and embedded widgets request the current takeover and may record aggregate activity such as impressions, heartbeat/last-seen information and collaborator attribution. Embedded widgets do not process payment-card information; takeover checkout remains handled through LAKADE and Stripe.
Retention and disclosure
Information is kept for as long as reasonably needed to operate the service, preserve takeover/history functionality, prevent abuse, manage collaborator relationships, handle payments and disputes, meet accounting obligations and comply with applicable law. Some records may therefore be kept longer than the message remains live.
LAKADE may share information with service providers only as needed to operate the service, for example payment processing, hosting and configured security/reputation checks, or when disclosure is required by law.
Your choices and rights
You can choose not to submit optional links or phone numbers. Browser settings can be used to remove or block first-party cookies, although some attribution, statistics or login functions may then work differently. Applicable privacy law may also give you rights to access, correct, delete, restrict or object to certain processing and to request information about your data.
Security
LAKADE uses access controls, hashed partner passwords, server-side validation and automated content/link checks to reduce misuse. No online service can guarantee absolute security, so only information intended for the relevant screen should be submitted.