PUBLIC PRELAUNCH DEMO / 5 NOVEMBER 2026

Privacy &
service status.

Aidan Brewis, trading as Integrate Your Systems, is the controller for this prelaunch website and its demo accounts. The proposed limited company has not been incorporated. This website demonstrates fictional workflows; it does not connect visitor or customer systems, create commercial commitments or operate verified production integrations.

Contact and your choices

Contact aidan.brewis@integrateyoursystems.com about this demo, access, correction or deletion of your account and associated data. You can use the public fictional walkthrough without an account. Do not enter customer records, secrets or sensitive information.

Account and session data

Production sign-up and login send your email address and password directly to Google Cloud Identity Platform. Google manages those credentials. The application verifies an email-verified identity token on the server. It stores the account identifier, session references, identity authentication/issue times, message allowance and draft workflow brief in Google Cloud Firestore in London. Your email stays in Identity Platform; the application does not copy it into Firestore. Each protected request checks current account security status with Identity Platform, so disabled or revoked access is refused. These checks request only the user identifier, enabled/verified status and revocation time. An essential Secure, HttpOnly session cookie keeps you signed in; sessions expire after one hour. Five demo messages are allowed per account, including after logging in again. You can delete your account using “Delete my demo account” beside the demo, after confirming your password and intent. Deletion blocks access immediately and removes the Identity Platform account, message allowance, every session and brief, any submitted pilot enquiry, and account-specific rate-limit records. An interrupted deletion can be retried safely in the same browser; contact us if you need help. A pending deletion record retains only the identity and security references needed to finish cleanup. A completed hashed security receipt remains for at least 24 hours to prevent old requests recreating the account; database housekeeping may remove it later. Global abuse counters and Google operational logs are separate and follow their own retention. The deletion retry reference and CSRF value may be held in browser sessionStorage until completion or the tab closes; passwords and identity tokens are never saved there. The application does not store your password or credentials in browser localStorage.

Fictional chat and draft briefs

The chat uses deterministic answers and fictional company records. No hosted language model or external model provider receives these requests. Chat questions are processed transiently by the server to produce the answer; they are not deliberately stored as a conversation history. The server stores the latest draft brief for the authenticated session. Only that session can download it. Logout deletes the draft and session; expiry blocks further access. Expired database records may remain until housekeeping or a deletion request; expiry is an access control, not a promise of immediate physical erasure. Form answers remain in page memory and clear on logout.

Optional pilot review requests

Creating a brief does not submit it to the business. The separate “Send this brief for pilot review” control requires a signed-in account and your explicit confirmation that the brief contains only system names and a workflow description, with no customer records, contact details or credentials. You also give permission for Aidan to review it and respond at your verified account email. The submitted copy includes only the system names, workflow goal, a reference hash of the saved brief, consent version and time, account/identity reference, review status and a draft qualification/proposal. Freeform decision answers are not copied into the enquiry. Your email remains in Identity Platform and is looked up only when an authorised operator explicitly reviews contact details for a current consented request.

One latest enquiry is stored per account in the existing London Firestore database. Up to three new or revised submissions per 24 hours are allowed. Submission creates a private review queue entry and indicative draft terms; it does not reserve capacity, accept a pilot, issue a contract or invoice, send a message or authorise customer-system access. No marketing list is created. Submitted enquiries remain after logout. Review access expires 30 days after the latest explicit submission; asynchronous database housekeeping removes expired records later. Identical retries do not extend retention. You can withdraw the request in the same pilot-review panel, including after a new login, or delete your account to remove the submitted details sooner. Withdrawal leaves only an account revision/rate counter to prevent stale requests and rate-limit bypass; account deletion removes those too. Correspondence you separately send and Google operational logs have their own retention.

Hosting and operational data

Google Cloud provides the website, DNS, identity and application infrastructure, including Firebase Hosting and Cloud Run. Delivery and security processing can include IP addresses, request URLs, timestamps, browser metadata and error information. Google infrastructure can process operational metadata outside the application database region. Operational logs follow the configured Google Cloud retention, ordinarily 30 days for standard logs; mandatory audit logs can be kept longer. Avoid placing personal data in URLs. Email sent to the contact address is handled in Google Workspace. Google acts under the applicable service and data-processing terms; London storage does not mean all support or operational processing stays in the UK.

This site has no advertising, third-party analytics or externally loaded fonts. Essential account cookies are used only for the requested demo functionality. We use supplied account information to operate and secure the requested service and respond to requests, not for an unsolicited mailing list.

Why we process data and your rights

We rely on legitimate interests to provide the requested demonstration, prevent misuse and respond to enquiries. Required account information enables authentication and the five-message limit; without it, you can still use the public walkthrough. We do not sell account information or use it for marketing. You can request access, correction, erasure or restriction, object to processing, and request portability where the legal conditions apply. We normally respond to rights requests within one month, subject to lawful extensions and identity checks. Data-protection complaints will be acknowledged within 30 days and investigated without undue delay. You can also complain to the UK Information Commissioner. Contact the address above for processing or transfer information.

Service limits

The public workflow illustration runs in your browser using fictional examples. Reference compiler checks use synthetic records, not connected systems. Drafting a scope does not approve integrations or authorise writes. Planned adapters, model inference, automatic rollout and customer-facing integration operations still require engineering, independent verification and applicable customer permission. No certification, service-level guarantee or vendor partnership is asserted. Platform names identify compatibility targets; their owners have not endorsed this business.

Local development

When developers run a visibly labelled local disposable-account mode, password hashes and sessions are stored on that local server. It is refused in production. These local accounts are separate from Google production accounts.