PRIVACY
Privacy notice
Your enquiry helps us understand your project. Here is how we handle the information you share.
What this notice covers
Red Ink Media uses the information you share through this website to respond to project enquiries and support our work with you. This notice explains what the website collects, how it is used and how to contact us about your information.
Information you share
The existing project form asks for your name, company, role, work email, message, audience and indicative budget. You may also provide a project interest, desired launch date and extra context. We record your consent and the time of submission. The story enquiry form requires only your name, work email and message. Company, role, audience, route, budget, timing and notes are optional. Submitting that form is a request for Red Ink Media to respond; we record the displayed notice version and submission time. Please share only information relevant to your enquiry and avoid including sensitive personal information about yourself or others.
How we use it
We use these details to respond, understand your brief, recommend an approach, prepare a quotation and communicate about a potential or agreed project. The website also uses limited technical information for security, spam prevention and troubleshooting. Submitting a project enquiry does not subscribe you to a mailing list.
Website storage and technical information
The site uses essential WordPress functionality and security measures. Hosting logs may include your IP address, requested pages, browser information and access times. Our Wordfence security plugin is configured to log all traffic, excluding signed-in users with publishing access, with limits of 2,000 Live Traffic rows and 30 days. These security-log limits do not set the retention of hosting, CDN/WAF, error or database logs, or backup copies; those separate retention periods have not yet been confirmed. The enquiry form uses a temporary, hashed IP-based counter to limit repeated submissions. The existing corporate-film enquiry journey keeps validated campaign values in browser session storage and may include them, the landing-page path and a Google click identifier (gclid), if supplied, in the enquiry email, separately from optional audience analytics. The separate story enquiry page includes the five validated UTM campaign fields described below with the enquiry email only after Google Analytics is allowed. Your project brief is sent to Red Ink by email; this form does not create a separate database of enquiry messages.
Analytics and external services
Our corporate-film enquiry page and its linked project-enquiry journey offer optional Google Analytics. It loads only if you choose Allow analytics. Google processes cookie identifiers, browser/device information, visits, campaign attribution and enquiry-start/completion events to help us compare how people find and use this page. Names, email addresses, company details, budget selections and other enquiry-form content are not sent to Google Analytics. Advertising personalisation is disabled. You can choose No thanks and still submit an enquiry. Your choice and analytics cookies last up to 180 days. Use Analytics preferences at the bottom of that page to change your choice; choosing No thanks stops further measurement and clears the analytics cookies used by this page. Google may process analytics information outside Singapore under its own privacy practices. Links to films, social platforms and other websites take you to services with their own privacy practices. These services may collect information when you visit or interact with them.
Automatic first-party aggregate site statistics
When enabled, the Make them care page automatically measures page loads, approximate foreground-time milestones of 10, 30 and 60 seconds and enquiry-button clicks. Accepted-enquiry counting is unavailable on our current PHP host. Missing counts are not evidence of zero enquiries. This first-party measurement does not depend on allowing Google Analytics. It helps us understand whether campaign traffic loads this page and remains in view. It does not establish unique visitors, exact visit duration, human attention, successful inbox delivery or sales.
The page keeps its current campaign category, timing and sent-event flags only in JavaScript memory for that page. It uses no measurement cookies, browser local storage, session storage, visitor identifiers, session identifiers or fingerprinting. Only a fixed page name, a fixed allowlisted campaign category, an event category and a coarse Singapore calendar day are sent to a same-origin endpoint. Arbitrary campaign values, full URLs, referrers, advertising click identifiers, IP addresses, browser details and form contents are not included in that measurement payload. A Google-tagged category can be assigned from the presence of a gclid parameter without reading, storing or transmitting its value; this does not prove a paid click or identify the Google campaign.
The aggregate store contains counters by page-load cohort day, page and campaign category, rather than individual event or visitor records. The intended reporting window is the current Singapore calendar day and the previous 29 days. Cleanup runs during collection, report viewing and scheduled WordPress tasks while the plugin is active; scheduler execution and database backup retention require separate host review. Short-lived aggregate rate-limit counters contain only minute and campaign scopes, with no visitor or IP key. The collection endpoint requests omit cookies and referrer information. Hosting, network and security systems necessarily process connection information such as IP addresses and request headers, and may retain separate logs; these are not part of the aggregate statistics table. Retention in hosting logs and backups is separate from the 30-day aggregate reporting period. We do not send these aggregate events to Google, OpenAI or another advertising service.
On a supported host, an enquiry can be counted only after the existing website handler accepts it for email delivery, using a coarse measurement-allowed flag, campaign category and cohort day attached to that request. The aggregate observer does not read enquiry form values. It checks the accepted response in memory but does not retain the enquiry reference. Very early submissions, failed measurement requests and blocked or stale page state can therefore be uncounted. The accepted-enquiry counter is omitted if the website host cannot finish the form response before updating statistics. Measurement failure must not affect enquiry delivery. Existing enquiry processing and optional Google Analytics continue under the separate sections below.
Open Privacy & measurement in the footer and choose Stop aggregate measurement on this page to stop further aggregate measurement for the current page. This stop is held only in page memory: reloading or opening another page starts measurement again only while site collection is enabled. Browser Do Not Track and Global Privacy Control requests are also respected. Google Analytics is separate; declining Google does not by itself turn off first-party aggregate statistics. Previously recorded aggregate counts cannot be linked back to a particular visitor for removal. Repeated page loads, automated requests, browser restrictions and lost requests can affect the totals.
Optional Google Analytics on the story enquiry page
Google Analytics is off initially and loads only after you allow it. You can send an enquiry without allowing analytics. Google processes browser and device information, cookie identifiers, visits and validated campaign information to help us understand use of this page. Accepted enquiries may produce a generate_lead event with an opaque enquiry reference. This measures an enquiry accepted for email delivery; it does not verify an eventual sale or advertising result.
Your name, email address, company, budget, brief and other form details are not sent to Google Analytics. The page URL sent to Google excludes query parameters and the page referrer is omitted. Advertising storage, Google signals and advertising personalisation are disabled.
Open Privacy & measurement in the footer to change your choice. Tick Allow Google Analytics and choose Save preferences to allow it. Unticking the checkbox withdraws permission immediately; Decline Google Analytics also stops further Google measurement and clears this page’s analytics cookies. Your choice and analytics cookies last up to 180 days. If browser storage is unavailable, the controls explain when a choice applies only to the current page.
Validated utm_source, utm_medium, utm_campaign, utm_content and utm_term values are kept in browser session storage only after you allow analytics, and are included with your enquiry email only while that permission applies. Email-like values and long numeric identifiers are rejected. The story form does not capture Google ad-click identifiers. Google may process analytics information outside Singapore under its privacy practices. Browser restrictions or clearing cookies can shorten storage periods. Cookie expiry is separate from Google’s retention of analytics data.
Optional Meta measurement
On Clear Story Film, its Start a Project enquiry journey and Make Them Care, Meta measurement is off until you separately choose Allow Meta measurement and save that preference. Google Analytics and first-party site statistics have separate controls. Enquiry forms work without Meta permission.
If allowed, the existing Gil Chan’s Pixel (749037251909930) receives PageView events and Lead events only after our website accepts an enquiry for email delivery. A Lead is not confirmation of inbox delivery, a qualified prospect or a sale. We use a one-way transformed random enquiry reference as an event identifier to prevent repeated measurement. We do not send your form field names, name, email, phone number, message or other enquiry contents to Meta. We do not use advanced matching or server-side Conversions API.
The Pixel runs in an isolated document with a fixed measurement URL and an empty referrer, separate from the enquiry form. Campaign UTMs and other query strings are not passed to Meta. Meta receives the fixed measurement URL, event timing, Pixel/event identifiers and normal browser request information, including IP address and browser details. Meta cookies may be used where the browser permits them. The isolated document cannot access our form or first-party cookie storage. Browser restrictions can reduce attribution.
Open Meta measurement preferences near the bottom of these pages to change your choice. Unticking the checkbox or choosing Keep Meta off stops further measurement immediately and removes the measurement document. Your choice is stored on this browser for up to 180 days; deduplication stores transformed event identifiers in this tab’s session storage for up to 48 hours. Withdrawal cannot recall data already sent or a request already in transit, and does not clear cookies held on Meta’s own domains. Do Not Track and Global Privacy Control requests also keep Meta off.
Meta may use the information under its own policies, including to measure and improve advertising, and process it outside Singapore. Our preference/storage periods do not set Meta’s retention period. Read Meta’s privacy policy and cookie policy. OpenAI advertising measurement remains disabled.
OpenAI advertising measurement
OpenAI advertising measurement is disabled on the Make them care enquiry page. The page does not use previously saved OpenAI permission, read ChatGPT ad-click references or request OpenAI measurement for new enquiries.
Earlier OpenAI choices may remain in browser local storage until their original expiry of up to 180 days. The earlier confirmation flow used consent and receipt cookies that expired within 10 minutes, with expired server records queued for cleanup. Disabling new measurement does not recall any previously sent event. These browser and receipt expiry periods do not describe OpenAI’s retention of information it may already have received. OpenAI may process that information outside Singapore under its privacy policy.
Who can receive information
Relevant Red Ink team members use enquiry information. Website hosting and email service providers also process information as needed to operate these services. Our hosting environment is located in the United States, so some website information is processed outside Singapore. We do not use your project enquiry as permission to disclose it for unrelated marketing. Where information is processed overseas, we are responsible for arranging protection consistent with applicable Singapore data-protection requirements.
Retention and protection
We keep information for as long as it is needed for the enquiry, an ongoing business relationship or a legal requirement. When it is no longer needed, it should be deleted or anonymised, including through the normal expiry of backups. We use appropriate access controls and security measures to protect it. No website or email system can guarantee absolute security.
Your choices and privacy contact
You can ask about the personal information we hold, request access or correction, or withdraw consent with reasonable notice by emailing gil@redinkmedia.asia with “Privacy enquiry” in the subject. We may need to verify your identity before responding. We will explain any applicable exceptions and the likely effect of withdrawing consent; without your contact details, we may be unable to continue responding to your project enquiry.
Updates
We may update this notice when our website or practices change. This notice was updated on 9 October 2026 (Singapore time). If a new use requires your consent, we will request it before proceeding.
