Privacy notice

Who is responsible

CODE ALPHA d.o.o., Ulica Dragutina Domjanića 28, 10000 Zagreb, operates SendProofs and is responsible for account, website and support processing described here. Contact vmarcetic@bytecode.hr for privacy questions or a request about your data. Do not attach the original campaign email or credentials.

You choose which test email to upload. Use only material you are entitled to process, minimize personal data and do not submit another person's confidential correspondence. Contact us before a use that requires separately agreed processing terms.

Information and purposes

• Accounts: name, email, password credentials in hashed form, workspace membership and account activity are used to provide and secure your workspace, manage access and respond to account requests.
• Uploaded tests: the service parses your .eml to extract subject, sender, message id, timestamps, short link labels, HTTP links and remote image URLs. Reports record redacted display URLs, check states, status codes, durations, warnings and timestamps. This processing provides the check you request.
• Support: your contact details and message are used to answer your request. Include only the information needed to explain the issue.
• Operations: web requests can generate server and application logs containing IP addresses, request paths, times, status codes and error details. They support availability, troubleshooting and abuse prevention.

For account provision, checks you request and related support, the legal basis is performance of our service agreement (GDPR Article 6(1)(b)). Website operation, security and abuse prevention rely on our legitimate interests in providing and protecting the service (Article 6(1)(f)). Where we must preserve information to meet a legal obligation, Article 6(1)(c) applies. Consent choices for Google's public-page integration are described below. SendProofs does not use campaign check results to make decisions with legal or similarly significant effects about individuals.

Raw email body, attachments and URLs

Raw email body content and attachment bytes are parsed transiently and are not stored in SendProofs domain tables. The upload exists in process memory and temporary request handling while it is processed. This describes application persistence, not a claim that a device or every infrastructure layer holds no temporary copy.

Original resource URLs and final URLs are encrypted at the application level. Visible URLs and redirect evidence redact non-UTM query values and recognized sensitive path segments. Pattern-based redaction cannot identify every secret: URL paths, link labels, subjects and even UTM values may contain personal information. Avoid including it in your test.

Eligible public destinations receive bounded HTTP requests with the SendProofs user agent. The destination receives the requested URL and our server's network request; an identifier embedded in a URL may therefore reach that destination. Recognized action links are not requested. See data handling and the security model.

Infrastructure and recipients

The application, PostgreSQL database, Redis queue and local file storage run on Hetzner Cloud infrastructure in Helsinki, Finland. Authorized operator personnel and infrastructure providers may process information as needed to operate, secure or support the service. Support correspondence passes through email transport and receiving mail providers. Sentry error monitoring is not currently enabled.

Website and workspace pages use Google's remotely hosted fonts and the conditional consent integration described below. These browser connections are separate from campaign checking. Google may process website connection information outside the European Economic Area under its applicable terms and transfer arrangements; see Google's privacy policy. We do not claim that all website-related information stays in Finland.

Retention and removal requests

Account and report data are kept for the workspace's operation and access to earlier evidence. Reports have no scheduled automatic expiry, and inactive workspaces do not expire automatically. Configured report periods do not currently trigger deletion. Request manual removal of a report or account by emailing support from your account address and identifying the workspace or report; we may need to verify your authority.

Removal requests are reviewed for the data concerned and any continuing legal or security need. Support correspondence and operational records may need separate review from the live report. We do not promise immediate erasure from backups or quote a fixed backup purge period. A response to a removal request will explain its scope and any applicable retention exception.

Public website and advertising

Website and workspace pages load fonts from Google's servers. Google ads and remarketing are not enabled.

On selected public pages, Google’s consent platform is loaded using the AdSense publisher script with ad requests paused. Loading it connects your browser to Google, which can receive your IP address, the public page address and browser information, and may read existing Google cookies. It does not receive uploaded emails, campaign reports or workspace information from SendProofs.

When Google’s consent window is available on the signed-out homepage, you can review its purposes and providers, accept, reject or change your choices. On signed-out policy pages, the “Privacy settings” link in the footer opens that page. If you are signed in, sign out first. A choice does not enable ads in this version. If the window is unavailable, ad requests remain paused.

See how Google uses information from sites and apps that use its services. Signed-in pages, account actions, uploads and reports do not load this publisher integration.

This notice and the terms, security and data-handling pages do not load the AdSense publisher script or Google’s consent window.

Essential session and security cookies support sign-in and request protection. You can browse the public guides without an account. Providing account details and a supported test file is necessary to use the workspace and run a check.

Your rights

Depending on the processing and applicable conditions, you can request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests. Where consent is used, you can withdraw it without affecting the lawfulness of earlier processing.

Send a request to vmarcetic@bytecode.hr. We respond without undue delay, normally within one month. If a lawful extension is needed because of complexity or the number of requests, we will explain it within that month. You can complain to AZOP, the Croatian data protection authority, or the supervisory authority competent for you.