Security & Data Handling

1. Who you are dealing with

Our products are published by NetDevGuru Infotech, registered at Behind BDA Complex, 3rd Block, Koramangala, Bengaluru - 560034. Security, privacy and support enquiries reach us at netdevguru@gmail.com, and we aim to respond within 30 days.

2. Where the software runs

On your infrastructure, not ours. You receive the full source and deploy it to a server, container platform or cloud account that you control. Your database is yours. NetDevGuru Infotech operates no hosted instance of the product, has no account on your systems, and holds no copy of your data.

This is the substantive difference from a SaaS vendor. With a hosted email platform, your subscriber list sits in the vendor’s database under their retention and subpoena exposure. Here it sits in yours.

3. The software does not call home

There is no licence check, no usage beacon, no remote logging and no analytics callback to NetDevGuru Infotech anywhere in the product. Once installed, it makes no outbound request to us at all.

You do not have to take that on trust: you receive the complete source code, so this is a claim you can verify by inspection before you deploy anything.

4. Who is the controller, and who is the processor

Under the GDPR and equivalent regimes, you are the data controller for the personal data in your installation. Because the software transmits nothing to us, NetDevGuru Infotech is not a data processor for your contacts, campaigns or analytics.

Your processors are the infrastructure providers you choose - typically your hosting provider and, if you send through Amazon SES, AWS. Both publish standard data processing agreements, and those are the agreements that actually govern your subscriber data. A processing agreement with us would not cover data we never receive.

5. The exception: support access

There is one circumstance in which we could become a processor, and we would rather state it than have you discover it. A licence includes a period of support. If resolving an issue ever requires us to access your instance, read your logs, or receive a database extract, then for that engagement we are processing your data on your instructions.

A scoped confidentiality and data processing addendum covering support access is available on request, and we are happy to sign yours instead. We do not require any standing access to your systems, and we do not ask for credentials as a condition of support.

6. How email leaves an AutomateFlow installation

AutomateFlow is not a mail server. It does not deliver mail itself and contains no MTA. Every message is relayed through a provider you configure and control: either your own Amazon SES account or a standard SMTP provider. Bulk sending accepts exactly those two transports and nothing else.

Your domain reputation therefore rests on the provider you chose plus your own SPF, DKIM and DMARC records - the same arrangement as with a hosted email platform. Self-hosting here means the application runs on your infrastructure; it does not mean mail originates from it.

One difference between the two transports is worth knowing before you choose. The bounce and complaint feedback loop arrives over Amazon SES’s event notifications. On a plain SMTP relay that feedback is not available, so suppression of hard bounces and complaints becomes a manual task. For meaningful sending volume we recommend SES.

7. Deliverability and list-hygiene controls

Sender reputation is a shared concern, so these are built in rather than left to the operator:

• Hard bounces and complaints are captured from the provider and added to a suppression list, so a bad address is not mailed twice.
• Every campaign carries RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers - the one-click requirement Gmail and Yahoo enforce on bulk senders.
• Sending is rate limited per workspace, and a campaign that hits a limit pauses and resumes rather than retrying against the provider.
• Contact engagement is scored and unengaged addresses are retired on a schedule, which is the single most effective protection against a decaying list.
• Every message carries a plain-text part alongside the HTML, because HTML-only mail is a long-standing spam signal.
• Automated opens from security scanners and link prefetchers are classified out of engagement metrics, so reporting is not inflated by machinery.

8. Separating marketing from transactional mail

We recommend it, and it is sound practice regardless of which vendor you use. Marketing and transactional mail should be sent from separate subdomains so that campaign performance cannot affect delivery of password resets and receipts. AutomateFlow can send transactional mail, but nothing requires you to route it there, and keeping the two apart at the outset is the more conservative choice.

9. Reporting a vulnerability

If you believe you have found a security issue in one of our products, email netdevguru@gmail.com with enough detail to reproduce it. Please give us a reasonable opportunity to issue a fix before disclosing publicly. We will confirm receipt and keep you updated on the remedy.