Privacy Policy

Effective date / last updated: August 21, 2026

1. Overview

MicroHub is an internal business application used by MicroDynamics employees, vendors, and customers (via the PressRoom customer portal) to manage equipment, sales, service, and production records. This policy describes what information MicroHub actually processes today and how it is used. It is not a certification of compliance with any specific law or regulation — see "Changes to this policy" below.

2. Information we process

MicroHub processes the following categories of information:

We do not lump this into a single vague "personal information" bucket internally — the categories above reflect how the underlying systems actually separate this data.

3. How we use information

We do not use this information for advertising or marketing, and MicroHub has no analytics, advertising, or marketing-tracking integrations today.

4. Business and equipment records

Sales, service, and production records are tied to a physical serial number or business relationship, not to an individual user account. These records are retained as ongoing business history even if the employee who created them, or the customer relationship, later changes — the same way a paper business record would be kept.

5. File uploads

Uploaded files (purchase orders, service attachments, software, configuration files, Feature Request attachments) are stored in access-controlled, private cloud storage. Files are not publicly browsable; access is granted only through short-lived, signed links generated by an authorized server request. One exception: product/package reference photography used in quotes and the product catalog is stored in a bucket that is intentionally public so it can render in generated documents — this bucket never contains customer names, serial numbers, or confidential business content.

MicroHub also automatically generates internal configuration backup archives ("Config Snapshots") on an approximately monthly schedule for administrators, containing only non-secret application configuration — never credentials, customer data, or uploaded files — stored in the same private, access-controlled storage described above.

6. Email and communications

MicroHub currently sends transactional email (invites, password resets, quotes, and diagnostics) through SMTP2GO, our current email delivery provider. We keep a delivery ledger (sent/delivered/bounced status and provider message IDs) to track whether messages were delivered and to avoid re-sending to addresses that have hard-bounced or complained. MicroDynamics previously used Resend for email delivery; that history is retained for record-keeping, but Resend is not used to send new mail today.

7. Authentication and security

Sign-in is protected by role-based access control, rate limiting, and IP-based lockouts after repeated failed attempts. We log IP address, user-agent, and success/failure of sign-in attempts to detect and respond to suspicious activity. See the Security page for more detail.

8. Service providers

MicroHub currently relies on the following service providers, by function:

We do not sell your information to third parties. We share information with the providers above only as needed for them to perform the function listed, and MicroHub does not otherwise disclose your information to unrelated third parties.

9. Data retention

Business and operational records (equipment, sales, service, production, licensing) are retained as ongoing business history for as long as they remain operationally useful; we do not currently apply an automatic deletion schedule to them. Email delivery history and security/audit logs are retained to support delivery troubleshooting and security review. See the dedicated Data Retention page for more detail.

10. Access and internal permissions

Access is role-based: customers see only their own account/project data through PressRoom; vendors see only their scoped vendor surface; internal employees see the areas their role covers; administrators have broader internal access needed to run the business. Roles are not redesigned by this policy — they reflect how MicroHub is actually built.

11. Data security

We use role-based authorization, private object storage with signed access links, rate limiting, and server-side handling of credentials and provider keys. No system is perfectly secure, and we make no absolute-security or formal-security-certification claim about MicroHub.

12. Your choices / requests

MicroHub does not currently offer a self-service data export or deletion tool. If you have a question about your information, or want to request account changes, contact support@microdynamics.net. An administrator can review and act on your request; some requests (e.g. deleting your sign-in account) do not remove historical business records that are kept for operational, accounting, or audit purposes.

13. Children's privacy

MicroHub is a business application intended for use by adult employees, vendors, and business customers of MicroDynamics. It is not directed to children, and we do not knowingly collect information from children.

14. Changes to this policy

We may update this policy as MicroHub's actual practices change. The effective date above reflects the most recent update. This policy describes MicroDynamics' current practices for MicroHub and PressRoom; it is not a certification of compliance with GDPR, CCPA, or any other specific law, and formal legal review is recommended before relying on it for broad external/commercial purposes.

15. Contact

Questions about this policy can be directed to support@microdynamics.net.