Angleserve

This is the Product Schedule for Angleserve, a content operations product within the Adeimantos AI suite, accessed at angleserve.pro. This Schedule is incorporated into and forms part of the master Terms of Service, which govern your use of the Service, and the master Privacy Policy, which describes how Adeimantos Ltd handles your personal data. Where this Schedule is silent on a contractual matter, the master Terms of Service govern. Where this Schedule sets product-specific contractual terms, those terms apply only to Angleserve and only to the extent of the variation. The master Privacy Policy is supplemented — not overridden — by the data-handling specifics recorded in this Schedule.

iAbout this Schedule

The master Terms of Service require each product in the Adeimantos AI suite to operate under its own Product Schedule. This document is that Schedule for Angleserve. It records the data sources, processors, cookies, and product-specific provisions that the master documents leave to be set per-product.

Adeimantos's roles in respect of personal data

Adeimantos Ltd's role under UK GDPR depends on the category of data processed through Angleserve:

• Controller — for account and technical data, including account information (name, email, password hash, role, timestamps), authentication artefacts, consent records, technical logs, and any other personal data that relates to identifying or supporting users of the Service itself. Full controller details and ICO registration are set out in the master Privacy Policy.
• Processor — for Project Content, meaning everything the Admin uploads, generates, organises, or imports within their workspace (brand voice profiles, campaign briefs and stylistic settings, posts, content templates, brand documents, imported synthesis, funnel canvas state, review artefacts, and any associated generation logs). Where Project Content contains personal data of identifiable individuals, the Admin (or the organisation on whose behalf the Admin acts) is the Controller of that data; Adeimantos Ltd processes it solely on the Admin's documented instructions to deliver the Service. The Article 28 terms applicable in this capacity are set out in section v.

iiThe product

Angleserve is a content operations workspace for marketing operators running content for a brand. It supports the planning, drafting, organising, and reviewing of marketing content within a project workspace. It is a drafting and intelligence tool in the sense set out in section v of the master Terms of Service: it produces drafts, it does not connect to or publish to any third-party platform, and it does not act as a legal, tax, financial, or marketing adviser.

Business-to-business product

Angleserve is a business-to-business tool. Both the Admin and Client roles access the Service in connection with their trade, business, craft, or profession — the Admin to operate marketing content for a brand, the Client to review that content as part of brand governance. By creating an Admin account or redeeming a binding code as a Client, you confirm that you are accessing the Service in a commercial capacity, in line with the business users provision in section iv of the master Terms of Service. The Consumer Rights Act 2015 and other consumer protection legislation do not apply to your use of Angleserve.

iiiRoles & access

Angleserve has two roles, and access to data is scoped accordingly.

• Admin The marketing operator who owns the project workspace. Admins create projects, build brand profiles, plan campaigns, draft content, organise the funnel canvas, and invite a Client to review. During private alpha there is one Admin per Angleserve deployment.
• Client A reviewer invited by the Admin via a single-use binding code. Clients self-onboard at /bind by entering the code and choosing a password. Clients have read-only access to campaigns, posts, and the funnel canvas, with the ability to record an approval status and feedback notes on individual posts. Clients cannot create, edit, or delete content.

Binding codes are single-use, expire on first redemption, and are issued by the Admin from within the workspace. A Client account, once bound, is associated with the project that issued the code and can only access data within that project. By redeeming a binding code and creating a Client account, the Client agrees to be bound by the Adeimantos AI master Terms of Service and this Schedule, and acknowledges the master Privacy Policy. The Admin is responsible for ensuring that any recipient of a binding code is authorised to enter into these Terms in the recipient's commercial capacity.

ivData we process

Angleserve processes data in two categories, reflecting the role split set out in section i. All processing falls under the contractual basis described in section iv of the master Privacy Policy (Stream 1).

Where Adeimantos Ltd acts as Controller

The following categories relate to identifying or supporting users of the Service itself. Adeimantos Ltd is the Controller of this data, and processing is governed by the master Privacy Policy:

• Account information — name, email address, hashed password (bcrypt), role (Admin or Client), and timestamps for account creation and last sign-in.
• Authentication artefacts — session tokens issued by NextAuth, single-use binding codes, and CSRF tokens.
• Consent records — Consent records — the document type, version, salted SHA-256 hash of the IP address (the raw IP is not retained), user agent, and timestamp captured at the point of acceptance of these Terms (see section iii).
• Technical logs — IP address, user agent, error logs, and request timestamps necessary to operate and secure the Service.

Where Adeimantos Ltd acts as Processor

The following categories together comprise Project Content. Adeimantos Ltd processes Project Content on behalf of the Admin (or the organisation on whose behalf the Admin acts), who is the Controller of any personal data within it. Processing is governed by the Article 28 terms set out in section v:

• Brand profiles and campaign content — brand voice profiles, campaign briefs and stylistic settings, posts (manually authored or, when AI features are active, generated), content templates, and uploaded brand documents.
• Funnel canvas state — stage definitions, post placements, connection arrows, sticky-note comments, and saved viewport position.
• Review artefacts — approval status and feedback notes recorded by the Client against individual posts.
• Imported synthesis — positioning analysis JSON imported by the Admin. Where this material refers to third-party companies (for example, competitor names or descriptions), it is processed as commercial information rather than personal data; competitor names are stripped before being passed into any drafting context.
• Generation logs — for each invocation of an AI drafting feature (see section ix), Angleserve records the prompt context, model invocation metadata (timestamp, model identifier, latency), and resulting output, stored against the relevant post for calibration and audit. Generation logs are retained for the life of the Admin's account and are returned or deleted on termination in line with the end-of-services provision in section v.

Retention

Retention follows the master Privacy Policy: account data and Project Content are retained for the life of the account, plus a limited period after closure for legal, tax, and dispute-handling purposes. On termination, Project Content is returned or deleted in accordance with the end-of-services provision in section v. Security and operational logs are retained for 30 to 90 days.

vAdeimantos as Processor — Article 28 terms

Where Adeimantos Ltd acts as Processor in respect of Project Content under section i, the following terms apply alongside the master documents to satisfy UK GDPR Article 28(3). The Admin (or, where applicable, the organisation on whose behalf the Admin acts) is the Controller for the purposes of this section.

• Subject matter, duration, nature, and purpose. The processing comprises hosting, organising, retrieving, displaying, transmitting to AI model providers (where AI features are active under section ix), and deleting Project Content for the purpose of providing Angleserve to the Admin. Duration is the term of the Admin's account, plus any agreed transition period and any retention required by law.
• Categories of data and data subjects. The categories of personal data and data subjects within Project Content are determined by the Admin. Special category data is not encouraged; the position where it is uploaded notwithstanding is recorded in section x.
• Documented instructions. Adeimantos Ltd processes Project Content only on the Admin's documented instructions, constituted by the master Terms of Service, this Schedule, and the Admin's interactive use of the Service. Any processing required by UK or other applicable law will be notified to the Admin before processing, unless that law prohibits notification on important grounds of public interest.
• Confidentiality. All personnel of Adeimantos Ltd authorised to process Project Content are bound by an obligation of confidentiality.
• Security. Adeimantos Ltd applies the technical and organisational measures described in section x of the master Privacy Policy.
• Sub-processors. Adeimantos Ltd engages only the sub-processors named in section vii of this Schedule. The Admin grants general written authorisation for these sub-processors. Adeimantos Ltd will give the Admin reasonable prior notice of any addition or replacement of a sub-processor through an update to this Schedule, and the Admin may object on reasonable grounds, in which case the parties will discuss in good faith.
• Assistance with data subject rights. Adeimantos Ltd will provide reasonable technical assistance to the Admin to enable a response to data subject requests concerning Project Content, and will refer to the Admin without undue delay any data subject request received directly that concerns Project Content.
• Breach notification and security assistance. Adeimantos Ltd will notify the Admin without undue delay on becoming aware of a personal data breach affecting Project Content, providing the information set out in Article 33(3) to the extent then available, and will assist the Admin in complying with Articles 32 to 36 to the extent appropriate to the nature of the processing and the information available to Adeimantos Ltd.
• End of services. On termination of the Admin's account, Adeimantos Ltd will, on the Admin's written request, return Project Content in a structured machine-readable format. In the absence of such a request, Project Content is retained on the Admin's behalf in line with the retention periods set out in section ix of the master Privacy Policy (typically the life of the account plus a limited period for legal, tax, and dispute-handling purposes, up to six years for tax records). The Admin may at any time request earlier deletion of Project Content, in which case Adeimantos Ltd will delete it within thirty (30) days of the verified request, subject to any retention required by law. Anonymised or aggregated data derived from Project Content may be retained indefinitely. Where the Admin requests an export under this section, the export is delivered in JSON format and is identical in structure to the per-account export available at /api/account/export.
• Audit and information. Adeimantos Ltd will make available to the Admin information reasonably necessary to demonstrate compliance with this section. Where the Admin reasonably requires an audit, this is satisfied by Adeimantos Ltd providing relevant policies, summaries of recent third-party assessments where available, or arranging a remote interview, in each case on reasonable notice and at the Admin's expense.

viStream classification

If a future version of Angleserve introduces public-signal processing, this Schedule will be updated to record the change and the relevant Stream 2 machinery from the master Privacy Policy will be brought into scope, with prior notice to account holders.

viiNamed processors

The processors used by Angleserve, each engaged under a written data processing agreement, are:

• Hosting and infrastructure — Fly.io, Inc. (the provider hosting the Angleserve application and the SQLite database that backs it). This processor stores all Project Content and account data on Angleserve's behalf. Compute and storage are deployed in the London region (lhr); encrypted off-host backups are written to an EU-region S3-compatible object store. Where Fly.io's group standard requires onward transfers outside the United Kingdom, those transfers are governed by the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as appropriate (see section xi).
• Transactional email — None currently engaged (system emails are handled via internal infrastructure; no third-party processor is currently engaged). No marketing emails are sent from Angleserve.
• AI model provider — Anthropic, PBC (Claude API), engaged on a no-training endpoint such that prompts and completions are not used to train Anthropic's foundation models. Used solely to generate drafts on behalf of the Admin within the admin-facing surfaces of Angleserve; the Client role does not invoke AI features. Inference is performed in the United States. See section ix.