← iiz studio

Privacy & cookies

Updated 24 September 2026 · Viewer discussion and optional support

This website is operated by IC LINKS TRADING LIMITED trading as iiz in Ireland. IC Link Drama is its private screening room. For privacy questions or requests, contact benson@iiz.ie.

We count requests to the password-protected screening page by approximate area and hour. We do not save your IP, a visitor identifier or playback history in these new counts. There is no analysis cookie or consent pop-up. You can object to being counted without losing access.

What we count

When you enter the screening page, the server temporarily uses the network IP already needed to deliver your request to estimate a country, region and city. It adds one to an hourly area total, then retains only the hour, estimated area and count. It does not save an individual visit, exact visit time, full or hashed IP, browser category, account, invitation identifier, referrer or email recipient. Reloading the page can increase the count; counts are not unique people and do not prove that a named recipient visited or watched a film.

The purpose is to understand the broad regional reach of this private screening room. We rely on our legitimate interest in obtaining limited regional usage information, balanced by these data-minimisation safeguards, the short retention period and the right to object. We do not use the counts to identify or target individual recipients, build profiles, track playback, advertise or sell data. No client-side analytics beacon, tracking pixel or fingerprint is used.

Approximate city estimates use a downloaded DB-IP Lite database (September 2026), converted to our own lookup format and queried within our hosting infrastructure. We do not send visitor IPs to DB-IP for lookups, request device GPS or save coordinates. VPNs, mobile and shared networks can give an inaccurate area. Unknown areas remain unknown.

Your choice and retention

Use Privacy choices → “Exclude this browser from counts” to object immediately for subsequent requests. This preference lasts 30 days in this browser and does not restrict viewing. Existing choices to reject the earlier optional statistics are respected until their preference expires. We also honour a Do Not Track or Global Privacy Control signal. No preference cookie is created merely by opening the page or signing in. Deleting cookies removes a locally saved preference; you can set it again or send a browser privacy signal.

Area totals appear only in the separately password-protected administrator page and are kept for up to 7 days. Expired data is excluded from queries and deleted on subsequent site activity or administrator queries. Because new totals have no individual identifier, the site cannot extract one person's contribution; we do not collect extra identification to do so.

Earlier optional statistics

The previous opt-in system is retired: no new full-IP, browser-ID, login or playback-start records are created, even if an older page sends a playback event. Previously consented records remain separate, under their original consent basis and 30-day retention, not repurposed for new counts. Changing either privacy preference deletes earlier optional records linked to the current browser's old identifier. If you have removed that cookie or changed browsers, contact us about earlier records. Withdrawal does not affect processing lawfully performed before withdrawal.

Viewing codes and separate series

A viewing code opens one named series only. Codes must be redeemed within 7 days and can be claimed by one browser identity. The resulting permission lasts up to 30 days; it can be revoked by the administrator. If you receive codes for different series in the same signed-in browser, each grants only its own series. Other series, their films and discussions remain protected. The earlier shared viewing password grants JADE FURY access only.

Code records contain a code hash, the relevant series, issue and redemption times, expiry and a random claiming-viewer reference. We do not save the readable code. Issued code records without a remaining grant are removed after their redemption deadline has passed by 90 days. Necessary browser sessions and per-series grants maintain this access; these are separate from area statistics. Clearing cookies, moving to a different browser or expiry can require a replacement code from the creator.

Facebook and Instagram invitations

If you request an invitation by commenting on a selected Facebook or Instagram post, the creator can send you a private viewing link. When automatic replies are enabled, Meta sends the comment event to this site so it can check the selected post and keyword and issue the invitation. The site keeps keyed, non-readable account and comment references to prevent duplicate invitations, together with the campaign, series, code reference and delivery status, for up to 90 days. Expired records are excluded and deleted on subsequent site activity. We do not save the social comment text, social display name or readable invitation in these delivery records. Meta processes the comment and private message under its own terms.

The private link contains a viewing code in its fragment, after #. The fragment is not sent to our server on opening the link and is removed from the address bar by the invitation page. Your code is submitted when you press Open my series; opening a link preview does not redeem it. Keep it private: another person could claim an unused invitation if you forward it.

Comments, story ideas and creator support

Viewing and contributing are free for invited viewers. When you first send a message or like one, a necessary browser cookie links your contributions to a random viewer record so you can manage your messages and likes. We store the display name, message, series, message type, submission time, review status and any creator reply. Replies also record their conversation and the message they answer; each reply has separate likes and review status. Earlier submissions may also retain the episode selected at the time. These records are separate from anonymous area counts and are not used to track playback. Other signed-in viewers can see approved messages; pending and hidden messages are visible only to their author and the administrator.

