Privacy Policy
Version dated October 16, 2026. Digutils minimizes data processing as described below.
General provisions
- This Policy explains data processing when using Digutils. The Operator's legal details and contact channels are made available on the website.
- Digutils seeks to minimize data, collection purposes and retention. Lack of registration does not mean IP addresses and security metadata are never processed. Applicable data-protection law applies.
Data and purposes
- Depending on the feature, data may include calculation inputs, Ask Digutils queries, inbox addresses and messages, attachment metadata, IP and network identifiers, browser and request diagnostics, cookies, local storage and voluntarily supplied feedback.
- Purposes include executing requested operations, mail delivery, technical security, abuse prevention, troubleshooting, product improvement when enabled and applicable legal duties.
Calculators
- Ordinary tools do not create mandatory permanent user profiles or a complete history of calculations. Inputs may be processed to deliver results without intentional long-term retention.
- Do not send unnecessary passwords, private keys or sensitive documents. User-exported files are not automatically stored by the Operator.
Temporary mail and TTL
- Inbox addresses, timestamps, text messages, sender and subject metadata, limited attachment metadata and access/abuse identifiers may be processed.
- Inboxes normally expire after 30 minutes, extendable once up to 60 minutes from creation. Periodic cleanup removes expired data from active storage, not necessarily instantaneously or cryptographically from every device. Expired messages are not recoverable.
Attachments
- Actual file content, including inline images or other embedded MIME file parts, is intentionally not retained; transient processing is necessary to parse inbound email.
- Only filename, MIME type and size may be retained. Viewing, downloading and restoring attachment content are unavailable. Text extracted from supported mail parts may be kept until TTL.
Access protection and acknowledgement
- Mailbox tokens are returned to the client and only hashes are stored in the working database. Sessions, CSRF protection and rate limits help protect access.
- The web inbox-create button requires acknowledgement of Terms and this Policy, and the API requires an explicit acceptance flag. This is a client declaration, not verified identity or proof the documents were read, nor a substitute for any legally required separate privacy consent.
Ask Digutils
- If enabled, request text may be collected for up to 30 days to improve tool discovery without deliberately attaching IP, account or session IDs to those text entries.
- A user may voluntarily include sensitive information in the text; please do not. Technical HTTP logs remain separate.
Technical logs
- HTTP infrastructure may process IP, time, route, method, status and diagnostic details. SMTP logs may include sending and receiving email addresses, sending server IP/name, timestamp and delivery result.
- These metadata logs are separate from temporary mailbox lifetime and may remain longer than 30–60 minutes. Application logs minimize message content and tokens; deleting an inbox does not instantly erase SMTP metadata.
Retention and backups
- Mail content follows its TTL; Ask Digutils text logs, when enabled, are kept up to 30 days. Technical log retention follows separate rotation settings rather than an asserted fixed seven-day period.
- The normal infrastructure backup excludes the active temporary-mail data directory. Other historical, provider or system copies may have separate lifecycles. Immediate physical erasure across all media is not promised.
Cookies and browser storage
- Necessary cookies and local storage may support themes, request protection and mail sessions. Mail access data may be kept in browser-tab storage; clearing it can prevent further access to the inbox.
Analytics, infrastructure and third parties
- Own analytics and external integrations are treated separately. Mention of advertising or analytics does not imply they are currently active.
- Hosting and network providers may process technical information to deliver services. Independent email providers are outside Digutils control. Data may be disclosed when legally required; cross-border processing follows applicable law.
- Digutils does not sell temporary-message contents or provide public access to other people's mailboxes.
Safeguards and user rights
- Controls include restricted access, TLS, tokens, rate limits, isolation, retention and minimal logging, without guaranteeing absolute security.
- Where applicable law grants access, correction, deletion, restriction or other rights, users may contact the Operator. Verification may be necessary to protect other people's data; expired anonymous inboxes may no longer be linkable to an individual.
Changes and contacts
- Updates are dated and published online, with separate consent or notice when legally required. Contact channels and Operator legal details must be completed before public legal publication.