REDSMART
All RedSmart applications

RedSmart Accounting and RedSmart Operations

Security & Trust

Last updated: October 29, 2026. Reflects Accounting 3.142.0 and Operations 1.55.2.

This page is for the person reviewing RedSmart Accounting or RedSmart Operations for your company. It describes how the two apps work today: where data lives, how people sign in, who can see what, what is recorded, and which outside companies process information.

It describes the software, nothing more. It is not an audit report or a certification, and it claims neither. If a feature is not listed here, do not assume the apps have it. Ask us at support@redsmartcorp.com.

Hosting and where data is stored

Signing in

MethodAccountingOperations
Email and passwordYesYes
Code sent by emailYesYes
Continue with GoogleYesYes
Sign in with AppleYesYes
Two-step sign-inYes (from 2.42.0)Yes (from 1.21.0)

Two-step sign-in

Roles and permissions

RedSmart support access

Audit trail

Your data

Financial controls (Accounting)

Uploaded files (Accounting)

Browser protections

Every page and API response from both apps carries these security headers:

The apps do not yet send a full script Content-Security-Policy.

Subprocessors

These companies process information on RedSmart's behalf to run the apps. This list covers only the services the apps' code calls.

CompanyWhat it does for usInformation involvedUsed by
Cloudflare, Inc.Runs the apps (Workers), stores the databases (D1) and files (R2), carries messages between the apps (Queues), runs the Turnstile human check, and keeps service secrets.All app data; visitors' IP addresses and request details.Accounting and Operations
ResendSends the apps' emails: sign-in codes, invitations and password links, two-step sign-in notices, in Accounting also partner-portal codes, invoices and statements, and in Operations purchase orders emailed to vendors.Recipient email address and the content of the message.Accounting and Operations
Anthropic, PBCAI model behind the in-app AI assistant, and behind document and receipt capture in Accounting.The question asked, the records the assistant looks up to answer it, the person's name or email and the company name; for capture, the uploaded document, the company's expense account list and earlier corrections.Accounting and Operations (document capture: Accounting only)
GoogleContinue with Google, if a person chooses it.Name and email address. RedSmart never receives the Google password.Accounting and Operations
AppleSign in with Apple, if a person chooses it.Email address, and name if the person allows it. RedSmart never receives the Apple ID password.Accounting and Operations
GitHubRedSmart's issue tracker for bug reports and feature requests sent from the app.The sender's email address, company name and identifier, what they wrote, and a link to any screenshot they attach, which opens without signing in.Accounting
CloudmersiveVirus scan of files vendors attach to a bill they enter in the partner portal.The uploaded file.Accounting
Stripe, Inc.Card and bank payment of invoices: when an invoice is sent, a payment request is created at Stripe. Stripe collects the payer's card or bank details itself. Bank feeds (Financial Connections), if a company connects a bank or card account: the bank sign-in happens in Stripe's window, and Accounting asks for transactions only.The invoice amount, currency and RedSmart's invoice and company identifiers; for bank feeds, the connected accounts' names and transactions.Accounting

In Accounting's document viewer, the browser loads the PDF.js viewer script (pinned version) from jsDelivr. The script reads the document in your browser; no document content is sent to jsDelivr.

Other RedSmart apps

Each of our other apps has its own security and privacy page:

Report a security issue

If you think you have found a security problem in RedSmart Accounting or RedSmart Operations, email support@redsmartcorp.com with "Security issue" in the subject. Tell us which app, what you found, and the steps to reproduce it. Please do not access other people's data or disrupt the service; under our Terms of Use, testing the apps' security needs our written permission first.

Related documents