Privacy Policy

Last updated: September 30, 2026

Entrpy, LLC (“Entrpy”, “we”) builds bespoke software for individual clients under signed consulting engagements. Our software is private, single-tenant, and operates exclusively on behalf of the contracting client. This policy explains what data our software accesses, how we store it, and how to revoke access.

1. Scope

This policy covers software developed by Entrpy that integrates with third-party services on a client’s behalf. It does not cover how those third-party services themselves handle data. Refer to the relevant provider’s policy for that.

Amazon Selling Partner API. GoBags Dashboard, our Amazon Selling Partner API application, is governed by its own policy: GoBags Dashboard Privacy Policy. That policy controls for any data read from a seller’s Amazon account.

Financial account data (Plaid).Where a client authorizes it, our software connects to the client’s business bank account through Plaid to retrieve account balances and transaction history on a read-onlybasis, for the client’s financial-operations reporting. The account holder connects their own account through Plaid’s hosted flow (Plaid Link) with explicit consent; we never receive or store banking login credentials, and we initiate no payments or transfers.

2. What our software accesses

Our software accesses only the data needed to perform the workflows the client has authorized. For our QuickBooks Online integration, this means data within the scope com.intuit.quickbooks.accounting: customers, vendors, items, estimates, invoices, purchase orders, and related entities. We do not request payments, payroll, or user-identity scopes.

All write operations are read-or-create-or-update. Our software never deletes records in a client’s source systems.

For our financial-account integration, we retrieve only account balances and transaction history via Plaid. This Plaid-derived data is retained only as long as needed to provide reporting and is deleted per our retention and disposal terms in Section 3.

3. Storage and security

OAuth refresh tokens and other credentials are stored either on hardware owned by the client (e.g., a dedicated server on the client’s network) or on a server operated by Entrpy in the United States, with file-system permissions restricted to the account that runs the software. Credentials are never committed to source control, never shared with third parties, and never transmitted anywhere except to the third-party service that issued them.

Operational state (in-flight workflow records) is stored on the same infrastructure as the software, or in a database operated by Entrpy for that client. We retain only what is needed to drive the workflow; no analytics or telemetry is collected on end users.

Financial-account data retrieved via Plaid, and the Plaid access tokens used to retrieve it, are encrypted at rest. They are retained only while the connection is active and are deleted within 30 days of disconnection, account termination, or a deletion request, at which point the associated Plaid access token is revoked.

4. Sharing

We do not sell, rent, or share data accessed by our software with any third party, except to the third-party services the client has authorized us to integrate with (e.g., posting an estimate back to QuickBooks Online).

5. Revoking access

You may revoke our software’s access at any time:

On revocation, our software loses the ability to read or write to that service. Any cached credentials on disk are invalidated by the provider and become unusable.

6. Data subject requests

To request information about or deletion of data our software has accessed on your behalf, contact us at the address below. Where the data lives in a third-party system (e.g., your own QuickBooks company), the source-of-truth records remain in that system and are subject to that provider’s policies.

7. Changes

We may update this policy as our software evolves. The “Last updated” date above reflects the most recent change.

8. Contact

Questions or requests: hello@entrpy.co.