Clear information about how Gateflow operates, protects data and uses browser storage.
Effective 4 August 2026Version 1.1CoinForge Capital Ltd. · 207122521
◎
Rewarded advertising is disabled by default. Gateflow's own cookies support authentication, security and preferences. The persistent analytics identifier is optional. If the ayeT integration is configured, Gateflow must ask for a separate advertising choice before loading its SDK; refusing or withdrawing that choice leaves the ordinary free waiting route available. A separate homepage request verifies the registered domain with the planned payment provider and may be subject to that provider's request handling.
01
What cookies are
Cookies are small text values a website stores in your browser. Session cookies support a current visit; persistent cookies remain for a defined period. Similar local browser storage can remember a device-level preference.
02
Cookies and preference records
Name
Purpose
Type
Duration
gateflow_session
Keeps a signed-in account authenticated and carries the CSRF value used to protect account actions.
Strictly necessary · first party · HttpOnly
Up to 7 days, or until sign-out
gateflow_google_oauth
Binds a Google authentication response to the browser that started it and prevents login-request forgery and replay.
Strictly necessary security · first party · HttpOnly
Up to 10 minutes; removed after the callback
gf_cookie_consent
Remembers whether you selected essential-only or allowed the analytics identifier.
Strictly necessary preference · first party · HttpOnly
180 days
gf_advertising_consent
Records the separate allow or deny choice for the optional rewarded-video integration. It does not itself identify an ad or confirm that a video was watched.
Advertising preference · first party · set only when the integration is offered
Up to 180 days; replaced when you change the choice
gf_visitor
Recognises a browser across protected-link visits so Gateflow can calculate unique and repeat link performance.
Optional analytics · first party · HttpOnly
Up to 180 days; deleted when analytics is withdrawn or permission expires
Gateflow's first-party cookies use SameSite=Lax. They are marked Secure when Gateflow is configured for HTTPS production use. If ayeT is enabled, the SDK or advertising demand partners may use additional browser storage under the applicable consent signal; the final vendor list and retention details must be reviewed before activation.
03
Consent and essential cookies
Strictly necessary cookies do not require consent when they are needed to provide a service you requested, such as authentication or remembering a privacy choice. Gateflow asks permission before enabling the persistent gf_visitor analytics identifier. Advertising is a separate choice stored as gf_advertising_consent and is not inferred from analytics permission.
Choosing “Use essential only” or refusing advertising does not block access, the ordinary free waiting flow, Premium, publisher tools or administration.
04
Analytics with and without consent
Gateflow records minimal server-side events required to operate and secure protected access, such as a page view, waiting-period completion or redirect. These may include a server-resolved two-letter country code, device category, source category, experiment variant, assigned wait, referring origin and time. Country resolution does not set a browser cookie, and raw IP addresses are not stored in publisher event analytics.
Without analytics consent, Gateflow does not store a persistent visitor identifier with those events and cannot increase a wait based on visits across separate sessions. When you allow analytics, gf_visitor enables unique and repeat-session measurement and bounded adaptive-wait testing. Analytics permission alone does not load ayeT or permit rewarded advertising.
05
Optional ayeT rewarded video
The ayeT integration is disabled by default. If it is configured for a protected link, Gateflow must first obtain the separate advertising choice recorded by gf_advertising_consent. The SDK is then loaded only as part of the optional video flow, and playback still requires your action; the video is not a condition for using the ordinary free waiting route.
When allowed, the SDK and advertising demand partners may access or set browser storage and receive consent signals, an opaque Gateflow attempt identifier, IP address, browser or device information, and video interaction data to select, deliver, measure and protect an ad from fraud. Available ads and the participating vendors can vary by country and request. Review the ayeT Services Privacy Policy ↗ and Rewarded Video SDK information ↗.
06
Manage or withdraw your choices
You can reopen the preference panel at any time. Withdrawing analytics permission deletes gf_visitor; future events will not receive a persistent browser identifier. Withdrawing advertising permission updates gf_advertising_consent, prevents future ayeT SDK requests from Gateflow and does not change your free waiting option. A video or provider request already in progress may need to finish or be closed before the change takes effect.
Your browser can also delete or block cookies. Blocking essential cookies may prevent sign-in or protected security flows from working correctly.
07
Third-party requests and Google
The homepage makes an image request to billing.ovgcpayments.com to verify the Gateflow hostname for the planned payment integration. The URL carries a verification token, hostname and timestamp; standard network metadata is also visible to the provider. Google is contacted only after you choose the Google access button. ayeT and its advertising demand partners are contacted only if the rewarded-video provider is enabled, the required advertising choice has been recorded and you start the optional video flow. External destinations may use their own cookies after you choose to open them.
08
Updates and contact
The policy and preference panel should be reviewed whenever the rewarded-video demand setup, vendor list, storage or retention changes. Questions can be sent to contact@coinforgecapital.net.
◎
Your privacy, your choice
Essential cookies keep sign-in and security working. With your permission, a first-party identifier enables repeat-visit analytics and adaptive wait experiments. Optional sponsor video is controlled separately and never loads until you allow it. The homepage also performs the payment-provider domain-verification request described in our policy. Read the cookie policy.
