Information security policy
Last updated November 2, 2026
This page summarizes how Gridwork Solutions LLC protects data in Gridwork Money, including data received from Plaid.
Governance
The operator, Brad Baker, is responsible for security. This policy is reviewed at least once a year and whenever the service changes in a way that affects how data is handled.
Access and authentication
- Users sign in with Google or Apple. We do not store passwords for user accounts.
- Access is by invitation. Only approved emails can create an account.
- Database access is controlled by row-level security so a signed-in user can read only their own household’s rows.
- Administrative access to hosting, database, Plaid and code repositories is limited to the operator and protected with multi-factor authentication. Access is removed when no longer needed.
Data protection
- All traffic uses TLS (HTTPS). Data is encrypted at rest by our database provider.
- Plaid access tokens are additionally encrypted in the application (AES-256-GCM) with a key kept outside the database, in the hosting provider’s secret store.
- We never receive or store bank credentials. Those go directly to your bank through Plaid.
- Secrets and API keys are kept in environment variables, never in source code, and are rotated if exposed.
- Plaid webhooks and scheduled jobs are authenticated with secrets before they act.
Minimizing and deleting data
We request only the Plaid products the app needs (transactions and the related balances), cap the number of banks per user, and disconnect banks when access ends. Users can delete their account, which disconnects their banks at Plaid and removes their data from our database. See the privacy policy for retention.
Systems and vendors
Production runs on managed services (Vercel for hosting, Supabase for database and sign-in, Plaid for bank connections). We use vendors that maintain recognized security programs and review them when we add or change one. Dependencies are kept current and checked for known vulnerabilities, and changes are made through version control before deployment.
Monitoring and incident response
We review hosting and database logs for errors and unusual access. If we suspect an incident, we contain it (revoke keys and sessions, disconnect affected bank links), investigate, fix the cause, and notify affected users and Plaid, and any regulators, as required by law and our agreements.
Reporting a vulnerability
Please email info@gridworksolutions.com with details. We will acknowledge reports promptly and will not pursue good-faith researchers.
