Privacy

Privacy notice

Company edition prepared 12 October 2026; effective from publication.

1. Who is responsible

This notice explains what happens to information when you visit this website or send CAFFTER a message. CAFFTER LABS LTD is the controller responsible for the personal information described in this website-and-enquiry notice. Its company details and correspondence and service address are in Business details at the end of this page.

For any privacy question or request, the public support and privacy contact is support@caffter.com.

2. What this notice covers

This notice covers two things: visits to this public information website, and messages that people choose to send to the public support address or the business/service address.

This effective website notice does not cover the CAFFTER app, which is still being built. That includes accounts, business profiles, Business Activity, uploaded media, AI processing and connected platforms. Proposed future service privacy wording appears below, but is not yet effective and does not describe app processing already available to the public. Its release depends on confirming the actual processing and legal requirements.

3. What information is handled

When you visit the website

The website is a set of simple pages. It has no contact form, no account sign-up, no payments, no upload feature, no analytics or advertising trackers, no cookies or browser storage, no third-party embeds and no scripts running in your browser.

The website is hosted using Cloudflare Workers Static Assets. To deliver and protect the site, Cloudflare may process technical information such as your IP address, the page or URL you asked for, details of your browser, device and system, timestamps, and traffic-routing and security data. CAFFTER has not set up client-side analytics, advertising tracking, third-party embeds or client-side scripts.

When you get in touch

If you contact CAFFTER, the information may include your name and contact details, your message and anything you choose to attach, and the correspondence and short case notes needed to reply.

Please don't send passwords, sign-in codes, access tokens, payment details, identity documents or customer records unless CAFFTER has specifically confirmed that they are needed and given you a suitable way to send them.

4. How messages are received and answered

The public support and privacy address is support@caffter.com. Cloudflare Email Routing forwards incoming messages to the Gmail inbox used by the person authorised to handle enquiries for CAFFTER LABS LTD.

Replies are sent manually from the Gmail address used to handle enquiries, which you will see, rather than from support@caffter.com.

This notice does not set up any automatic reply, any marketing use of your message, any additional person reading the mailbox, or a guaranteed response time.

5. Why information is used, and the lawful basis

Everyday questions and support

CAFFTER LABS LTD uses the least information needed to understand your enquiry, reply and follow up, keep the website and correspondence secure, and keep a short record in case the problem comes back or you raise a complaint later. It relies on legitimate interests for these limited purposes, taking account of what you would reasonably expect, the likely impact on you and the safeguards described in this notice.

Privacy-rights requests

If you make a privacy-rights request, CAFFTER will use the least information needed to identify you, assess the request and respond. The lawful basis, and whether any identification step is needed, depend on the circumstances and are recorded when the request is handled. You won't routinely be asked for identity documents.

Other exceptional records

A complaint, a security incident or a documented legal hold may mean keeping a limited record for that specific legal, security or dispute purpose. For each one, the reason, the lawful basis, the minimum information kept and the next review date are recorded.

6. Who else is involved, and international transfers

Enquiries are meant to be seen only by the person authorised to handle support and privacy for CAFFTER LABS LTD, and by the services that carry or store them: Cloudflare, for routing incoming email and delivering the website, and Google LLC, through the Gmail inbox that receives messages.

Cloudflare and Google LLC both operate and process information internationally. Both say publicly that they use the UK Extension to the EU-US Data Privacy Framework (DPF) for transfers from the UK to the US. Cloudflare also describes contractual safeguards under its self-serve Data Processing Addendum (DPA) where it applies. These are the providers' own statements; CAFFTER has not independently certified those frameworks. CAFFTER does not claim UK-only storage, Google Workspace protections, a CAFFTER-specific processor or DPA arrangement with Google, or any Cloudflare localisation set up specifically for this project.

7. How long information is kept

For an everyday enquiry or support case, CAFFTER keeps the relevant messages while they are needed to resolve it, and for six months after the case is closed. If they stop being needed sooner, they should be deleted sooner.

A monthly review picks out cases that have passed that point and removes them at the next review, no later than seven months after closure. Attachments and identity copies that are no longer needed are removed promptly.

For a complaint, privacy request, security incident or documented legal hold, only the minimum record justified for that purpose is kept. The reason is recorded, together with a next review date no more than 90 days away. This is not a blanket six-year retention rule.

