Right now: this public website does not implement user accounts, ad delivery, visitor analytics, advertising pixels, or a contact form. The planned ad-tracking system described below is not live.
01. The current website
QLYNK Ads is currently an informational website made up of static public pages. The pages do not intentionally run advertising analytics scripts, behavioural tracking pixels, or a user-profile system. There is no ad dashboard or publisher tracking SDK operating from this version of the site.
This statement describes the application pages in this release; it is not a promise about logs independently maintained by the hosting provider or network infrastructure.
02. Hosting and security logs
To deliver and protect a website, its hosting provider, edge network, or other infrastructure may process standard technical request information. Depending on the deployment configuration, that may include an IP address, user-agent string, request time, requested path, and request headers.
Actual provider logging, access, and retention depend on the hosting configuration and provider terms. Those settings must be reviewed before the production site is launched. The static pages themselves do not maintain a separate visitor analytics database.
03. The planned advertising service
When the ad-serving and analytics features are implemented, the design currently calls for events to be associated with an event ID, UTC timestamp, source IP address, user-agent string, a reviewed subset of request headers, ad ID, ad-unit ID, website ID, and traffic classification labels.
The planned classifications separate network type (for example, VPN/proxy/unknown), actor or bot type, and event legitimacy or risk. These are distinct dimensions: using a VPN does not by itself make a person a bot or an invalid visitor.
These are planned data fields, not a description of an active collection process. Before these features launch, this policy must be checked against the actual code, provider configuration, access controls, and retention schedule.
04. Approximate location
The current design intends to derive approximate location from an IP address only when needed for the live admin dashboard. The application is planned not to write that derived location to event records or its own persistent enrichment cache.
This design has not been implemented or audited yet. Hosting logs or an external lookup provider may have their own processing or retention, which must be assessed before launch. IP-based estimates are approximate and should not be treated as an exact physical location.
06. Retention and access
The current application pages do not store ad-click or ad-impression events. A retention period for planned raw IP, user-agent, selected-header, event, and classification data has not yet been finalised. That schedule must be chosen, documented, and implemented before production tracking begins.
The intended admin dashboard is for authorised project administrators. Any future access to raw request metadata must be restricted, and secrets or sensitive headers such as cookies and authorization tokens must not be copied into event records.
07. Your choices
Because no visitor account or application-level tracking preferences exist in this release, there is currently no in-product privacy dashboard or preference centre. If the planned service introduces tracking controls or account preferences, they will be described before those features launch.
08. Policy updates
This policy must be revised when implementation changes materially affect data processing, the hosting or storage providers, event contents, retention, or user choices. The date at the top of the policy identifies the latest editorial update, not a legal certification.
09. Questions about privacy
A dedicated public contact channel has not yet been published. A route for privacy questions will be available before the advertising and analytics service launches.
This policy is preliminary product wording and should be checked against actual hosting behaviour and applicable requirements before launch.