RenderedEventually diagnostic lab

Privacy

How audit data is handled

Rendered Eventually is operated by Manuel Madeddu. For questions about your data, contact zeroduedsgn@gmail.com.

Data processed

The application processes submitted URLs, publicly retrievable website evidence and, when authorised, read-only Search Console performance and URL Inspection responses.

Public session mode

Google access tokens are held in process memory and are not written into audit files or reports. Audit working files are temporary, isolated by browser session and automatically removed after the configured expiry. Users can delete their session immediately from the dashboard.

Registered accounts

Administrator and standard accounts retain submitted URLs, audit evidence and history until the user or administrator deletes them. Account passwords are stored as salted hashes. Authorised Google access and refresh tokens are encrypted at rest and associated with the individual account. Disconnect Google to remove stored credentials; revoke access in your Google account to remove authorisation at Google. Account creation emails include a generated temporary password. Password-change notifications contain no password.

Captured HTML and scheduled audits

New audits retain source HTML and browser DOM as plain-text evidence with explicit size limits. They follow the same saved or temporary audit retention. Saved accounts can authorise repeated analyses using their own Google connection. Schedule settings and copied URL inputs remain until the schedule or account is deleted. Removing the original audit does not remove its schedule. Completion/failure alerts send the account email and report summary/link through Resend, with recent delivery status stored for retries. Delete or pause a schedule to stop future runs.

Guest accounts

Guest audit working files are kept only in temporary server storage and expire with the session. Google access tokens are kept in memory only; no refresh token is requested or retained. Guest audits are isolated by browser session, including when visitors share the same guest username. Browser sessions and expired temporary working files are removed automatically on subsequent application activity, once any active stage finishes.

Private mode

The private operator controls stored run history, retention and deletion. Service-account credentials remain deployment environment variables and are not included in exports.

Setup drafts

Entered settings and uploaded URL files are kept in a short-lived draft when you connect Google or submit setup. Each draft belongs only to its logged-in user or guest browser session. Account drafts expire after 24 hours from the latest save; guest drafts use temporary storage and expire with the session. Drafts are removed after successful URL collection, logout or account deletion, and expired drafts are cleared on subsequent activity. Google credentials are never stored in a setup draft.

Google data

Google data is used only to produce audits and comparisons requested by the account holder. We do not use it for advertising or sell it. We follow the Google API Services User Data Policy, including its Limited Use requirements. Account invitation and security notification emails are sent through Resend. The application requests read-only Search Console access and does not request permission to modify a property.

Contact and deletion

Contact zeroduedsgn@gmail.com with privacy or deletion questions.