Deleting a message from the inbox, sent items, exports and paper records that CAFFTER controls does not immediately delete it from the providers' backup or security systems. Google says deleted Gmail messages first move to the Bin and are permanently deleted after 30 days, unless deleted for good sooner; its wider storage systems and encrypted backups can keep data for longer under its published deletion process.

These retention periods apply to the company’s handling of website enquiries from publication of this edition. The manual process includes checking correspondence, keeping minimal case records, tracking privacy-request deadlines and carrying out the monthly retention review.

8. Your rights

Depending on the circumstances, you may have the right to access, correct or delete your information, to restrict or object to how it is used, and to receive it in a portable form. Some rights are limited or don't apply to every lawful basis, and each request is assessed under the law that applies at the time.

You can also raise a concern with the UK Information Commissioner's Office. Contacting the ICO doesn't stop you from contacting CAFFTER first.

9. Cookies and automated decisions

The website is built not to set cookies, and it runs no analytics, advertising or AI. When the previously deployed version was checked, no CAFFTER client-side script or tracker and no Set-Cookie response header were found; each production release is checked separately after it is deployed. This is separate from the technical processing Cloudflare carries out on its servers, described above. CAFFTER does not use information from website visits or enquiries to make decisions about people by automated means alone.

10. Changes to this notice

This company edition takes effect when it is published and does not describe the company as operating before its incorporation on 9 October 2026. Earlier records retain their historical provenance. This notice will be updated if the website, the providers, the purposes or the way enquiries are handled change.

Future Caffter app Privacy Notice — not yet effective

Service status: The website and enquiry notice above applies now. The approved app privacy wording below is proposed and not yet effective. It does not mean the listed app processing, permissions, deletion, reporting or retention controls are operating. The actual service and privacy release require separate verification and a release decision.

Caffter Global Privacy Notice

1. Who we are

Caffter is operated by CAFFTER LABS LTD.

For data-protection purposes, Caffter is the controller for the personal data described below where Caffter determines why and how it is processed. For some Business User content, Caffter may instead act as a processor on the Business User’s documented instructions; section 4 and the Business Data Processing Addendum explain that distinction.

Contact for privacy questions, rights requests and privacy complaints: support@caffter.com.

Caffter’s exact geographic service address is published on Caffter’s legal pages. The address remains available on the public legal pages.

2. What this notice covers

This notice is designed to cover, once the relevant features are legally released and implemented:

Third-party services may process data under their own privacy notices where they act as independent controllers. A link to or integration with a third party does not make its processing Caffter’s processing.

3. Categories of personal data

Depending on the feature used, Caffter may process:

Account and authentication data

Name, email address, account/user identifiers, authentication-provider identifiers, profile image where supplied by the identity provider, session/security information.

Age-eligibility confirmation, Business/Consumer capacity selection, declared country/region, Terms/AUP/DPA version accepted, document hash/version, acceptance timestamp, platform/app version and any separate permission/consent record.

Business Profile

Business name, category, services, style/voice preferences and other context the user chooses to provide.

Business Activity

Descriptions, instructions, factual observations, intended marketing messages and other text provided for content generation.

Uploaded media

Photos, videos, metadata retained by the implemented upload pipeline, and personal data visible or audible in the media. Media may incidentally contain information about customers, staff or other third parties.

AI data

Relevant Business Profile context, Business Activity input, instructions, prompts created by Caffter, uploaded media where a model feature requires it, generated captions/content and safety/operational metadata.

Connected-service data

Provider/platform name, provider account/page/profile identifiers, display names/handles, permission status, connection/disconnection events and secure access credentials/tokens where the authorised architecture requires them.

Publishing records

Selected destinations, approved content/version, approval evidence, request/result timestamps, provider identifiers returned by the provider, publishing state, uncertainty/reconciliation evidence and idempotency/reliability records.

Support correspondence, complaint details, privacy-rights requests, abuse reports, security incidents, legal holds and records needed to establish or defend legal claims.

Technical and security information

App version, operating system/device information, coarse network/security information, request/response metadata, authentication/security events, crash/error and service-performance information to the extent actually collected.

Marketing preferences

Separate opt-in/opt-out and suppression records if direct marketing is introduced.

Public website technical information

The current public website has been implemented as static pages without first-party analytics/advertising trackers. Its host may process ordinary network/security data such as IP address, requested URL, browser/device information, timestamps and traffic/security metadata.

4. Our role: controller or processor

