TrustyRunner · DigitalBanzai
Privacy and cookies
Last updated: 18 November 2026 · v1.4
This notice covers trustyrunner.com, the TrustyRunner application and its API at api.trustyrunner.com. TrustyRunner is a DigitalBanzai tool for technical website checks.
1. Controller and contacts
The controller is Radu Gabriel Tanasescu, operating the DigitalBanzai project, Viale Nicola Fabrizi 105, 41124 Modena, Italy.
For personal data enquiries and rights requests, contact info@digitalbanzai.it. For service support, you can also use support@trustyrunner.com.
2. Accounts and access
We process your email address, hashed password, internal identifier, plan, account status, language and available preferences. Passwords are not stored in plain text. Email and password are necessary to create and use an account; Free features remain available without registration.
We also process registration and access dates, sessions, browser information and identifiers derived from IP addresses for security. Verification and password recovery links use temporary codes. Do not send us passwords or access codes when requesting support.
At registration, we also store the date, language and versions of the Terms of Service you accepted and the Privacy Notice you acknowledged, to record this step together with your account data.
3. Scans and website data
When you start a scan, we process the requested website and technical information obtained from the resources checked: URLs, links, response headers, metadata, DNS, TLS and email configuration, check outcomes, limited evidence and execution information.
Free scans without an account do not create a personal history. The server temporarily retains the request and result to run the scan and allow that session to read it. Account scans are associated with your history, including results, dates, errors and any AI summary.
Requests to the website originate from our servers. That website and technical services queried may log our server’s IP address and the requested resources. We do not control their logs.
URLs and public evidence may contain other people’s personal data, obtained from the website or resource checked. This is not a collection intended to profile people. We use this information to identify and explain technical website issues, limiting evidence to the check performed. Public information can still be personal data: contact us if a result contains information about you, even if you have no account. Avoid submitting URLs containing credentials, access codes or confidential information.
4. AI summaries
AI Summary uses OpenAI to explain selected technical results. The application’s input includes outcomes, coverage, issue codes and suggested actions. It excludes user emails, passwords, IP addresses, sessions, tokens, website names or URLs, page lists, HTML and raw page text.
The summary is associated with the scan. We record attempts and AI quota consumption. The API setting store: false does not mean that the provider performs no processing or retains no technical logs.
5. Email and support
We use your email to verify registration, resend requested verification links and reset passwords. The application queue processes recipients, message types, language, dates, delivery status, attempts and errors; codes needed for links are encrypted in the queue.
Delivery uses TrustyRunner’s SMTP service on the VPS and the recipient’s mailbox provider. Messages already delivered to your mailbox remain under your and your provider’s control.
When you contact us, we use your address and message to respond. Support correspondence is separate from the automatic queue and is not automatically erased by the Delete account button. Retention depends on handling and closing the request and on information still needed to follow it up; you can request its erasure using the contacts above. We do not apply blanket ticket retention for hypothetical disputes.
6. Image conversion
The WebP converter on the website processes JPEG and PNG files directly in the browser: images are not sent to TrustyRunner. The previous account-only conversion API receives JPEG or PNG files and returns WebP; the following applies to that API. Processing takes place in memory and may use temporary files; the application does not build a permanent image archive. People or personal metadata in a file are part of the processed content. Technical request logs follow the rules below.
7. Quotas, security and logs
To apply Free scan limits, we use a protected code derived from the IP address that changes each day. To prevent abusive registrations, we use other IP-derived codes and consider attempts from the past 30 days. These counters store the codes, not the plain IP address. They still help distinguish requests and prevent abuse: we do not treat them as anonymous.
Web, email and infrastructure logs are separate: they may include plain IP addresses, dates, requested URLs, browser information, identifiers and operation status. They help diagnose faults and protect the service. Administrative access to data is limited to management and support activities.
8. Purposes and legal bases
- Requested service: account creation and management, access, email verification, password recovery, scans, history, quotas and service-related support rely on performance of a contract or requested pre-contractual steps (GDPR Article 6(1)(b)).
- Security and operation: abuse prevention, logs and diagnostics rely on our legitimate interest in service security and availability (Article 6(1)(f)). For third-party personal information in public evidence, the interest is performing the requested technical website check, limiting collection and use to that purpose. The requesting user’s contract is not treated as other people’s consent.
- Rights and deletion: handling privacy requests and preventing deleted accounts from being reactivated after recovery serve data protection obligations (Article 6(1)(c)).
The “I have read the Privacy Notice” checkbox confirms that you have read how we handle your data. It concerns this notice: it does not authorise other uses of your data or replace acceptance of the purchase terms for a paid plan.
9. Cookies
TrustyRunner uses one cookie only, a technical cookie, named trustyrunner_session. It keeps you signed into your account so you do not need to enter your email and password on every page or visit. It is not used for advertising tracking or profiling your habits.
The cookie is set by api.trustyrunner.com after login and expires after 14 days. Signing out, changing your password or having the session revoked can end access earlier. Normal use does not automatically extend its expiry. This cookie does not require consent because it is necessary for the login you request.
Access can persist after closing the browser. Use Sign out on shared devices. Removing the cookie in browser settings requires a new login. Server-side session records have separate cleanup.
The TrustyRunner frontend does not use analytics, advertising pixels, tag managers or fingerprinting. External websites reached through links have their own notices.
9.1. Search ideas (Jumpy)
When you start Jumpy, your browser requests suggestions directly from Google (including YouTube) and Microsoft Bing. Sources receive the initial keyword or phrase, the variations tried and your IP address. They may also receive their own cookies if your browser settings and protections permit this. They process these data under their privacy notices: Google and Microsoft. Requests to sources do not pass through TrustyRunner’s server. Avoid personal or confidential search terms.
What TrustyRunner stores. For Free, we do not store terms or results on the server. For Registered and Light, we store the initial term associated with a start and, when you save a collection, its suggestions, sources, date and “keep, maybe, discard” choices. Collections are private and linked to your account: they are not shared with other users or added to a shared cache. Providing Jumpy and the saving you request follow the legal basis for the requested service described in section 8.
How long we keep it. Saved collections remain available for 30 days from start, up to 10 for Registered and 30 for Light. Saving beyond the limit replaces the oldest collection. You can delete a collection from your account; account deletion includes these collections. Expired data are removed through periodic cleanup; the general backup rules in this notice apply.
Allowances and waiting periods. We retain technical start records for 30 days, then remove them through periodic cleanup, without terms or results for Free. Identifiers for users without an account are cryptographically derived from the IP address and change daily. The browser stores the last start time (tr-jumpy-last in local storage), solely to space collections apart, without analytics or advertising purposes.
10. Retention
The following distinguishes active data, technical records and copies. Application cleanup is periodic: expiry of use and removal of a record may happen at different times. Work still in progress must first finish or be stopped safely.
- Accounts: until deletion. Unverified registrations expire 48 hours after the initial request and are removed by periodic cleanup; resending a link does not extend the deadline.
- Account history: a 30-day window from scan creation and the plan limit (10 Registered results, 30 Light results). Older or excess completed scans are removed by periodic cleanup. Associated summaries and AI attempts follow their scan, protecting processing still in progress.
- Free scans: temporary results expire for reading 24 hours after completion; cleanup removes the target and result content. Technical identifiers used to prevent duplicate requests have a 35-day window.
- Quotas and abuse prevention: daily scan counters 35 days; registration abuse events 30 days. AI quota movements 13 months, preserving events still needed for the active annual plan period. Account-linked data is removed by account deletion except for the separate records described below.
- Sessions and codes: no longer usable after expiry or revocation; unusable records are removed periodically. For consumed codes, cleanup waits until expiry to support resend handling and consistent responses.
- Email queue entries with links: eligible for removal 48 hours after the link expires, then removed during periodic cleanup; messages still being processed must first be resolved.
- Ordinary service and infrastructure logs covered by rotation: an operational ceiling of 15 days.
- Database copies, including managed local release copies: at most 15 days from creation of each copy. File and configuration backups: at most 21 days from creation. These are copy lifetimes, not a guarantee that all data categories disappear within that period after account closure.
- Working files: removed when their use ends; remnants of interrupted work require cleanup. Backup retention does not replace that operation.
- Receipts for deleting individual scans: a 35-day window. Minimal account deletion ledger, its receipts and administrative audit records: kept separately from operational data. They currently have no automatic expiry. Their removal requires checking that they are no longer needed to enforce deletion during recovery or to reconstruct a specific administrative operation. They contain identifiers, metadata and, for administrative actions, the reason entered by the operator, not automatic copies of accounts or reports; we do not treat them as anonymous.
We therefore do not state a single 30-day deadline for every record to disappear from every archive. These are the current rules; residual copies are not used to continue providing service to a deleted account.
11. Deleting your account
Save any reports you want to keep before deleting your account. Once the request is accepted, you immediately lose the ability to view or download reports. The account and its history cannot be recovered, including through support. Permanent removal of application data continues automatically; you do not need to repeat the request.
Any remaining backup copies follow the retention cycle described in section 10. They are not an archive from which to request account recovery: a technical service restore preserves previously requested deletions. The personal data rights described in section 13 remain available as provided by law.
The service and its reports are also described in the Terms of Service.
Use Permanently delete account in the Account area, including on the free Registered plan. Once accepted, the request blocks access and revokes sessions. The procedure safely handles running work before removing the account and its associated application data.
Completed means removal from active systems has finished. It does not mean all backup copies or separate records have already disappeared. To prevent an old backup from bringing back a deleted account, we keep a minimal, encrypted record of the deletion outside the server too, on Google Drive. Before confirming completion, we verify that this record has been saved correctly. Following a restore, the ledger allows deleted accounts to be removed again before the service reopens.
A new registration creates a new account without recovering previous history. The procedure does not send a confirmation email to the deleted address. You can also request deletion or exercise your other rights by emailing info@digitalbanzai.it. You do not have to use the “Permanently delete account” button in the Account area.
12. Providers and transfers
The application and database run on an IONOS VPS in Germany. TrustyRunner’s email service is managed on that VPS. Authorised personnel and providers may process data within their management, security and support activities.
Backups and the deletion ledger are also held on Google Drive, currently through a personal account, encrypted before upload. Encryption does not make data anonymous or guarantee that the provider cannot access it: recovery requires keys. The deletion ledger recovery kit stored on Drive is itself encrypted with a passphrase that is not saved to Drive. Operational keys needed by the service remain protected on the server.
Google describes processing across different countries, including outside the European Economic Area. Its transfer framework describes adequacy decisions, the Data Privacy Framework and standard contractual clauses applicable to its services; its privacy policy describes other processing. The personal account is not a Workspace account and is not presented as covered by the corresponding business agreement.
OpenAI receives the technical input described in section 4 through its API. TrustyRunner account data is not part of that input. The provider’s technical processing is described in its API data documentation. We do not claim exclusively European processing or an absolute absence of provider retention.
We do not sell account data or use it for personalised advertising. Contact us for information about recipients and applicable transfer safeguards. These links do not replace our responsibility for TrustyRunner’s processing.
13. Your rights
You may request access and a copy, correction, erasure, restriction and, where applicable, portability. For processing based on legitimate interests, you may object on grounds relating to your particular situation.
Contact info@digitalbanzai.it. Where necessary, we request only information needed to verify identity. We respond without undue delay and within one month. Where permitted because of complexity or the number of requests, this may be extended by two further months, informing you within the first month and explaining why.
You may complain to the Italian data protection authority or the competent supervisory authority and seek a judicial remedy.
14. Updates
The date at the top identifies this version. We update the notice when services or processing change; material changes require appropriate information for affected people.
