Legal
Privacy Policy
Your business records can include personal information. This policy explains AccountGo's role, the information involved in using our website and products, and the choices and rights that may apply to you.
1 Who we are and scope
This policy describes how AccountGo (“AccountGo,” “we,” or “us”) handles personal information.
This policy covers the website at accountgo.dev, the application at app.accountgo.dev, and the related API at api.accountgo.dev. AccountGo offers Invoicing & Bills and Accounting, with an Enterprise offering for tailored Accounting requirements. The features available depend on the applicable product and agreement.
Third-party websites and services have their own privacy notices. This policy does not replace a customer's agreement or any applicable data processing addendum.
2 Our role and your workspace
Our privacy role depends on the activity, not simply on who owns the software. A business customer may determine why personal information is included in its invoices, bills, and accounting records. Where AccountGo processes that information on the customer's behalf, the customer's instructions and applicable data processing terms govern that processing.
AccountGo may separately act as a controller for activities such as its own account administration, support, and website operations. A customer's privacy notice explains its own uses of information.
If your information is in another business's workspace
Contact that business about its records or instructions. You may also contact AccountGo about our processing. Where we act as a processor, requests must be handled in coordination with the responsible customer.
Workspace membership includes Owner, Admin, and Member roles. Owners and administrators have broad workspace permissions; member access depends on assigned security roles. Authorized workspace users can see business records and other members' names, email addresses, roles, and membership details. Removing a person's membership does not erase the business records they helped create.
3 Information we handle
The inventory below distinguishes implemented product workflows from details still needing production verification. It is not a claim that every category is collected from every visitor.
| Category | Information and source |
|---|---|
| Accounts and workspaces | Registration requires an email address and first and last names. Profiles can include a phone number. Sign-in uses emailed verification codes; the API also supports Google sign-in when configured, using a verified email and Google account identifier. Account records include identifiers and authentication information; workspace records include names, URL slugs, membership, roles, permissions, invitations, and accounting settings. |
| Business and accounting records | Business legal/trading names, tax identifiers, contact and postal details; client and vendor names, emails, phones, and addresses; invoice and bill lines, dates, amounts, taxes, notes, payment instructions, payment methods and references; and journals, account balances, reports, and available inventory records. Free-text fields can contain personal or sensitive information you enter. Recording a payment does not initiate a money transfer. |
| Communications | Information you choose to provide when contacting AccountGo. |
| AI interactions | Messages, conversation/session identifiers and history, current page route/title, user and workspace identifiers, role and plan/module context, requested financial-tool results, and submitted approval decisions or reasons. The assistant integration uses Anter; see section 7 for details and remaining provider questions. |
| Browser storage | Display preferences, last-used workspace, interface preferences, an unfinished workspace-creation draft, a temporary invitation token, and an authentication cookie. Service workers cache site/app assets. See the Cookie Policy for names, purposes, and lifetimes. |
| Technical and session information | Sign-in sessions record creation/expiry times, IP address as seen by the API, user-agent information, and token hashes/revocation status. Application email logs include recipient, subject, provider message ID, and delivery/error details. Cloudflare configuration enables persisted invocation logs and traces; the application also configures OpenTelemetry diagnostics and a conditional exporter. |
| Service messages and invoice delivery | Sign-in codes, welcome messages, and invitations are sent through the configured email service. Requested invoice emails and reminders include invoice information and a signed PDF link, an optional invoice PDF attachment, and a blind copy to the sender where applicable. Send history records recipient/sender details, subject, time, and provider message ID. |
| Subscription information | The application stores workspace plan, module entitlements, subscription status, and a validity field. The reviewed plan-change flow updates entitlements; it is not a subscription checkout. |
The current marketing-site code has no demo request form; the former demo endpoint returns an unavailable response without processing or echoing submitted contact details. That does not establish what infrastructure logs capture or prove that the reviewed version is deployed.
Email and name fields are required to register; access also requires verifying the email address. Creating a workspace requires its name and valid accounting settings, including a currency. Other people can supply your information through workspace invitations, client/vendor records, or invoices and bills. Without the required registration information and verification, the account cannot be activated.
4 How information is used
The implemented workflows use information to create and verify accounts; maintain sessions and workspace permissions; deliver sign-in codes and invitations; manage invoices, bills, payment records, and books; generate reports and downloads; send requested invoices and reminders; and diagnose delivery or service errors. Browser preferences preserve selected display and workspace settings. AI-related purposes are addressed separately below.
5 Legal bases
Where data protection law requires a legal basis, the basis must match the specific purpose and AccountGo's role. A customer's contract with AccountGo is not automatically a contractual basis for processing personal information about the customer's employees, suppliers, or clients.
| Purpose | Basis to assess |
|---|---|
| Account administration and services requested by an individual contracting with us | Contract necessity, where its conditions are met. |
| Business contact administration, security, and abuse prevention | Legitimate interests, where applicable, after assessing necessity and individuals' rights. |
| Records or disclosures required by law | A specific applicable legal obligation. |
| Optional processing requiring consent | Consent only where validly obtained and withdrawable. Enabling a feature alone does not establish valid consent. |
| Customer-controlled business records | The customer determines its basis; AccountGo's processor activities require documented instructions and applicable processing terms. |
7 AI and human review
The assistant sends messages through AccountGo's authenticated API to Anter. Context includes the page route/title, conversation identifier, user and workspace identifiers, workspace role, plan, enabled modules, and subscription status. Financial tools can return the chart of accounts, trial balance, balance sheet, income statement, and paginated posted ledger transactions, including account names, balances, descriptions or narrations, and document types.
The five financial tools implemented in this repository read records; they do not post journals, modify records, or transfer money. Access is scoped to the current workspace. Tools check enabled accounting/report modules; reports and ledger retrieval also check the user's relevant permissions. Context is not limited to anonymous totals: descriptions and ledger narrations may contain personal information.
The integration supports human-in-the-loop review through approve/deny decisions on tool requests, with an optional reason sent to Anter. It also retrieves conversation history and forwards conversation deletion requests to Anter. This is not evidence that an AccountGo employee or accountant reviews every answer, or that every tool call always requires approval.
See the AI Feature Disclosure for the proposed public explanation. The product also needs an accurate notice at the point of AI interaction.
8 International transfers
Data location and access depend on the actual deployment and provider arrangements. This draft makes no promise that information remains in a particular country.
9 Retention and deletion
Retention must account for service needs, customer instructions, applicable recordkeeping obligations, and necessary legal holds. Accounting records held by a customer may be subject to obligations separate from AccountGo's own obligations.
| Records | Period or criteria to establish |
|---|---|
| Account and workspace records | Self-service account closure marks the account deleted, revokes refresh sessions, removes stored sign-in-code tokens and memberships, and revokes pending incoming invitations. Identity/profile and historical records remain. Workspace deletion marks the workspace deleted rather than erasing its data. |
| Customer invoices, bills, accounting records, and exports | Clients/vendors with transaction history are archived rather than deleted. Approved bills are voided rather than deleted; invoice records preserve issued details. Invoice PDFs and selected accounting CSV downloads exist, but not a verified complete-workspace export. |
| AI conversations and review records | History is retrieved through Anter's session API; deletion requests are forwarded to it. Closing an AccountGo account does not invoke that conversation-deletion flow. |
| Support, billing, and legal records | Not yet established. |
| Operational logs and backups | Not yet established. |
Closing access is not erasure. You can request account closure in Profile by confirming your email address. You must first transfer ownership or delete workspaces where you are the sole owner or only active member; the last platform administrator also cannot close their account. Workspace deletion is an owner action requiring its URL slug as confirmation. Neither action automatically erases retained financial, identity, email, or AI records.
This draft does not promise a 30-day deletion period or immediate erasure. Token expiry, invitation expiry, and invoice-link expiry end their use; they do not establish deletion of the corresponding stored records.
10 Security
No system can be guaranteed completely secure. Protect your sign-in credentials, limit access to people authorized to use your workspace, and report suspected unauthorized access.
Implemented controls include emailed verification codes with a five-minute validity, hashed code verification, rotating refresh tokens stored as hashes on the server, an HttpOnly refresh cookie, and workspace membership/role checks. Profile provides active-session information and controls to revoke individual or other sessions. These specific controls are not a certification or guarantee of security.
Suspected vulnerabilities can be reported to support@accountgo.dev.
Where a personal data breach triggers notification duties, notifications must follow the applicable law and customer processing terms. A regulator's notification deadline is not necessarily the deadline or threshold for notifying individuals.
11 Your privacy rights
Depending on the law that applies and any exceptions, you may have rights to:
- request access to and correction of your personal information;
- request deletion or a portable copy of eligible information;
- restrict or object to certain processing;
- withdraw consent where processing relies on consent, without affecting the lawfulness of earlier processing;
- opt out of covered sales, sharing, targeted advertising, or certain profiling, where applicable; and
- complain to a supervisory authority or appeal a request decision where local law provides that right.
Requests may require identity verification or evidence that an agent is authorized to act for you. Where AccountGo processes information for a customer, we must coordinate with that customer rather than independently altering its business records.
Profile lets you update your first/last name and phone number and manage sessions. Available downloads include invoice PDFs and CSV files for the chart of accounts, financial statements, and the currently displayed/filtered ledger page. These tools are not a complete personal-data access or portability response, and account closure is not a complete erasure request.
12 Regional information
EEA and UK. Where applicable, individuals may complain to their competent supervisory authority. Confirm the relevant controller, representative or data protection officer, purposes, bases, transfer safeguards, and other required notice information before serving these markets.
California and other US states. Applicability depends on the business, processing, statutory thresholds, and exemptions. This draft does not establish that AccountGo is covered or exempt.
14 Children
AccountGo is designed for business invoicing and accounting. That audience description does not establish a minimum age or resolve how information about children in customer records is handled.
15 Changes to this policy
When this policy is revised, its last-updated date will change. Any material change requires the notice, consent, or other steps required by applicable law; revising this page alone does not authorize a new use of personal information.
16 Contact
General questions can be sent to support@accountgo.dev, the support address listed on this site. Do not email passwords or full accounting records.
Publication requires a complete data and vendor inventory, verified production practices, implemented rights processes, and qualified legal review. This draft is not a compliance certification.