What we collect, and what we do not.
Plain-language summary of how Daenah handles data. This is an initial policy for the marketing release and will be expanded before billing or accounts go live.
Read-only auditing
Daenah fetches and renders pages on the website you ask it to audit. It reads publicly reachable content and does not write to, modify, or publish anything on your site.
Google Search Console scope
If you connect Google Search Console, Daenah requests only the read-only Search Console scope. In the current connection milestone, it lists properties available to your Google authorisation and validates the exact property you choose. It does not fetch Search Analytics performance data or change audit findings, reports, or scores. You can remove the local connection or request Google revocation from project settings. We do not request write scopes.
Credentials and tokens
OAuth tokens are encrypted before server-side storage, used only for the authorised read-only connection, and never shared with third parties, exposed to the browser, or written into reports.
Data retention
Audit inputs and generated reports are retained only as long as needed to provide the service and show your history. You can request deletion of your reports.
Account deletion
When accounts are available, you will be able to delete your account and associated reports. Deletion will remove stored audit data and local connection credentials. You can separately revoke the Google grant from project settings or your Google Account.
This summary is not legal advice and will be replaced by a full policy before paid accounts launch.