EnerLinks Solutions

EnerLinks Solutions Privacy Policy

Version: 2026-11-03 Effective: 2026-11-03T17:00:00Z Last revised: 2026-11-03

This Privacy Policy explains how EnerLinks Solutions, LLC (`EnerLinks`, `we`, `us`, or `our`) collects, uses, discloses, and retains personal information through the EnerLinks website, accounts, purchases, support, email, and EnerViz license services.

1. Scope and roles

This Policy applies when EnerLinks determines why and how personal information is processed for these services. It does not govern an external service you use independently or project/model data that remains only on your device.

EnerViz project files, component libraries, settings, autosaves, local paths, calculations, and exports remain local under the audited product behavior unless you choose to send them to us, such as in a support request. EnerViz still communicates for required licensing, validation, and related security functions as described below.

2. Information we collect

Information you provide

  • - Account information: your email address and your password, which is handled by Supabase, our authentication provider, and is never stored in readable form. We do not ask for your name when you sign up; a name can reach us only through optional seat assignment, the billing details Stripe sends us, or your correspondence, as described below.
  • - Purchase information, such as selected product, seat quantity, billing cadence, billing contact, transaction status, and Stripe customer, checkout, subscription, invoice, or payment identifiers. Card details are collected and processed by Stripe; your full card details never reach our servers. When you start a checkout, we store the identifier Stripe assigns to you as a customer with your account; this happens before payment, so it may be stored even if you do not complete the purchase. When your payment is confirmed, Stripe sends our systems the billing details you entered at checkout (such as your name and billing contact information) together with payment records (the amount, payment status and Stripe's payment identifiers); of these, we store the payment records with your order.
  • - Support and correspondence, including messages, attachments, diagnostic information you choose to send, and records of our response.
  • - Named-user seat information supplied by a purchaser or organization, including the assignee email, optional display name, assignment time, and assignment/reassignment audit records such as the actor, previous/new assignee and reason. The purchaser must have authority to provide that information. The signed license file does not itself contain the assignee name or email. Each seat is one named user, who may activate EnerViz on up to two devices.
  • - Requests concerning access, correction, deletion, account closure, refunds, licensing, or privacy.

Information collected through operation

  • - Account, order, entitlement, license, activation, expiry, validation, refund, cancellation, dispute, invoice-reconciliation, complimentary-grant, download/release, and transaction-event records.
  • - Agreement-acceptance records, including the accepted document version, effective date and hash, acceptance time, exact acceptance wording, and relevant account, order or download context where collected. Desktop acceptance is stored locally; it is not automatically uploaded merely because you accept.
  • - An application-scoped, one-way device identifier derived from a stable operating-system identifier, activation timestamps, and related device-seat status. We keep it with the license's activation records for as long as the license exists, to enforce the per-seat device limit.
  • - A source-network hash used for license-validation rate limiting and abuse prevention. The audited implementation mechanically limits this rate-limit ledger to approximately 30 days. We do not use the device identifier or the network hash for marketing. Licenses issued for offline use do not send validation requests.
  • - Website and infrastructure information such as IP address, request time, browser/device attributes, requested page, security events, error and operational logs, and functional cookie/local-storage state.
  • - Transactional email delivery information such as recipient address, message type, delivery identifier, status, and timing.

We did not observe optional desktop analytics, advertising trackers, or crash-upload telemetry in the audited release path. We will update this Policy and implement any required choice before introducing optional collection.

3. How we use information

We use personal information to:

  • - create, secure, authenticate, and administer accounts;
  • - process orders, payments, subscriptions, taxes, receipts, cancellations, refunds, disputes, and reconciliation;
  • - issue, activate, validate, enforce, reset, and support software licenses and device seats;
  • - deliver software and transactional messages;
  • - provide support, diagnose defects, and respond to requests;
  • - prevent fraud, abuse, unauthorized access, license circumvention, and security incidents;
  • - maintain, measure the reliability of, and improve the services using operational information;
  • - comply with law, enforce agreements, establish or defend legal claims, and maintain required business records; and
  • - communicate material service, security, policy, renewal, cancellation, or account information.

We do not use project/model data that remains on your device. If you voluntarily submit a project or diagnostic artifact to support, we use it only to handle the request, maintain security, and meet applicable record obligations unless we obtain separate permission for another use.

4. How we disclose information

We disclose information as needed to providers that perform services for us, including:

  • - Supabase for authentication and application database services;
  • - Stripe for checkout, payment, subscriptions, billing portal, refunds, disputes, and related fraud controls;
  • - Resend for transactional email delivery;
  • - Microsoft 365 and Google/Gmail for the business/support mailboxes and correspondence we operate;
  • - Vercel for website/application hosting and operations; and
  • - Cloudflare for domain, network, delivery, and security services.

These providers process information under their own applicable service terms and privacy commitments. We may also disclose information to professional advisers, auditors, insurers, authorities, or counterparties when reasonably necessary for legal compliance, security, a claim, or a corporate transaction. If ownership of the relevant business changes, the successor must handle personal information consistently with applicable law and the promises made at transfer.

We do not sell personal information or share it for cross-context behavioral advertising, and we do not use it for targeted advertising under the audited behavior.

5. Cookies and similar technologies

The Website uses essential authentication/security technologies and a functional theme preference. Supabase authentication may use cookies or related browser storage to maintain a signed-in or account-recovery session; the audited vendored maximum can be up to approximately 400 days, subject to the hosted session configuration and earlier expiration or sign-out. The theme preference may last up to one year. Cloudflare and Vercel may process request and security data needed to deliver and protect the service.

We did not observe advertising or optional analytics cookies in the audited source. The Cookies Policy provides more detail. If optional cookies or similar tracking are introduced, we will update the notices and provide any choice required before using them.

6. Retention

We keep personal information only as long as reasonably needed for the purpose collected, including to provide an active account or subscription, maintain license and assent evidence, complete transactions, meet accounting/tax and legal obligations, prevent abuse, resolve disputes, and enforce agreements.

Examples:

  • - the hashed source-network rate-limit ledger is mechanically limited to approximately 30 days under the audited implementation;
  • - account, order, payment-reference, license, activation, cancellation, refund, dispute, invoice, and assent records may be kept for the account/service relationship and a reasonable legal, tax, audit, and dispute period afterward;
  • - support records are retained long enough to resolve the matter, identify recurring defects or abuse, and meet legal needs;
  • - email-delivery and infrastructure records are kept according to operational, security, provider, and legal requirements; and
  • - backups may retain information for a limited rotation period before deletion propagates.

We will publish more specific retention periods when operations have verified that the application, providers, backups, and legal holds can honor them consistently. We do not promise immediate deletion where a record is needed for security, payment, license/assent evidence, legal compliance, or an active dispute.

7. Security

We use reasonable administrative, technical, and organizational safeguards designed for the nature of the information, including managed authentication, access controls, signed license artifacts, one-way identifiers for device/network functions, and payment handling by Stripe. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

If we determine that a security incident affects personal information, we will investigate and provide notice as required by applicable law.

8. Your choices and requests

You may update certain account information through available account controls. You may ask to access, correct, delete, or obtain information about personal information we hold, or request account closure, by contacting us. We may verify your identity and authority before acting. We may deny or limit a request where the information is not subject to the request, cannot be linked reasonably, or must be retained for security, transaction, legal, or claims purposes; we will explain when applicable.

You may cancel a subscription through the authenticated billing page and hosted billing portal. Cancellation and data deletion are separate actions. Essential service and legal messages are not marketing and may continue while needed for the account, transaction, license, or security. We will honor applicable marketing opt-out rights before sending marketing email.

9. Children

The services are intended for adults and are not directed to children under 13. Account creation and purchases require a user who is at least 18. If we learn that we collected a child's personal information contrary to this section, we will take appropriate steps to delete it.

10. United States processing and regional rights

EnerLinks is based in Florida, United States, and the providers listed above may process information in the United States and other locations where they operate. Laws in those places may differ from those where you live.

Residents of some jurisdictions may have additional non-waivable rights. We will honor applicable rights and appeals even if they are not listed exhaustively here. Contact us with the request and your jurisdiction; do not email sensitive identity documents unless we first provide an appropriate method.

11. Changes

We may update this Policy to reflect product, provider, legal, or operational changes. The published copy will identify the effective and revision dates. We will provide additional notice when required or when a change materially affects how we use information already collected.

12. Contact

EnerLinks Solutions, LLC 7754 Okeechobee Blvd PMB 2003 West Palm Beach, FL 33411, United States Email: [email protected]