How CaptureContext handles your information

Draft revised: September 6, 2026

Before publication: confirm the deployed Railway log-retention settings and Resend open/click tracking configuration. Resolve the external Google Fonts loading described below, either by hosting the font files with the website or establishing the appropriate legal basis and any required consent. Set the effective date when this policy takes effect and remove this draft note.

This policy covers visits to capturecontext.dev, newsletter subscriptions, and correspondence with CaptureContext. Individual apps have their own policies. Information about the Myo app is covered by the Myo Privacy Policy.

1. Who is responsible

Maksim Kruk, a sole trader established in Poland, operates this website and is the controller of personal data processed for its operation, newsletter, and correspondence. CaptureContext is the umbrella brand for his independent developer work, not a separate company or legal entity.

For privacy questions or requests, contact support@contact.capturecontext.dev.

2. Visiting the website

The website and newsletter subscription service use Railway hosting. When you visit or submit a request, the hosting infrastructure receives technical information needed to serve it. This can include your IP address, requested URL, time of the request, browser information, referring page when supplied by your browser, and response or error information. We use operational information to deliver the website, investigate failures, and protect the service from abuse.

The website uses browser storage to remember your light, dark, or system theme preference. This preference is used for appearance, rather than advertising or measuring your activity across websites. You can remove it by clearing this website's stored data in your browser.

The website currently requests the Inter typeface from Google Fonts. Your browser connects to Google's font servers and sends network information, including your IP address and browser request headers, to receive those files. This request can occur without subscribing or sending a message. Google's handling of its services is explained in its privacy policy.

3. Newsletter subscriptions

When you subscribe, we process:

• the email address you submit;
• your subscription status and newsletter-list membership;
• message-delivery information, such as delivery status, bounces, and spam complaints; and
• technical information used to protect the subscription service from abuse.

The subscription form sends your email address to our newsletter endpoint, which passes it to Resend. Resend stores the contact record and manages newsletter delivery. We do not maintain a separate newsletter contact database in the subscription service.

To limit repeated requests, the service temporarily stores hashes derived from the submitted email address and connecting IP address, together with request counters. Hashing does not make these records anonymous. These counters are used for abuse prevention, not marketing profiles.

Subscribing is optional. The form explains that submitting your address signs you up for CaptureContext product updates and news about new work. If you do not subscribe, you can still browse the website.

4. Email engagement measurement

Resend supports per-recipient email-open and link-click measurement. Open measurement uses an image request, and click measurement routes links through a tracking address. These features are separate from delivery and bounce information.

Configuration to confirm: replace this paragraph with the actual sending-domain configuration before publication. If open and click tracking are disabled, state that directly. If enabled, disclose the resulting recipient-linked activity, its purpose and retention, and establish the required consent before sending tracked messages. Newsletter subscription consent should not be treated as automatic consent to every form of engagement tracking.

5. Contacting us

The website contact form prepares an email draft in your own mail app. Its fields include a category, subject, name, email address, and message. The form does not submit those contents to a website contact-form backend. We receive them when you choose to send the email.

We use Resend to handle correspondence sent to our contact addresses. We process the sender's address, message, attachments, and other details included in the email to respond to enquiries, discuss potential work, provide support, and resolve issues. Your own email provider also processes the message under its own terms.

You choose what to send. We may need a reply address and enough context to respond meaningfully. Contacting us does not subscribe you to the newsletter.

6. Purposes and legal bases

The Google Fonts integration and any optional email engagement measurement require the separate assessment identified in the draft notes above. This policy does not treat merely visiting the website as consent to optional tracking.

Where we rely on consent, you may withdraw it at any time. Withdrawal does not affect processing that was lawful before it. Where we rely on legitimate interests, you may object as explained below.

7. Providers and international processing

We use Railway for hosting and Resend, operated by Plus Five Five, Inc., for newsletter contacts, email delivery, and correspondence. They process information on our behalf under applicable data-processing arrangements. Providers may separately process limited information for their own legal, security, or business responsibilities.

Resend stores customer data in the United States. Choosing a European sending region does not move its stored data to Europe. Its data-processing addendum incorporates Standard Contractual Clauses for relevant transfers, and its GDPR information describes the applicable safeguards. Its infrastructure providers are listed on its subprocessors page.

Railway and its providers may process information outside the European Economic Area. Its data-processing addendum and privacy policy explain its processing and transfer arrangements. The font requests described in section 2 also involve Google directly.

We remain responsible for processing carried out on our behalf. Contact us for information about the safeguards applicable to your data, including how to obtain a copy. External websites you choose to visit through links on this site operate under their own policies.

8. Retention

• Newsletter contacts: kept while you remain subscribed. After withdrawal, a limited unsubscribed or suppression record may remain to prevent further mailings. It is used to respect your choice, not to continue marketing. Contact us to request deletion; we will explain any information that must remain for compliance or suppression.
• Emails and delivery logs: Resend states that standard-plan email and log data are retained for 30 days while the account is active. Correspondence is available to us through that service for 30 days. Contact-list records have a separate purpose and are not automatically removed under the email-log window.
• Resend backups: Resend states that backups persist for seven days. Its DPA separately provides for deletion of remaining customer data within 90 days after account termination, subject to its stated exceptions. These are different retention rules, not a promise that every record disappears on the same date. See Resend's retention information.
• Abuse-prevention counters: held in server memory. The default counting window is 15 minutes. Expired entries are removed during subsequent cleanup or when the process ends, so the window is not a guaranteed deletion deadline for every entry. These counters are not stored in a separate persistent database.
• Website and service logs: retained through the hosting provider for operations and security. Railway's log documentation describes plan-dependent availability. The deployed plan and any additional retention must be confirmed before an exact period can be stated.
• Theme preference: remains in your browser until you change it, clear the stored site data, or your browser removes it.

Where a specific legal obligation or dispute requires limited information to be retained longer, that information is limited to what is necessary for that purpose.

9. Unsubscribing and your rights

You can unsubscribe using the link in a newsletter message or by contacting support@contact.capturecontext.dev. Unsubscribing stops newsletter delivery; it is different from requesting deletion of all related records.

Depending on the processing and applicable law, you may request access, correction, deletion, restriction, or a portable copy of your personal data. You may object to processing based on legitimate interests and may object to direct marketing at any time. You may withdraw consent where consent is the legal basis.

Send requests to the contact address above. We may need limited information to verify that a request relates to your address or records. We normally respond within one month and will explain any permitted extension within that first month.

You can complain to the President of Poland's Personal Data Protection Office, UODO, or another competent data-protection authority.

10. Sale, automated decisions, and changes

We do not sell your personal data. We do not use the website or newsletter data to make solely automated decisions that produce legal or similarly significant effects on you.

We will update this policy when our practices change. Material changes will be communicated appropriately before new processing begins, and we will obtain additional consent where required. A policy update alone does not authorize a new use of your data.