Cookie Policy

DateFoundry · Cookie Policy · v2.1 · Effective 8 October 2026

1. Introduction and scope

This Cookie Policy describes how DateFoundry uses cookies and comparable storage or access technologies on datefoundry.com. The site supports adult dating profiles, matching, communication and online purchase of tokens, likes and virtual gifts. Some technologies are required to keep a session secure and associate an order with the correct account; others can collect information about page performance, preferences or advertising. Different purposes involve different permissions, and merely opening an Account does not mean you agree to unrestricted tracking.

The operator is AMORIAX LTD, company number 17502222, and questions can be sent to info@datefoundry.com. The Privacy Policy explains how information derived from a device may become personal data, the relevant lawful bases, retention and rights. This Policy addresses both cookies and other mechanisms capable of storing information on or reading information from a device, including local storage, pixels and comparable client-side technologies.

2. What cookies and similar technologies are

A cookie is a small value stored by a browser and returned to a website or associated provider. Session cookies commonly expire when the session closes, while persistent cookies can survive later visits until they expire or are removed. First-party storage is associated with the website you are visiting; third-party mechanisms may involve another organisation. A cookie need not contain a name to identify a device or contribute to a profile when combined with other signals.

Similar technologies include web storage, pixels embedded in a page or email, scripts that access device information and identifiers added to links. Some technologies are necessary to detect forged checkout submissions or maintain your login; others measure visitor journeys or serve personalised advertising. A browser's privacy settings may control some, but not all, mechanisms. We explain the purpose and applicable choice rather than treating every technology as interchangeable.

3. Why we use cookies

Necessary mechanisms can preserve a login, prevent cross-site request forgery, remember an in-progress payment session, enforce rate limits and protect an Account from unauthorised access. Without them, some requested functions may not operate securely. A consent-preference record can be needed to respect your earlier choice and avoid repeatedly showing the same panel. We limit the information kept in such records to what is appropriate for that task.

Optional functions may remember non-essential display choices, help us understand which pages are confusing or measure advertising performance. They are not required to purchase tokens or speak with another member unless a particular feature genuinely cannot function without the relevant setting. We distinguish anonymous aggregate analysis from methods that store or access identifying device information; the latter can trigger additional electronic-communications and data-protection obligations.

4. Cookie categories

Strictly necessary storage is used for essential login, security, fraud prevention, payments and a choice you have actively requested. Functional storage supports convenient preferences such as language or layout when not strictly necessary. Analytics may reveal how pages are used, and advertising technologies can attribute a campaign or associate browsing behaviour with marketing identifiers. A single technology used for multiple purposes is assessed against the requirements for each purpose, rather than characterised as essential merely because one aspect is useful.

The category matrix below explains when an affirmative consent or a qualifying statutory exception applies and what may stop working after refusal. We will not use a purportedly essential classification to override user choice for behavioural advertising. A feature designed solely to personalise promotions is not technically necessary for a consumer to log in, manage their Account or obtain previously purchased digital content.

A functional technology serving only a requested appearance or interface preference must be distinguished from a cross-site behavioural profile. Labelling a script "analytics" is insufficient to determine its legal treatment: the processing purpose, aggregation method, recipients, onward use, ability to object and retention all matter. Any combination with advertising or cross-site identity matching normally removes reliance on the narrow statistical exception.

Cookie categories

5. Lawful basis and consent

The Privacy and Electronic Communications Regulations generally require information and valid consent before storing or accessing information on a person's device, unless a relevant statutory exception applies. Necessary communication or strictly requested service functionality may be exempt, and any further qualifying exception is subject to its legal conditions. Where consent is required, it must be informed, specific, freely given and indicated by a positive action; pre-ticked selections and continued browsing alone do not provide valid consent.

Our preference controls allow a user to refuse optional non-exempt technology and change that refusal later without losing core account features. The UK GDPR may separately apply to personal data generated by the same technology and requires an Article 6 lawful basis. Consent for device access, marketing email and processing sensitive profile fields are distinct choices and are not bundled with general Terms & Conditions acceptance. Withdrawal operates prospectively without invalidating previously lawful processing.

