Purpose and status
BooksAI is a product of SumPulse Software Inc. This overview explains the service at a customer-facing level. It is not an executed data-processing agreement, a certification or a promise of a specific hosting arrangement.
Our security and compliance documentation program is in progress. If your organization requires a DPA, formal subprocessor terms, transfer provisions or a security schedule, contact us before submitting data and confirm any commitments in writing.
The data journey
1. Connect and submit: an authorized user connects a supported company or provides a document or question. Workspace membership and company permissions determine intended access.
2. Retrieve and prepare: BooksAI uses relevant connected records and supplied context to answer questions, suggest coding and prepare work. An AI provider may process selected context.
3. Review and act: your team reviews the result or configures rules for eligible automated work. The applicable workflow, permissions and connection determine which actions can reach QuickBooks.
4. Report and retain: reports, approval activity and posting records support the working history. Exports and connected channels introduce copies that may be governed outside BooksAI.
Your organization’s responsibilities
Connect only records and companies you are authorized to use. Establish an appropriate basis for processing personal or financial information and inform affected people when required.
Choose appropriate administrators, company grants and booking policies. Review source data and AI-prepared results, manage user access and protect provider accounts.
Assess your own accounting, tax, privacy, employment and industry requirements. The presence of a product control does not by itself establish legal or regulatory compliance.
Provider and channel choices
Managed AI primarily uses the Claude-led experience described on our AI options page, subject to your plan and configuration. Customer-supplied keys route supported requests through the selected provider account.
Provider terms, billing, model availability and processing locations can differ. A bring-your-own key does not mean that information remains on your device.
Web chat is available; Telegram is a private pilot; Slack is planned. Channel availability and supported actions may change. Review the destination and audience before sharing records through messaging platforms.
Access and retention lifecycle
Before onboarding, identify the companies, users, providers and data types your team intends to use. Resolve any special contractual or regional requirements with us.
During use, review permissions, provider access, learning settings and exceptions. Keep company guidance current and manage access when people change roles.
When leaving, export needed information, remove or disconnect available connections and request account or data closure through support. Confirm what must be retained and how existing copies, backups, audit records or third-party exports are handled. No immediate universal deletion promise is made here.
What to confirm with us
For procurement, ask about the processing services applicable to your configuration, retention and deletion arrangements, incident communication, any requested DPA, regional requirements and available assurance evidence.
Independent certifications and attestations have not yet been completed. Do not treat a supplier’s certification as certification of BooksAI or SumPulse Software Inc.
Contact Krishna@booksai.io for the discussion. Use the initial message to describe your requirements; do not send secret keys or sensitive customer documents.
Questions? Contact SumPulse Software Inc.