Draft for review · Not yet effective

Privacy notice

Draft for review · Version 2026-09-30 · Not yet effective

This notice describes the Ultrafast implementation inspected for this draft. Company registration/address, lawful bases, retention decisions, hosting locations and provider contracts still need confirmation before publication. It does not certify legal compliance or describe every other AutoEgo product.

1. Who is responsible

Founding House Ltd, [BUSINESS / SERVICE ADDRESS], United Kingdom is the proposed controller for account administration, support and any other processing it determines. Contact [PRIVACY EMAIL] to ask about personal information. For organisation-directed processing, controller/processor roles and any required data processing agreement must be specified separately.

2. What the app processes

Voice: while listening is active, microphone audio and conversation context are sent to the configured realtime AI service for transcription and responses. Relevant conversation text and task results can be saved locally. Voice has its own controls.

Speech context: when enabled, the app can read the active app and window, selected and visible text, a page URL, pointer context and a short preview of recently copied clipboard text. OCR may extract text from screen pixels. Relevant context can accompany an AI request.

History: when recording is enabled, background activity capture can save timestamps, app identities, window titles, URLs and observed text in a local SQLite database. It responds to activity and idle checks. Focused-window image buffers support OCR and change detection; this History path does not persist a screen-video archive. Saved text and summaries may contain personal or confidential information.

History summaries and questions: selected saved entries can be sent automatically to a configured AI provider to create summaries. Asking about history also sends relevant excerpts. Recent model summaries can be included in voice-session context. Local storage does not mean all processing stays on the Mac.

Teach: a demonstration can retain screen video or fallback screenshots, action events, typed content outside detected secure fields, and narration/transcripts. Selected demonstration material is used by AI services to learn a skill. Demonstration media may be archived with the resulting skill.

Tasks and learned skills: instructions, relevant files or images, browser/page contents, results, local chat records and diagnostic task logs may be processed and saved. Computer actions can disclose content to the apps, sites and recipients involved in your requested task.

Account and support: signing in can process an email address, identity-provider data, account identifiers and authentication records through Supabase and your selected sign-in provider. Session credentials are stored in macOS Keychain. Information you send for support may include contact details and diagnostic material you choose to share.

3. Defaults and sensitive information

In the inspected source, History and speech-context preferences default to enabled. macOS permissions and onboarding also affect when capture can run. This draft does not describe those features as off by default or claim that a verified release consent flow already exists.

Secure-field text is skipped where the app detects it. This is not a guarantee that passwords or other sensitive information cannot appear in screen video, screenshots, OCR, clipboard previews, page contents or logs. No universal private-browsing exclusion or sensitive-content redaction guarantee is made.

Before capturing a conversation or other people's information, provide the notice and obtain the permission required in your circumstances. Workplace use may require additional organisational controls. Processing health or other specially protected information requires a separate assessment and any applicable additional legal condition.

4. Why information is processed

The intended purposes are to provide voice assistance, remember and retrieve activity, learn and execute requested tasks, authenticate accounts, provide support, protect the service and meet legal obligations.

Before release, the operator must approve a purpose-by-purpose lawful-basis register. Contract necessity may cover genuinely necessary service processing; security and support may involve assessed legitimate interests; legal obligations may require some records. Optional background collection and any special-category processing need their own analysis and, where relied upon, valid consent. Agreeing to terms or this notice is not blanket consent for all processing.

5. Recipients and international processing

The inspected code supports OpenAI or Microsoft Azure for configured AI processing; TypeSafe/Jev can receive task-routing input such as utterances and the frontmost app; Supabase supports account authentication. Google sign-in is optional. The exact release providers, contracting entities, processing regions and retention terms must be confirmed. This list is a code-based inventory, not a verified production subprocessor register.

A London-region authentication project alone does not establish UK-only processing for the whole product. Providers or support personnel may process information in other countries. Before release, the operator must identify those locations and the applicable transfer safeguards and explain how to obtain a copy where required.

Third-party apps and recipients may receive information as part of a task you request. Legal authorities may receive information where disclosure is required by applicable law. Provider access and disclosure must be limited to the applicable purpose and contractual arrangements.

No sale or advertising use is identified in the inspected Ultrafast capture code. The operator must verify business and analytics practices before making a company-wide no-sale or no-sharing promise.

6. AI training and retention

No general-model training pipeline was identified in the inspected app. History summary and question calls set store=False. That flag is not a guarantee of zero provider retention or a universal no-training agreement across every provider and endpoint. Provider settings, contracts, safety logging and retention exceptions must be confirmed before release.

Local History does not have a verified automatic expiry in this build. It remains until deleted through the relevant controls or otherwise removed. Chats, skills, demonstration archives and diagnostic logs have separate storage and deletion scopes. Account records, support messages, provider logs and backups need approved retention periods or sufficiently specific criteria: [RETENTION SCHEDULE TO COMPLETE].

Deleting a History interval removes matching database entries and affected summaries/search records. It does not promise forensic erasure from SQLite journals, system backups, previously sent AI requests, separate chats, or Teach archives. Each of those stores must be addressed through its applicable deletion process.

7. Your controls and rights

You can pause or disable History, use the available range/all-history deletion controls, manage app exclusions in builds containing those controls, disable screen sharing when speaking, stop Teach, and revoke macOS permissions. See Data controls. Exclusions apply to future History and speech snapshots; they do not erase previous records or replace Teach controls.

Sign-out clears the local account session; it does not by itself delete your account or local activity records. A production account-deletion and rights-request channel is still to be confirmed at [PRIVACY EMAIL].

Depending on applicable law, you may request access, correction, deletion, restriction or portability; object to relevant processing; withdraw consent without affecting earlier lawful processing; and complain to your data protection authority. UK residents can contact the Information Commissioner's Office. Identity checks must be proportionate. Requests will be handled within the applicable legal time limits; no unverified shorter service promise is made here.

8. Website connections and device storage

The reviewed landing page loads a font from Google Fonts, creating a request to Google that includes connection information such as an IP address. Its shader code is bundled. No advertising pixel, optional analytics tag or signup submission backend was identified in the reviewed static page. This is a source inspection, not a production network audit.

The eventual hosting provider can receive ordinary connection/security logs. [HOSTING PROVIDER AND LOG RETENTION TO CONFIRM]. Any later analytics, cookies or similar storage must be assessed and disclosed; obtain consent where legally required before enabling optional tracking. This draft does not add tracking or a cosmetic consent banner.

9. Security and updates

Account credentials use Keychain, and configured API connections use secure transport. The inspected History database and ordinary local content files are not shown to have application-level encryption. Device permissions, account access and disk protection therefore matter. No end-to-end encryption, SOC 2, ISO certification or zero-risk claim is made.

We will keep the effective notice dated and explain material changes. Further consent will be obtained where the law requires it. Before release, complete the operator/contact fields, retention and provider details, and verify the notice against the distributed build.