Current UK rules recognise narrowly defined exemptions for communications, strictly necessary requested services, qualifying statistical purposes, requested appearance/functionality and emergency assistance. A qualifying statistical or appearance use requires clear information and a simple, free means to object; it is not a blanket exemption for all analytics or personalisation. Advertising measurement, cross-site profiling and multi-purpose trackers that go beyond an exemption require valid prior consent. We classify each purpose against the current rules before activating storage.

6. Cookie inventory and example technology

The technology inventory describes the relevant functional categories and their intended use and retention boundaries. A session identifier is different from an advertising identifier: the former supports account security and the latter can enable marketing measurement or personalisation. The categories are not a grant of permission to deploy every listed technology; a technology may be activated only if the applicable law, website setting and user preference permit it. Providers' current notices should identify any third-party service that receives information through a specific integration.

Duration is measured from the creation or most recent permitted refresh of a stored value, not from the date you first read this Policy. Some security values change more frequently than a login cookie, and a preference record may outlast a browsing session solely to preserve your choice. A device identifier should not remain indefinitely without justified need and applicable lawful permission. Where provider settings impose a shorter limit or law requires one, that shorter period controls.

A cookie or storage entry is meaningful only when the technology name, real provider, purpose and lifespan reflect the deployed configuration. Entries describing a category do not establish that a particular third-party tag is installed. Where a provider changes, the user-facing inventory and control interface must be updated before the new non-exempt purpose is enabled; a generic acceptance of a previous supplier is not permission for a materially different one.

Technology inventory

7. Third-party cookies and embedded services

A third-party payment interface may apply essential security checks when you authorise a card transaction. Embedded media, analytics scripts or marketing pixels may also set storage or access information if enabled. The fact that code is supplied by another business does not remove DateFoundry's responsibility to assess whether integration into its site is lawful and adequately explained. Before deployment, we obtain information about the provider, purposes, storage periods and transfer arrangements.

Links to independent websites work differently: clicking a link may take you to another controller's service, where its own policy applies. We cannot control cookies created solely on that unrelated destination. We do not treat every third-party feature as necessary; where it is optional and non-exempt, access to the feature and activation of associated technologies should follow the consent choice applicable to it.

8. Managing preferences

Use the site's cookie or privacy preference controls when presented to accept, refuse or revise non-essential categories. Changes should take effect for future storage and access, and rejection should be at least as practical as consent. You may also remove cookies from browser settings, restrict third-party storage or use a private browsing session, although clearing a preference cookie may require asking you to choose again. Some browser tools block essential storage and can therefore prevent reliable account sign-in or checkout.

If your device is shared, another user may overwrite preferences, and browsers or devices may not synchronise choices automatically. A choice made for optional tracking does not cancel a purchased token pack or erase financial records. To exercise personal-data rights, use the Privacy Policy process, since merely deleting local cookies may not affect information already lawfully stored in a server-side account ledger.

Refusing and withdrawing permission for non-exempt technologies must be as accessible as accepting them. Where a statutory statistical or appearance exemption applies, the objection control is separate from consent and must also be simple and free. We will not obscure refusal in a second-level menu while presenting an immediate "accept all" control. An already-started optional integration should cease future storage or access after withdrawal, subject to technical and legal requirements.

9. Retention and review

Necessary session values expire when no longer required, within the time limit set for the session and applicable security purpose. An opted-in persistent login may survive longer, but must remain subject to account controls and device logout. Optional measurement or advertising identifiers should have a declared purpose and bounded lifetime, with permissions and consent records reviewed when providers or configurations change. A consent decision record may be retained to demonstrate that a request to enable optional storage was appropriately handled.

We periodically test the website using a fresh browser state and a refusal of optional tracking to check whether unintended technologies appear before choice. We also check scripts introduced by theme, payment, membership or chat features after updates. Categories and retention periods are revised where the implementation changes. A current inventory should reflect actual technologies in use rather than merely a library of technologies that might be deployed.

The lifespan of a cookie is not the same as the period for which the related server-side account, security or payment record may lawfully be kept. The retention period for consent evidence should be justified independently from that of an advertising identifier, and a consent record must not be used to track browsing behaviour for a different purpose. The inventory is reviewed after material code changes and after periodic tests using a fresh browser and a declined-consent state.

