Privacy
Who operates DakNode
DakNode is not incorporated. It is an unincorporated software service operated by Subodh Kumar, trading as DakNode. The operator is based in Uttar Pradesh, India. Service infrastructure runs in AWS Asia Pacific (Mumbai), ap-south-1, which is a hosting location and not the operator's address.
What this website collects
This website does not use analytics, advertising or tracking of any kind. There are no cookies set by DakNode, no tag manager, and no third-party scripts. If you contact us, we receive whatever you put in your email.
What the DakNode service handles
DakNode is infrastructure that gives software agents an email address. When a customer uses the service, it stores and indexes the mail sent to and from the addresses that customer creates, so their software can retrieve it. That content belongs to the customer. It is processed to operate the service and is not sold, rented or used to train models.
The waitlist: what we collect
If you join the waitlist we store the email address you enter. If you fill them in, we also store your name, company, role, what you plan to use DakNode for, and roughly how many inboxes you expect to need — every one of those is optional and the form works without them. Alongside that we record the time you gave consent, a version label for the consent wording you were shown, and a fingerprint of that exact wording, so we can show later what you actually agreed to. The waitlist database, Redis rate-limit keys and application logs do not store your raw IP address or browser metadata. Separate infrastructure security logs record limited connection metadata, including IP address, as described below.
The waitlist: why we hold it
To record that you are interested in DakNode, to run early access, and — only because you ticked the box saying so — to send you product updates and early-access email in future. Joining the waitlist sends you no email today: this feature has no confirmation message and none is on its way. Waitlist information is not sold, rented or shared for anyone else's marketing.
The waitlist: how long we keep it
Waitlist entries are hard-deleted from the active waitlist database twelve months after they are created, or earlier after we verify a withdrawal request. This removes the active row rather than marking it deleted or copying it into an application archive. To withdraw, email privacy@daknode.com; there is no self-service delete button on this site, and we would rather say so than imply one exists. This twelve-month period describes waitlist entries specifically. It is not a retention period for customer mail handled by the DakNode service, which is a separate question we have not fixed an answer to.
The live inbox demo: what it processes
The homepage shows a live inbox demo. When the panel is on screen it asks our API for a temporary email address, which is created for you and shown to you. If anyone sends mail to that address, we temporarily process the demo address itself, the times it was created and mail arrived at it, the sender's email address, the subject line, and the message body converted to plain text. Attachments are not stored and are not exposed anywhere — the panel has no attachment control and the API returns none. The demo does not use a cookie.
The live inbox demo: who can send to it
Anyone who knows a temporary demo address can send mail to it, and whoever does so chose to. The address is shown in the panel and is meant to be used, so treat anything you send to it as something that will be displayed in a browser. Do not send anything confidential, and do not send anyone else's personal information. The demo is receive-only: it never replies, never forwards, and sends no email of any kind.
The live inbox demo: how long it lasts
Retrieval access ends fifteen minutes after the server created the inbox. That deadline is set once by the server and nothing extends it — not refreshing the page, not reopening the panel, not a clock difference on your device. After it passes the messages are unreachable, whatever still exists on disk. The active database rows are then removed by the next hourly sweep, so a row survives at most about an hour past expiry while already being unreachable. The raw message file is deleted as soon as processing finishes, whatever the outcome, and a one-day storage lifecycle rule is the asynchronous backstop for anything a crash leaves behind.
The live inbox demo: what we are not claiming
The periods above describe when data becomes eligible for deletion, not a guarantee that a byte has physically gone at an exact second. Object storage deletion is asynchronous and the sweep runs on a schedule, so we describe the mechanism rather than quote a deadline we cannot enforce. What we do guarantee is revocation: retrieval is refused from the fifteen-minute expiry onward. Demo mail is kept separate from customer inboxes — it is stored in its own tables with no customer or organisation identifier on them, and it is never indexed into, searchable from, or delivered to any customer's mailbox.
Security logging by our infrastructure
The AWS load balancer in front of our API records limited connection metadata about requests, including the IP address they came from. This exists for security and to keep the service running, and it predates the waitlist. These logs are bounded rather than kept forever: a current log version becomes eligible for lifecycle deletion after 90 days, and the superseded version after one further day. Because Amazon S3 carries out that deletion asynchronously, roughly 91 days is when a log becomes eligible to be removed, not a guaranteed deadline by which it has physically gone. We would rather describe the mechanism accurately than quote a number we cannot enforce.
What we deliberately do not claim
We are not making a certification claim. DakNode holds no SOC 2, ISO 27001 or equivalent audit, and this page does not assert compliance with any specific regulatory framework. Nothing here has been reviewed by a lawyer, and none of it is a guarantee.
Contacting us about your data
Privacy questions, access requests and deletion requests go to privacy@daknode.com.
Draft prepared August 2026