Our policies
Acceptable use policy
Effective September 20, 2026 · Version 2026-09-20-v3
On this page
Questions? Contact supportReview before reliance
Extraction creates a draft. Do not present unreviewed rows as verified records, conceal known errors, or use an export as a substitute for the original statement when the source is legally or operationally required.
Protect accounts and API keys
Do not share credentials, expose workspace API keys, bypass workspace roles, automate sign-in abuse, or attempt to access another workspace, private object, support attachment, admin surface, or operator function. Creating an account requires accepting the current terms, and acceptance may not be falsified, scripted around, or recorded for another person.
Respect quotas, credits, and discounts
Do not create duplicate accounts, manipulate client addresses, replay idempotency keys with changed payloads, exploit retries, or otherwise evade page limits. Page credits and promotion codes may not be transferred, resold, counterfeited, redeemed after expiration, redeemed beyond their disclosed redemption count, or obtained through payment fraud.
Use the API responsibly
Respect documented rate limits, idempotency requirements, file limits, and approval requirements. Do not probe for hidden data, send malware, interfere with service availability, or use the API to operate an unauthorized financial-data collection service.
Exports, storage, and delivery
Exports remain private objects within the statement's existing content lifetime. Do not attempt to discover object locations or keys, reuse or replay upload or download authorizations, bypass the storage proxy, distribute export links unlawfully, or extend, defeat, or circumvent expiration and deletion controls.
Communication
Transactional email is limited to account, billing, allowance, and support messages. Do not use support or invitation mail to send unsolicited or unlawful content, misrepresent who you are, or trigger delivery to addresses you are not authorized to contact.
Enforcement
Fulla may reject a request, set a workspace to read-only, revoke an API key, deactivate a discount, cancel a fraudulent purchase, or suspend access needed to protect users and the service. Required billing, security, and audit records may be retained as described in the Privacy notice.
Questions: contact support. See the Terms of service and Privacy notice.
A question about our policies?
Contact us about the way Fulla Ledger handles your information and statements.