10. Do-Not-Track and browser signals

Browsers may communicate a Do-Not-Track setting or a separate privacy signal. Technical signals vary in meaning and may not universally express a legally sufficient choice for every purpose. Where a signal creates a legally binding requirement, we apply that requirement; otherwise, use the site's preference mechanism to communicate your choice about optional technologies. We do not claim that absence of a signal equals permission to set tracking storage.

The Service should not deliberately circumvent a user's refusal by replacing a cookie with covert fingerprinting or server-side identifiers serving the same restricted purpose. Where a device-level choice cannot be honoured for a particular essential mechanism, we describe its purpose and explain the functional consequence of disabling it through browser settings.

11. Children and age

DateFoundry is for adults aged at least 18 and does not intentionally offer an account experience to minors. Cookie and device information must not be used to profile children for dating-related promotions. We may use minimal security information to investigate credible underage use and safeguard persons who may be affected, subject to the Privacy Policy and applicable law.

Parents who believe a child has created an Account should contact info@datefoundry.com. They should avoid sharing a child's private communications or photographs beyond what is reasonably necessary to identify the reported issue. Access restrictions and data handling will be assessed proportionately, with priority given to safety and lawful retention.

12. International data flows

Storage and access technologies may involve a provider operating outside the United Kingdom or receiving information in another country. Where personal data is transferred internationally, the Privacy Policy explains the lawful transfer mechanisms, including relevant adequacy arrangements and contractual safeguards. The geographical location of a script supplier does not, by itself, establish that a transfer is lawful; the data flow, recipient and purpose are assessed together.

A third-party advertising or analytics service should not be granted access to intimate dating-profile content merely because its script runs on the website. Appropriate data minimisation and permission boundaries are especially important where a visit or profile action can reveal sexual orientation or relationship preferences. You may ask about relevant safeguards through the privacy contact channel.

13. Changes to this Policy

We may amend this Policy to reflect new security functionality, a revised user-preference mechanism, a provider change or evolving law. A material new non-exempt purpose will not be treated as automatically authorised by an older acceptance that did not cover it. When a fresh choice is required, the consent interface should request it before the new technology is enabled.

We record the version and effective date for transparency and review the inventory against the deployed website. An update to written wording cannot retroactively justify storage that should have required earlier permission. Previous contractual and privacy rights are preserved where legally applicable.

14. Contact and governing law

AMORIAX LTD, trading as DateFoundry, handles questions about device technologies at info@datefoundry.com. When reporting a cookie issue, provide the browser type, approximate time, page and the choice made; do not send passwords or payment-card data. Requests about personal information should follow the Privacy Policy, and an unresolved data-protection concern may be raised with the UK Information Commissioner's Office.

This Policy is interpreted under the laws of England and Wales, subject to mandatory consumer and data-protection rules that may apply elsewhere. A refusal of non-essential tracking is not a contractual breach. Where relevant law grants a right to object or withdraw permission, that right remains available irrespective of other service terms.

15. Operational Maintenance Checklist

Before adding a plugin, marketing tag or payment integration, the operator should map each storage item, its provider, purpose, duration and destination; classify whether an exception applies; and, where necessary, prevent activation until the required permission is obtained. The classification should be checked both for a fresh visitor and for a logged-in adult with different consent settings. Consent records and an effective withdrawal method should be retained in a proportionate manner.

After major releases and at suitable scheduled intervals, the deployed site should be scanned for unexpected scripts, persistent values and sharing of identifiable or sensitive dating information. The inventory should reflect actual versioned technology and any third-party processing, and the user-facing controls should be retested. A failed preference control or tracking script deployed prematurely requires prompt remedial action, not merely a textual change to this Policy.

The operational check records the actual cookie names, storage keys, host domains, parties, precise expiry and processing purposes seen in an unauthenticated visit, registration flow and payment flow. Tests are repeated after the user refuses optional technologies and after consent is withdrawn. Any unlisted or unexpectedly active tracker is disabled until an appropriate notice and lawful configuration are in place.

DateFoundry · Cookie Policy · v2.1 · 8 October 2026. Published on the website; subject to update; the current published version governs.