Who is responsible
Ekanatha Reddy Urivakili, based in Milton Keynes, United Kingdom, operates ekanatha.io and is responsible for personal information handled for this publication. Contact ekanatha.dev@gmail.com with privacy questions or requests.
Reading the site
You do not need a reader account to browse articles. Serving a page involves technical information such as your IP address, requested URL, browser information and request time. Hosting and infrastructure providers may process these details in operational and security logs.
With your consent, the site adds to aggregate article view totals. A marker in your browser’s session storage avoids sending the same article view repeatedly within a tab session. The article counter itself does not store a reader profile or a unique cross-site advertising identifier.
With your consent, theme preferences and offline page copies are stored on your device. The Cookies & storage policy describes these features, and Cookie settings lets you change your choice at any time.
The weekly newsletter
If you subscribe, the site stores your email address, where on the site you subscribed, and when you subscribed, confirmed and (if you do) unsubscribed. Nobody is added until they click the confirmation link sent to that address. Your address is used only to send the Saturday digest of new articles; it is not sold, shared for others’ marketing or combined with other data.
Every digest includes a one-click unsubscribe link, and supporting mail apps show their own unsubscribe button. Once you unsubscribe, no further digests are sent; the record that you unsubscribed is kept so the address is not emailed by mistake. Unconfirmed sign-ups receive no further email. Ask the author to delete your record entirely at any time.
If you contact the author
Emailing the author shares your email address, message and any information or attachments you choose to send. That information is used to reply, investigate corrections, address privacy requests and keep a relevant record of the conversation. Please avoid sending passwords, access tokens or other confidential information.
Studio administration
The restricted studio uses Google sign-in and optional additional authentication factors. For authorised administrators, the site handles account identifiers, email, role, sign-in times and security settings. Sign-in alerts can include IP address and browser information. Authenticator secrets are encrypted; recovery codes are stored as hashes; passkey records contain public-key credentials rather than your fingerprint or face data.
These features are for site administration, not a public reader registration service.
Purposes and legal grounds
Technical and security information is used to operate, protect and maintain the publication. Contact correspondence is used to handle the enquiry or request. The newsletter, optional cookies and similar storage rely on your consent, which you can withdraw at any time. These activities rely on legitimate interests in running a secure publication and communicating with people who contact it, except where a different legal ground is required. Any processing that requires consent must use that consent as its basis; you can withdraw it for future processing.
Service providers and external content
Railway provides hosting and database infrastructure. Google provides administrator sign-in and the email service used by the published contact address. Resend delivers newsletter, confirmation and operational notification emails, and OpenAI processes editor prompts and article-generation inputs. Reading a public article does not, by itself, send its reader’s message to an AI model.
Articles may contain externally hosted images or embedded videos. Loading those resources can share technical request information with their providers. Following a social link or sending an email also brings the relevant provider’s privacy practices into play.
Providers may process information outside the United Kingdom. Locations, retention and transfer arrangements depend on the provider and the service configuration. Contact the author for information about a particular processing activity. Personal information is not sold by this publication.
How long information is kept
Contact messages are kept for as long as needed to deal with the enquiry, follow-up and any relevant dispute or legal obligation. Administrator records are kept while access is needed and, where necessary, for security investigations. Infrastructure logs follow the hosting provider’s configured retention. These criteria depend on the purpose rather than one universal retention period; contact the author about a specific record.
Browser session markers normally end with the tab session. Preferences and offline caches can remain until you clear site data, the browser removes them or cached entries are replaced. Cookies have the durations listed in the storage policy.
Your choices and rights
Depending on the circumstances, you can request access, correction, deletion or restriction of personal information, object to processing, or request a portable copy where the relevant conditions apply. These rights have limits and depend on the processing involved. Email the author with enough information to identify the request; proportionate identity checks may be needed before disclosing personal information.
You can also raise a concern with the UK Information Commissioner’s Office. The ICO’s information on data protection rights explains the different rights and when they apply.
Updates
This notice will be updated when the site’s processing changes. The date above identifies the current version.