Our role depends on the particular purpose and who decides why and how the personal data is used, not simply on whether a record is called a Business Profile, photograph, support ticket or security log.

Where a Business User determines the marketing purpose and instructs us to handle personal data in Business Activities, media, drafts or approved publishing, we act on that customer’s behalf under the DPA. A customer may itself be acting for another controller, in which case the required chain of instructions and authority must exist. Providing technical security for that instructed processing does not automatically make all of it our independent-controller activity.

We act as controller for processing whose purposes and essential means we determine, such as administering our own account relationship, protecting our service against abuse and meeting our own legal duties. Those purposes require their own lawful basis and notices. We do not obtain an unrestricted right to reuse customer-controlled content by calling it security, support or analytics data.

A Consumer or Business selection is not, by itself, a controller/processor determination. The DPA does not convert our own purposes into processing on someone else’s behalf or remove an individual’s rights.

5. Where data comes from

We may obtain data:

Business Users must ensure they are entitled to provide personal data about other people to Caffter.

Personal data may reach us indirectly through a customer’s Business Activity, uploaded media, a Connected Service or a report. Where we process it solely for a customer, that customer is responsible for the notices required of it, and we provide the assistance required by the DPA. Where we collect or use it for our own purposes, we assess and meet our own notification obligations; we do not assume that the customer’s general notice covers those purposes.

For processing subject to New Zealand’s Privacy Act, indirect collection on or after 1 May 2026 is assessed under IPP3A. Where the notification duty applies to us, we take reasonable steps to make the affected individual aware of the collection, its purpose, intended recipients, the collecting and holding agencies’ names and addresses, any law authorising or requiring the collection, and their access and correction rights, as soon as reasonably practicable, unless a documented legal exception applies. Solely holding or processing information on another agency’s behalf is assessed separately under section 11. Using that information for our own purposes may create our own responsibilities.

6. Why we use data and UK lawful-basis baseline

The following table explains the basis applicable to the identified purpose. Contract necessity applies only where the individual whose data is processed is a party to the relevant contract, or has requested necessary pre-contract steps. Our agreement with a business does not itself provide a contract basis for using an employee’s, client’s or photographed person’s data.

Purpose Our role and lawful basis
Providing an individual account holder with the core contracted account service and handling their service requests “We act as controller and use contract necessity only for personal data objectively necessary to provide the service to that individual.”
Managing contacts for an organisation’s account, including its authorised staff “We act as controller and rely on legitimate interests in administering and supporting that business relationship, after assessing necessity and the individuals’ interests and rights. We do not rely on a contract with the organisation as though each contact were a party to it.”
Customer-directed Business Profile marketing context, Business Activities, media, AI drafting and approved submission containing third-party personal data “Where we act on the customer’s behalf, the customer determines and documents the lawful basis, gives required notices and supplies lawful instructions; we process under the DPA. Additional conditions are required where special-category or criminal-offence data is involved. A customer instruction alone does not remove these requirements.”
Our own service security, abuse prevention and investigation of AI-content reports “We act as controller for the minimum information necessary for our legitimate interests in operating a safe service, subject to assessment of the effect on individuals. We rely on legal obligation instead only where an identified applicable law actually requires the particular processing. Instructed customer security/support processing remains within the DPA.”
Responding to rights requests, privacy complaints and legally compulsory disclosures “We act as controller to meet the particular data-protection or other legal duty that applies. We identify the applicable obligation rather than treating all provider-policy requirements as law.”
Establishing, exercising or defending legal claims “We act as controller where necessary for our legitimate interests in legal rights, subject to necessity, balancing, access restrictions and a limited retention period. Any sensitive information requires the additional legal condition that applies.”
Optional marketing or non-essential analytics/storage “We will use a separately assessed lawful basis and obtain consent where required. Optional consent is not bundled into Terms acceptance. Required device-storage consent and any applicable exception are assessed separately from the personal-data basis.”

A platform permission to send information to an AI provider is separate from deciding the lawful basis for that processing. Where consent is our lawful basis, withdrawal stops future processing based on that consent without affecting the lawfulness of earlier processing. A change of purpose requires a new assessment and any required notice or consent; merely changing this notice does not authorise it.

7. AI processing

When the relevant service is released, Caffter will use third-party AI services to assist with drafting and related functions.

