DevInside

Privacy at DevInside

How DevInside handles optional usage analytics, contact enquiries, investment pitch submissions and future email subscriptions.

Last updated: 14 November 2026. This notice describes the current DevInside website operated by Marcin Borecki. For questions about personal information, contact marcin@devinside.cloud. You can also reach Marcin through the public LinkedIn profile.

Reading this website

You can read the articles, guides and public labs without subscribing. The web server processes connection information to deliver pages and maintain the service. Operational access logs are separate from the optional usage analytics described below.

Optional usage analytics

If you choose “Allow analytics”, DevInside uses a self-hosted Umami installation on its Hetzner server to understand which pages and resources are useful. It records page views, selected link clicks, campaign labels, browser and device information, and approximate location derived from the connection. Umami derives pseudonymous session information from connection data; it does not need a name or email address.

The integration does not record session replays, form contents, email addresses, newsletter member identifiers or the text of messages. Page fragments and arbitrary query parameters are removed before sending an event; only restricted campaign labels are retained. Referring addresses are reduced to their origin.

The tracker is not loaded until you allow analytics. Your choice is saved in this browser's local storage. “No thanks” leaves optional analytics off. Browser Do Not Track and Global Privacy Control signals are respected. You can change the choice using or the link in the footer. Withdrawing consent stops further optional events on the page; it does not automatically erase previously aggregated measurements.

Email and enquiries

A contact link opens your own email application. DevInside does not collect the message through a web form. Messages you send to Marcin are handled to respond to your enquiry and, where appropriate, discuss or perform the work you request. Please do not include credentials or confidential production data in an initial enquiry.

Email subscriptions are not yet open while delivery is being connected. The intended newsletter is DevInside Field Notes, normally every two weeks. Before subscriptions open, this notice will identify the active email delivery provider and the signup flow will explain confirmation and unsubscribe options. The public field guide does not require an email address.

Investment pitch submissions

The form on the investing page collects your name, email, company details, the text you write, any links you share and up to three attached files. It is used only to evaluate a possible investment and to reply to you. You give consent with the checkbox in the form.

Submissions are stored on the DevInside server operated by Marcin Borecki on Hetzner infrastructure. They are not sent to third parties without your permission. Attachments are reachable only through private, expiring links available to Marcin. You can ask for your submission to be deleted at any time by writing to marcin@devinside.cloud.

The form uses no tracking. A hidden field and a timestamp help reject automated spam, and the server limits how often one connection can submit.

Service providers and access

The website and its analytics database are hosted on the owner's Hetzner infrastructure. The analytics dashboard is restricted to administrative access. The website does not send its optional analytics to an advertising network. External links, including LinkedIn, are governed by their destination's own notices when you follow them.

Your choices and requests

You can decline optional analytics, change your choice later, read public material without a subscription, and ask about information associated with an enquiry. Where applicable, you may request access, correction, deletion or restriction of personal information and object to its use. You may also contact the relevant data protection supervisory authority. Include enough context to locate the information without sending unnecessary sensitive data.