Privacy notice
Last updated September 5, 2026
What we collect
When you create a Decyml account, we collect your name and email address and store a secure hash of your password. When you join the early-access list, we collect your email address and may also store basic campaign information from the link you used, such as UTM parameters, the referring page, and the landing-page URL. We place a first-party cookie on that browser so the site can remember that you joined; the cookie does not contain your email address. When you connect or import accounting data, we store normalized transaction details, including transaction notes, memos, and line-item descriptions, source categories, and review history. Uploaded CSV files are processed for import but are not retained after the request.
How we use it
We use this information to operate your workspace, import and search transactions, suggest categories, surface items for human review, measure interest in Decyml, and send occasional product research or launch updates. We do not sell waitlist or transaction information.
Storage and sharing
Account, waitlist, normalized transaction, and review data is stored in Decyml's application database. The current site does not use third-party advertising pixels or behavioral analytics.
When you select transactions for AI review, Decyml sends the transaction fields needed for categorization and anomaly review, including their notes, memos, and line-item descriptions, to OpenAI for processing. API requests disable response storage, but provider processing remains subject to OpenAI's applicable terms and policies.
Check documents and extraction
When you upload a check, we store the original image or PDF encrypted in Decyml's database, its client association, extracted payee/date/check number/amount/memo, and your review corrections. The document and review data are retained until you delete the check in its review screen or request account deletion. Deleting a check removes its application record and stored document; existing backups follow the site's backup retention process.
The full check image is sent to the configured AI provider described above, including OpenAI when it is the primary provider or an explicitly configured fallback. Check PDFs go directly to OpenAI when it is the primary provider or explicit fallback; PDF extraction is unavailable in an Ollama-only configuration. Any routing numbers, account numbers, signatures or other information visible in the document are included in that processing even though Decyml does not extract them as separate fields. OpenAI check requests disable response storage. Extracted check fields remain drafts until you confirm them. Extraction and confirmation do not post to QuickBooks; you can separately prepare and approve a sandbox expense.
Statements, financial reports and workflows
When you upload a bank or credit card statement, we store the original PDF encrypted in the application database, extracted and corrected statement data, the selected account, and comparison results. PDF extraction sends the complete document to OpenAI when OpenAI is the configured provider or explicit fallback, including details printed on its pages. Response storage is disabled. PDF extraction is unavailable with an Ollama-only configuration. Deleting a statement removes its PDF and application extraction/comparison record; existing backups remain subject to the site's backup retention process.
QuickBooks report review stores the requested P&L reports, periods, basis, computed comparisons and optional AI summary drafts and review questions. Generating a draft sends calculated financial observations, including totals, margins and selected account changes, to the configured AI provider described above. AI writes an introduction and selects highlights; Decyml inserts the corresponding saved financial figures. The generated wording and questions require accountant review. We also store workflow templates and published versions, client assignments and settings, linked review records, monthly runs and review notes to track your work.
When you request an allocation suggestion, the source payee, date, amount, memo and line descriptions, together with eligible company GL accounts and class names, are sent to the configured AI provider described above. We store the proposed allocations and review notes. Suggestions require your review and saving; posting still requires separate approval of the exact saved change.
Review rules can store separate GL account and class mappings for each client, tied to that client's connected company. Saved rule proposals retain the mapping used for the review. Rule-based allocation proposals run locally without an AI request and still require review and separate posting approval.
Preparing QuickBooks changes stores account, vendor and class references, a source snapshot, allocations, an approval record and the posting result. Each write requires explicit accountant approval; the initial posting flow supports sandbox companies. Deleting an uploaded source document does not delete a separate posting approval or change anything already recorded in QuickBooks. Contact us to request deletion of retained workflow, report or posting records.
Connected services
If you connect QuickBooks Online, Intuit handles the authorization screen and Decyml stores your QuickBooks company ID, encrypted authorization tokens, and the transaction details imported for your workspace. These credentials maintain the connection and will be used only for QuickBooks features you choose to use. You can revoke the connection from Settings; imported transaction data remains available until you ask us to delete it.
Your choices
You may ask to access or delete your account or waitlist information, or unsubscribe from future messages, by contacting admin@accthalo.com.
Product status
Decyml is an early-stage software concept. AI categories and anomaly flags are suggestions that require human review and may be incomplete or incorrect. Decyml does not provide accounting, tax, legal, or financial advice.