Consumer availability is restricted as explained in the Terms. The application of the relevant AI provider contract to the intended downstream Consumer service must be established before that access is enabled; this notice does not assert a blanket provider ban on every downstream Consumer. The separate requirements concerning service mode, personal-data handling, permissions and supported territories still apply.

For an AI function requested through the service, Caffter will send only necessary data and will not intentionally send passwords, secrets, payment credentials, government identifiers or highly sensitive data to an AI service.

8. Who receives data

Depending on the implemented feature, categories can include:

Infrastructure/processors

Connected Services / user-directed recipients

App/build/store ecosystem

App, build, store or runtime services may receive personal data only where the released service actually sends them information relevant to this notice. The applicable recipients and their roles will be identified before that processing begins.

Insurers, legal advisers, accountants, regulators, courts or law-enforcement bodies where disclosure is lawfully required or reasonably necessary for legal rights.

Caffter will not describe a provider as a “subprocessor” unless the legal/data-processing relationship actually supports that classification.

9. International transfers

Caffter is UK-based and its service providers may process data in multiple countries.

Where UK/EU transfer rules apply, Caffter must use an applicable lawful transfer mechanism and complete any required transfer-risk assessment.

Depending on the verified provider arrangement, mechanisms may include:

10. Retention — proposed operational schedule

Data Proposed active-system retention
Account/profile/Business Activity/drafts/uploads Retained while needed for the active service. Following a verified deletion instruction, active-system deletion is targeted within 30 calendar days, subject to an earlier applicable legal deadline, the controller’s DPA return choice and narrowly documented lawful retention. A longer statutory response period does not automatically justify longer retention.
Connected-service access tokens/credentials New AI and publishing activity is stopped first. Credentials are used only for any necessary, authorised, non-publishing reconciliation and revocation during the bounded closure process, then disabled/revoked where available and deleted. They are not retained for later marketing or republication.
Deleted active-system data in backups Copies awaiting deletion are put beyond ordinary use, access is restricted and deletions are reapplied before any restored data returns to service. Deletion occurs as soon as practicable in the controlled expiry cycle, with a proposed maximum of 90 calendar days from the verified deletion instruction or end-of-processing instruction, unless applicable law requires particular data to be retained. A generic security label does not justify an indefinite backup exception.
Publishing/idempotency/reliability operational records While needed, operational records have a proposed maximum retention of 13 months from the relevant event. After account deletion, only the minimum separately justified evidence of the finality state, duplicate-prevention or a specific legal requirement/claim is retained. This is not permission to retain the post body, uploaded media, working credentials or a full activity history by default. Each retained category has a purpose, lawful basis, access restriction and deletion/review date; the operational maximum is not an automatic post-deletion entitlement.
Authentication/security logs 12 months unless an incident investigation requires longer
Closed ordinary support cases 24 months after closure
Legal acceptance/contract evidence Proposed 6 years after the relevant relationship ends, subject to qualified UK solicitor confirmation
Privacy complaints/rights requests/legal disputes Minimum necessary evidence while matter is active and thereafter only as justified for statutory/limitation periods
Marketing consent/suppression While relevant to demonstrate preference and, for suppression, as long as reasonably necessary to avoid re-contact
Provider-held copies Provider’s applicable deletion/retention rules, plus Caffter’s reasonable deletion/revocation requests where available

The stated deletion timing applies only after the storage, backup and provider arrangements are implemented to meet it.

Pseudonymised data remains personal data when an individual can still be identified using means reasonably likely to be used. Replacing a name with an identifier or hash is not, by itself, anonymisation. We treat data as anonymous only after assessing that people are no longer identifiable by such means. Where the DPA requires return or deletion, we do not substitute anonymisation without the controller’s documented instruction. Separate controller retention must be genuinely justified; we do not reclassify processor copies to avoid deletion.

11. Account deletion and provider disconnection

After proportionate verification of a deletion instruction, we first prevent new AI generation and publishing side effects for the affected account and stop queued work from starting. We then assess already in-flight requests. Where authorised and necessary, reconciliation uses status checks rather than a new publication or retry. An unresolved publication remains uncertain; deletion is not permission to republish or to erase the minimum evidence needed to avoid a duplicate before closure is made safe.

We then revoke or disable provider connections where supported and remove the stored credentials. We carry out the applicable deletion or, for customer-controlled personal data, the controller’s DPA return choice followed by deletion of copies. The process covers active systems, caches, subprocessors and controlled backup expiry, subject only to the applicable narrowly documented retention rules. We explain any outstanding provider action, retained data and its basis, and will not describe incomplete external deletion as confirmed.

