Know what you share.
Know why it’s needed.
This notice covers the hosted Your Optimiser service at youroptimiser.com. The project maintainers operate the service. A self-hosted installation is controlled by its own operator and configuration.
Information the service processes.
Account information includes your email address, Firebase account identifier and authentication status. Workspace information includes connected repository identifiers, website URLs, project settings, business facts and goals you provide, quotas and activity records.
To perform an audit or repair, the service may process relevant source files, public page content, audit evidence, findings, proposed edits, check results, optional screenshots and pull request or deployment information. GitHub connection grants and installation identifiers support authorised repository access.
Operational records can include request times, network addresses, errors and service activity. Authentication and hosting providers also process information needed to run their services.
Why this information is used.
The information supports sign-in, workspace isolation, repository connection, SEO checks, proposed fixes, verification, abuse prevention, troubleshooting and usage limits. Project facts help the agent avoid unsupported changes.
The current application does not include advertising trackers or a third-party marketing analytics SDK. That does not mean the service is anonymous: authentication, infrastructure and support activity still involve data processing.
Providers and AI processing.
The hosted service uses Google Cloud and Firebase for hosting, authentication, storage, operational services and logs, and GitHub for repository authorisation, code changes and pull requests. A third-party AI provider processes relevant task inputs to generate assessments and proposed edits; inputs can include code, page content, project facts and screenshots.
AI providers may change. Their applicable terms and processing settings govern their handling of inputs. We do not promise that every possible provider configuration has the same retention or training policy. Do not provide unnecessary secrets, sensitive personal information or material you lack permission to process.
Firebase’s privacy information ↗Storage and access.
Workspace records are stored in a Firestore database selected for this application. The backend enforces tenant ownership. Service credentials are supplied through Secret Manager, and stored application credentials and connection grants are encrypted by the backend. Authorised operators can access systems when needed to operate and support the service.
These measures reduce risk; they are not a promise that every security incident can be prevented. Data may be processed in countries where infrastructure and AI providers operate. We do not promise that all processing stays in a single region.
Cookies and browser storage.
Firebase Authentication uses browser storage to maintain your sign-in state. The service may use session information for account and authorisation flows. You can clear browser storage or sign out; clearing it does not delete server-side account or workspace records.
Retention and your choices.
Account, project, audit and activity records are retained while supporting the service and its operations. There is currently no universal automatic deletion period for all record types. Infrastructure providers manage operational logs and temporary artifacts according to their configured lifecycles.
Disconnecting GitHub pauses related projects and removes their active connection authorisation from the workspace. It does not automatically delete historical workspace records or remove commits and pull requests already published to GitHub.
You can request access, correction or deletion of account and workspace data through the private contact process. Requests are handled manually and may require identity verification. Applicable law may give you additional rights; legal obligations, security needs and provider records can affect what can be removed.
Request a private contact channel →Changes to this notice.
This notice will be updated when the service’s practices change. The effective date identifies the current version. Material changes may also be communicated through the service. Contact the maintainers with questions before connecting data you are unsure about sharing.