We process submissions to provide the discussion you request and moderate it. The publication checkbox records your choice to show the submitted words and display name. Approved messages remain until removed. Unpublished messages are kept for up to 90 days after submission or the most recent moderation change, excluded from viewer and administrator queries after that period, and deleted on subsequent activity. Viewer records without a remaining session, viewing grant or message are removed once they are more than 90 days old. You can remove a message under My submissions while signed in. Removing a top-level comment also removes its conversation and likes, as stated in the confirmation. Removing an individual reply leaves other replies in place and clears their link to the removed reply. Hiding a top-level comment makes its conversation unavailable to other viewers; after its unpublished retention period, the conversation is removed. For corrections, deletion or a lost browser identity, contact Benson. Signing out, cookie deletion or expiry may require help recovering an older submission.

We use a limited set of language rules to reject obvious profanity. Respectful criticism and fictional story discussion are allowed. When AI moderation is connected, the display name, message and any proposed creator reply are sent to OpenAI's moderation API for screening; we do not attach your viewing code, browser cookie, IP, viewer reference or payment information. The administrator can see whether a message passed, needs contextual review or could not be checked. A content digest, policy and model identifiers, result categories, check time and any explicit human-review reason stay with the message under the same retention period. Automated checks may make mistakes; contact Benson to request a review. No message is automatically published, and an enabled AI check failing does not automatically approve it.

For each like, we store the message reference, your random viewer reference and the time. Each viewer identity can like a message once and can undo the like. Other viewers see the total and their own selection, not a list of people who liked it. Likes are removed when undone, when the message is deleted or when the associated viewer record is removed. Four opening discussions provide starting points for conversation and are shown as discussion starters, without viewer names. They remain in the discussion as new viewer messages arrive. Their likes and replies come from actual viewer actions, start at zero, and follow the same access, review and removal rules as other discussion records. These opening topics are not independent viewer reviews. They are retained unless the creator removes them; hiding a topic stops its public replies and likes but does not automatically delete it. Unpublished viewer replies still follow the 90-day retention period.

Comment, like and sign-in security counters use a keyed hash of the network IP for up to one hour; separate author submission quotas last up to 24 hours. We do not bind access to your IP or combine this information with area counts. Sessions last up to 30 days and can be revoked. Cookies identify a browser, not a physical device.

Facebook sign-in is being prepared and is disabled until configured and tested. If enabled later, it asks Meta to confirm your identity and your own Like on one specified post. A keyed account reference maintains your viewing session; your Facebook access token is used during verification only and is not stored. The browser-bound sign-in transaction expires after 10 minutes. Facebook processes sign-in under its own privacy terms. This is separate from liking a Facebook Page or visiting a link.

The optional Buy Me a Coffee link opens an external payment page once it is available. We do not collect card details or track payment status on this site. No payment is required to watch, comment or submit an idea, and support does not give a suggestion priority. The external provider handles payment under its own terms and privacy notice.

Necessary service functions and cookies

Hosting and video delivery necessarily handle network addresses and requests to provide the service. A login cookie protects the films. Limited login-attempt information prevents password guessing; this is separate from area counts and supports service security.

CookiePurposeDuration
__Host-jf_sessionMaintain access after entering the viewing password; not used to identify visitors in counts.Browser session, or 30 days if you choose “Remember my login”.
__Host-jf_privacyRemember a privacy preference only when you change it. New preferences have no visitor ID. An old opt-in cookie may remain solely to support deletion of earlier records.30 days.
__Host-jf_viewerMaintain per-series viewing permissions after redeeming a code and manage your submissions and likes. Also used for future Facebook viewing verification.Up to 30 days.
__Host-jf_facebookBind an explicitly started Facebook sign-in to this browser, when enabled.10 minutes.
__Host-jf_adminMaintain the owner's separate administrator login; not set for ordinary viewers.30 days.

Cookies are first-party, Secure and HttpOnly. We do not read other sites' cookies. Login-attempt counters expire after 15 minutes; persistent expired counters are cleaned on later activity. Passwords and login tokens are never stored in access statistics.

Providers and international processing

The site uses OpenAI Sites and Cloudflare hosting. Video delivery uses Alibaba Cloud, with a Shanghai origin and overseas delivery network. These providers handle requests to deliver the service; processing may take place outside Ireland and the EEA, including China for the video origin. Provider operational logs, backups, contractual safeguards and retention are separate from the application's area counts and earlier optional records. Contact us for details of provider arrangements.

Studio enquiries

If you use the studio enquiry form, we store the name, company, email address, request type, budget and message you provide so the administrator can review and respond to your request. Enquiries are stored in the site database and visible to authorised administrators; the form does not automatically email or use an AI service. A security counter uses a keyed digest of the network IP to limit repeated submissions. The counter window expires after one hour; expired counters are removed on a later enquiry or administrative housekeeping. Contact us for the applicable retention period and to request access, correction or deletion.

Your rights

Depending on the applicable circumstances, you may request access, correction, erasure, restriction, portability or object to processing based on legitimate interests. Use Privacy choices to exclude this browser, or contact benson@iiz.ie for requests. You may complain to the Irish Data Protection Commission.