LegalForty Two Six
Privacy policy
How Forty Two Six handles account, company, financial, document, and service data.
About Forty Two Six and this policy
Forty Two Six is wholly owned by Timothy LeGendre CPA LLC, based in Florida. This policy explains how information is handled when someone visits the Forty Two Six website, creates an account, joins a workspace, or uses the accounting service.
Questions about privacy, legal matters, or support may be sent to [email protected].
Information we handle
The information we handle depends on how you use the service. It may include the following categories:
- Account and profile information, including your email address, user identifier, account dates, display name, and profile details returned when you choose Google sign-in, such as a name or avatar.
- Company and workspace information, including entity names, business type, tax classification, fiscal-year settings, member names and email addresses, roles, and invitation records.
- Financial and bookkeeping information, including charts of accounts, transaction dates, amounts, descriptions, merchant names, journal entries and lines, memos, categorization and clearing status, reconciliations, balances, and period locks.
- Documents and file information that you choose to upload, including the file itself, filename, type, size, digest, uploader, workspace or entity association, and any link to a journal entry or transaction. Uploaded records may contain information about customers, vendors, employees, owners, or other people.
- Connection and service information, including provider and external-account labels, account masks, synchronization status, API-key names and prefixes, creation and last-use dates, request identifiers, and security or migration records.
- Technical information used to deliver and protect the service, such as source-address or IP information, request timing, browser or device metadata made available to hosting systems, and application activity used for authentication, rate limiting, troubleshooting, and security.
- Subscription and payment status. Where a payment provider is used, it receives payment details directly. Forty Two Six may receive customer, checkout, subscription, price, invoice, and event identifiers and related status, but the application is not designed to receive a full card number from the checkout form.
How information reaches us
We receive information when you create or update an account, configure a company, invite a workspace member, enter or upload records, use an export or integration, contact us, or otherwise use the service. A workspace member may also provide information about you or give you access to records in that workspace.
We also receive limited information from services used to operate Forty Two Six. For example, Supabase supports authentication, database, file storage, and server functions. Google provides sign-in information when you choose Google sign-in and serves the website fonts. Hosting and security systems may produce ordinary request metadata.
How we use information
We use information for the following purposes:
- Provide, maintain, and secure accounts, workspaces, accounting records, document storage, exports, and customer-requested services.
- Authenticate users, apply workspace permissions, support optional multi-factor authentication, prevent abuse, rate-limit requests, and investigate security or service issues.
- Process bookkeeping instructions, organize financial inputs, produce reports and exports, support reconciliation and audit history, and provide an Operated service when separately agreed.
- Administer subscriptions, confirm access, respond to questions and requests, communicate service or policy changes, and keep operational, tax, accounting, dispute, and legal records.
- Debug and improve the reliability, usability, and performance of the service using information reasonably needed for those purposes.
Google sign-in
If you choose Google sign-in, Google authenticates you and returns the account information needed for that sign-in, including your email address and potentially your name and avatar. Forty Two Six uses that information to create or identify your account and display your profile. Google sign-in does not itself give Forty Two Six access to your Gmail, Google Drive files, or financial records.
Your use of Google services is also governed by Google’s terms and privacy practices.
Exports, API, and MCP
The service can create CSV exports for selected accounting records. You can also create a key and connect a compatible outside client that can read the workspace information you authorize, such as entities, accounts, journal data, bank transactions, or trial balances.
Forty Two Six does not select the outside client or control what it does with information after you direct the transfer. Review the recipient’s privacy and security practices before connecting it, protect your key, and revoke the key if access should end. The platform sends authorized data to the client you choose; it does not invoke AI or another model to process that data.
Browser storage and service metadata
The application uses browser storage to keep an authenticated session, remember a theme choice, and remember the last-selected entity. Authentication, hosting, and other infrastructure providers may use cookies or similar technologies when needed to provide their services. Hosting and security systems may also log ordinary metadata such as an IP address, browser details, timestamps, and requested pages or endpoints.
Do not use a shared or public device for sensitive records unless you can sign out and clear the browser data safely.
Retention
We expect to retain information while an account or service relationship is active and afterward when reasonably needed to operate the service, preserve accounting and audit history, maintain security records, resolve disputes, comply with tax, accounting, or other legal obligations, and protect legal rights. Different records may require different retention based on their purpose and sensitivity.
Deletion from an active system may not immediately remove information from backups or records that must be retained. When information is no longer reasonably needed, it should be deleted, de-identified, or otherwise disposed of in a manner appropriate to the information and the systems that hold it.
Your choices and requests
You can update certain profile and workspace information in the service, remove individual documents and settings where controls are available, revoke API keys, export selected records as CSV files, and export each book’s chart of accounts, journal entries and lines, bank transactions and trial balance as an Excel workbook. Uploaded documents, rules and settings are not part of that export, and the application does not currently provide complete self-service account deletion.
To ask for access, correction, export, or deletion of other information, email [email protected]. We may need to verify your identity and authority over the account or workspace. A request may be limited where retention is reasonably required, where records concern another person or workspace member, or where applicable law permits or requires continued handling. Applicable law may provide additional rights.
Security
Forty Two Six uses safeguards intended to reduce the risk of unauthorized access, alteration, disclosure, or loss. Current application controls include passwordless authentication, optional multi-factor authentication, workspace-based access checks, hashed API keys, file validation, time-limited download links, and audit-oriented records. Service providers also protect the systems they operate under their own security programs.
No service or transmission method can be guaranteed completely secure. You are responsible for protecting access to your email, authentication methods, devices, exported files, and API keys, and for notifying us promptly at [email protected] if you believe an account or workspace has been compromised.
Accounts and records about other people
Forty Two Six accounts are intended for people who have the legal capacity and authority to use the service for themselves or an organization. Do not create an account for someone who cannot legally agree to these terms or intentionally provide information collected directly from a child through the service.
Accounting records often contain information about other people. Before entering, uploading, sharing, or exporting that information, you are responsible for having the rights and authority needed to do so and for giving any notices or obtaining any permissions required by applicable law or your agreements.
Updates and contact
We may update this policy as the service or our practices change. We will post the revised policy with a new date and provide any additional notice required by applicable law.
Contact [email protected] with privacy questions, legal requests, or support needs.