Armogentic.

Armogentic · Beta

Privacy Policy

This policy describes information Armogentic may process to provide static analysis, connected n8n monitoring, billing, and support.

Effective date: pending owner/legal confirmationLast updated: September 23, 2026

1. Data collected

  • Account and authentication: account identifier, email/profile information, authentication state, and account status.
  • Static scans: uploaded source/configuration while it is analyzed, plus reports, findings, evidence, and sanitized metadata needed to return results.
  • n8n connections: instance URL, display name, connection status, verification timestamps, API credential, and credential fingerprint. The server-side code encrypts stored n8n API credentials with an application-managed key.
  • Connected monitoring: workflow names and identifiers, node types/names, connections, hashes/fingerprints, findings, sanitized baselines, monitoring status, check outcomes, drift summaries, and history.
  • Billing: Paddle customer, subscription, price, status, cancellation, and billing-event identifiers. Paddle handles payment-card details separately.
  • Operations and support: diagnostic/security events, abuse-prevention information, operational records, and communications sent to support, where collected.

2. How data is used

We use information to provide static analysis and reports; enforce paid subscription entitlements; authenticate and manage accounts; administer billing; provide n8n monitoring; prevent abuse and fraud; troubleshoot and secure the service; respond to support; and meet legal obligations.

3. Uploaded-source handling

Static uploads are processed locally in the browser in the current homepage flow. Uploaded n8n JSON exports are inspected without executing their nodes, code, expressions, or credentials. Subscriber AI Red Team and AutoFix actions send the selected n8n workflow and purpose to the server for deterministic static analysis. This endpoint does not persist the submitted source or execute its nodes, code, expressions, or credentials. AutoFix generates a separate candidate; the original remains unchanged, and a modified download requires review and approval. Connected n8n monitoring is different: the server retrieves workflow data from the configured n8n instance to perform a requested check.

Persisted n8n baselines remove raw node parameters and store sanitized structure, fingerprints, findings, and metadata. The repository does not establish a complete raw-file retention schedule or every possible processing path, so do not submit information you are not authorized to share.

4. Service providers

Repository and configuration evidence confirms Supabase components for authentication/database access and Paddle for billing. Paddle processes payment information under its own terms and privacy practices. A complete production subprocessor inventory and hosting arrangement require owner confirmation before this list is treated as exhaustive.

5. Retention and deletion

Information may be retained as needed to provide the service, maintain account and billing records, support security and operations, resolve disputes, and meet legal obligations. Exact retention periods, raw-file behavior, backup deletion, and production deletion workflows are not verified here. Account-associated deletion requests can be sent to support; billing, security, audit, backup, or legal records may need to remain.

6. Rights and controls

Where available, you can manage account information and connected n8n credentials in the service. You may ask for access, correction, deletion, or account closure by contacting support. Depending on location, additional rights may apply, including consent withdrawal where consent is the applicable basis. We will review requests under applicable law. International processing, children’s privacy age thresholds, and a jurisdiction-specific grievance route require owner/legal confirmation.

7. Security

Safeguards include server-side access controls and encryption of stored n8n API credentials. No storage or transmission method is completely secure, and Armogentic does not claim absolute or end-to-end security. Never send secrets or full payment-card details to support.

8. Policy updates

We may update this policy as the service changes. The current version will be posted here with an updated date; material changes may also be communicated through the service or by email where reasonably practical.

9. Contact

For privacy questions, requests, or concerns, email support@armogentic.com.