These steps are a bounded closure process, not a reason to keep an account or token indefinitely. Account deletion does not itself remove posts from independent social platforms. Those platforms’ controls and rules govern their copies; we do not recreate or automatically delete a social post merely because the Caffter account is being deleted.

12. Your rights

Depending on applicable law and the facts, you may have rights to:

Rights are not absolute and exceptions can apply.

For UK data, you may complain to the Information Commissioner’s Office (ICO). You can still contact Caffter first.

Caffter must provide an electronic route for data-protection complaints, acknowledge a complaint within 30 days, and provide an outcome without undue delay after investigating it as appropriate.

For Business User content where Caffter acts as processor, Caffter may refer or support the request through the Business User/controller unless law requires Caffter to respond directly.

Rights-request timing

For requests governed by the UK or EU GDPR, we respond without undue delay and ordinarily within one calendar month, calculated under the applicable rules. Where the law permits an extension because of complexity or the number of requests, it may be up to two further months, and we explain the extension and reasons within the initial applicable period. We request any reasonably necessary identity or authority information promptly and proportionately. Any effect on the clock must be supported by the applicable law; we do not automatically reset deadlines whenever a message is exchanged. Other territories’ applicable deadlines remain available to their residents. You do not have to use one particular form to exercise a right.

Privacy-complaint timing

You may complain about our handling of personal data at support@caffter.com. For a UK data-protection complaint we acknowledge receipt within 30 days, investigate and communicate the outcome without undue delay, and keep you appropriately informed. The acknowledgement period is not a 30-day waiting period before investigation or a general deadline for resolving every complaint. Your right to contact the regulator is not removed.

13. Security

Caffter will use technical and organisational measures appropriate to the service when released. Controls include, as applicable:

No internet service is perfectly secure. This does not reduce Caffter’s legal obligations to use appropriate security.

14. Personal-data breaches

Where we act as processor, we notify the relevant customer/controller of a personal-data breach without undue delay after becoming aware and provide further information as it becomes available. We do not wait for a complete investigation or use the controller’s regulatory deadline as our own waiting period. Where we act as controller and notification is required, we notify the relevant regulator within the applicable legal time limit; under UK/EU GDPR this is without undue delay and, where feasible, within 72 hours of awareness, subject to the statutory risk test. Required notification to affected individuals is handled without undue delay under the applicable high-risk test. These duties are separate from complaint, rights-request and account-closure timelines.

15. Cookies, SDKs and storage/access technology

The current public information website operates without first-party analytics or advertising trackers or non-essential browser storage.

If the mobile app uses local/device storage or SDK functionality for authentication or core service operation, that technology and its purpose will be disclosed before release.

In the UK, PECR rules can apply to mobile apps as well as websites. Non-essential access/storage requires consent unless a current statutory exception applies.

16. Direct marketing

Service/security/legal messages needed to operate an account are different from marketing.

Caffter must not treat acceptance of the Terms as consent to marketing.

Before direct email/SMS/DM marketing is enabled:

17. Children

Caffter is 18+ only under the current provider/legal architecture. It is not directed to children or teenagers.

If Caffter learns that an under-18 account is using the service, it may suspend the account and take reasonable steps to delete or otherwise lawfully handle the data.

A future decision to admit minors would require a separate product/legal/provider/privacy design and cannot be made by merely changing this notice.

18. DPIA, data protection fee and records

Caffter will assess privacy risks and maintain the records and safeguards required for the processing it actually undertakes, including any required data-protection impact assessment, processing inventory and data-protection-fee assessment. The service privacy practices described here will be released only after the relevant provider, transfer, retention, deletion and complaint arrangements are verified.

19. Changes to this notice

Caffter may update this notice when processing changes. Where a change is material, users will receive appropriate notice before the changed processing begins when required.

A privacy update is not automatically a request for contractual consent. Where consent is the lawful basis, Caffter will use a separate granular consent control.

20. Contact

Privacy questions, rights requests and complaints: support@caffter.com.

The public legal pages must continue to display Caffter’s exact geographic service address where required.

Business details

CAFFTER is owned and operated by CAFFTER LABS LTD, company number 17510348, registered in England and Wales.

Company correspondence and service address: 30 Imperial Heights, Queen Mary Avenue, London, England, E18 2FJ.

Email: support@caffter.com