RICE Financial · Effective October 8, 2026

Privacy Policy

Your information, how we use it, and the choices you have.

Scope and contact

This Privacy Policy explains how RICE Financial ("RICE", "we", "us") handles personal information when you use our website, financial workspace and Help Center. It covers the current beta product, including support and optional processing. Future services may have additional notices.

For privacy questions, access, correction or deletion requests, use Contact support below. You can verify a contact email without signing in to an app account. If you cannot access your account email, use an email you can access and explain the issue. We verify ownership before disclosing account information or making account changes.

Information we collect

Account information includes your email, authentication information, user identifiers, profile details and preferences. Workspace information includes the records you enter or import: accounts, balances, transactions, bills, subscriptions, obligations, people, business details, documents, notes and related metadata. You choose the information you add.

We also process sharing permissions, invitations, messages, support requests and their replies. Technical information can include IP addresses, browser and device information, request times, authentication events, delivery status and diagnostic logs needed to operate and protect the service. Do not put passwords, verification codes or unnecessary financial account numbers into support requests.

How we use information

We use information to create and secure accounts, store and display records, calculate summaries, process imports you initiate, provide sharing features, deliver service emails, respond to support requests, troubleshoot errors and improve the product. We also use information to prevent abuse, enforce our terms and meet applicable legal obligations.

The beta is manual-first. Recording a bank account or a payment does not connect us to your bank, move money or execute that payment. Public product previews use fictional records, not customer workspace data.

Sharing and service providers

Workspace access is private by default and sharing is permission-based. People you authorize can access the information covered by that permission. Social connections alone do not grant financial access. Information you deliberately publish through public-profile features can be viewed publicly. Revoking access cannot recall copies another person already downloaded.

We use service providers to operate the product, including Cloudflare for hosting, file storage and optional import AI, Neon for database and authentication services, and Resend for transactional email. Google services provide fonts and tag management. Providers receive information needed for their functions. Authorized personnel may access information when necessary for support, operations, security or legal obligations; this beta does not provide end-to-end encryption.

We may disclose information when required by law, to address fraud or security threats, protect legal rights, or in connection with a merger, acquisition or transfer of the service, subject to applicable law. The current product does not offer a customer-data sale or revenue-sharing program. Roadmap concepts are not permission to use your private records for such a program.

Optional AI and imports

Manual entry and standard imports can be used without cloud AI. If you choose AI assistance for a screenshot or pasted text, the selected source and context you provide are sent to Cloudflare Workers AI after the feature asks for your consent. This processing is not end-to-end encrypted. Review the proposed records before confirming what to save.

Extraction does not by itself save the original file to Archive. Files you separately upload for storage and records you confirm are retained in your workspace. Other optional AI features may describe their provider and data use separately before processing.

Cookies, analytics and third-party resources

Authentication and support use cookies or similar storage to keep sessions secure. Local browser storage also remembers preferences such as appearance and table layout. The public support verification cookie lasts up to 30 days; signing out of support clears it in that browser.

First-party analytics count broad page and feature categories and signed-in activity dates. They do not record financial amounts, record contents, keystrokes or full browsing URLs. Daily activity and aggregate counts are retained for up to 90 days; first and last observed account activity remain with the account. These counters respect Do Not Track and Global Privacy Control, and signed-in feature analytics also respect the analytics setting.

The site loads Google Tag Manager and Google Fonts. Third-party requests can disclose technical information such as IP address, browser details and page information; tags may use cookies or similar identifiers. The limits described for first-party counters do not describe every third-party tag. Browser controls can restrict cookies and third-party requests, although blocking essential storage may affect sign-in.

Retention and deletion

We retain workspace information while your account is active and as needed to provide the service. Retention depends on the information and purpose. Security, delivery, support and legal records may need to be retained to resolve disputes, prevent abuse or satisfy legal obligations. Backup copies can remain until the applicable backup or recovery period expires.

Account deletion is currently handled through a verified support request, not an immediate self-service purge. We confirm ownership and scope, including owned files, shared records and account access, before completing a request. We will explain any information we must retain or cannot remove, and confirm the result. A request alone does not delete your account. Records independently owned by other users and copies they already hold may remain.

Your choices and rights

You can edit records, manage sharing, choose whether to use optional AI and adjust available analytics preferences. Settings > Data exports owned records and document metadata as JSON. Download original documents separately. This export excludes file bytes, conversations, sharing permissions and other users' records; contact support for requests outside its scope.

Depending on where you live and which laws apply, you may have rights to access, correct, delete or obtain a copy of personal information, object to or restrict processing, withdraw consent, or appeal a decision on a request. Contact support to exercise a right or appeal a response. We may request information needed to verify your identity and will respond within the period applicable to your request. You may also contact your local data-protection authority.

Security, location and age

We use authenticated access checks, permissions and other technical measures to protect information. No service can guarantee absolute security. Protect your email and account credentials, review sharing permissions and keep independent copies of important records.

The service and its providers may process information in the United States and other countries where they operate. Privacy protections can differ by location. Where required, appropriate safeguards must apply to international transfers.

RICE Financial accounts are intended for adults aged 18 or older. If you believe a child has created an account or provided information inappropriately, contact us so we can investigate and address it.

Policy updates

We will update this page when our practices change and display the updated date. For material changes, we will provide additional notice through the product or email where appropriate, and obtain consent when required.