← Back to ReadyReceipt

Privacy Policy

Last updated: June 25, 2026

1. Introduction

This Privacy Policy explains how ReadyReceipt by CJT ("ReadyReceipt," "we," "us," or "our") collects, uses, stores, processes, and protects information when you use ReadyReceipt at readyreceipt.cjt.solutions.

ReadyReceipt is operated by CJT Solutions of Texas LLC. We may refer to ourselves in these documents as "CJT Solutions," "CJT," "we," "us," or "our." ReadyReceipt is designed for U.S.-based businesses that need receipt extraction, review, verification, and export tools. We understand that receipts may contain financial, vendor, payment, tax, reimbursement, and other business-record information, so this Privacy Policy is intended to explain our practices in plain language.

If you have questions about this Privacy Policy, contact us at:

CJT Solutions of Texas LLC
DBA / public name: CJT Solutions
Email: hello@cjt.solutions
Product: readyreceipt.cjt.solutions

2. U.S.-Only Service and Restricted Jurisdictions

ReadyReceipt is intended for use by U.S.-based businesses and authorized users located in the United States.

ReadyReceipt is not offered to, directed to, or intended for use by individuals, businesses, organizations, or users located in the European Economic Area, the United Kingdom, Switzerland, or any other jurisdiction we designate as restricted.

We may use technical, billing, fraud-prevention, and compliance controls to enforce this restriction, including IP-based access controls, card-issuing-country checks, billing-country checks, account review, and other signals.

You may not access or use ReadyReceipt from a restricted jurisdiction, use a VPN, proxy, false billing information, false account information, or other method to bypass these restrictions, or use ReadyReceipt on behalf of a person or business located in a restricted jurisdiction.

If we determine that an account is associated with a restricted jurisdiction or has attempted to bypass these restrictions, we may suspend or terminate the account and delete, restrict, or preserve associated data as described in this Privacy Policy and our Terms of Service.

3. Business-Use Product

ReadyReceipt is designed for business receipt processing. It is not intended to be used as a personal document vault, medical-record system, legal-record archive, government-record archive, or long-term tax-record custodian.

Users may accidentally upload personal or non-business receipts. ReadyReceipt may still process, classify, extract, reject, flag, review, or store those files as part of the normal operation of the service. Users are responsible for ensuring that they have the right to upload and process any receipt, image, document, or data submitted to ReadyReceipt.

4. Information We Collect

4.1 Account Information

When you create an account or are invited to a tenant, we may collect and store account-related information, including:

  • Name
  • Email address
  • Authentication provider user ID
  • Tenant or business association
  • Assigned role, such as owner, admin, or member
  • Account status
  • Login, session, and authentication metadata

Authentication is handled by Clerk. We do not store your password in ReadyReceipt.

4.2 Tenant and Team Information

ReadyReceipt is a multi-tenant product. Each tenant generally represents a business, organization, client account, or workspace.

We may collect and store information about your tenant, including:

  • Tenant name
  • Tenant ID
  • Team members
  • User roles and permissions
  • Invitations
  • Seat usage
  • Subscription status
  • Receipt usage limits
  • Billing-plan association

Team members within a tenant may be able to view receipt data, extracted data, verification activity, exports, and other tenant information depending on their role.

4.3 Receipt Images

When you upload receipt images, we collect and store the original uploaded files. Supported formats may include JPEG, PNG, WebP, or other formats we choose to support in the future.

Receipt images may contain information such as:

  • Vendor or merchant name
  • Transaction date and time
  • Purchased goods or services
  • Total amount
  • Tax amount
  • Payment method details
  • Last four digits of a payment card
  • Business location
  • Personal or business notes printed on the receipt
  • Other information visible in the image

Receipt images are stored in Cloudflare R2 object storage. Images may be organized using tenant-specific paths, object keys, metadata, hashes, or other identifiers.

We may generate a cryptographic hash, such as a SHA-256 hash, to help detect duplicate uploads, support integrity checks, or operate the service.

4.4 Extracted Receipt and Financial Data

ReadyReceipt uses AI-assisted processing and application logic to extract structured information from receipt images.

Extracted data may include:

  • Vendor name
  • Transaction date
  • Transaction time
  • Total amount
  • Subtotal
  • Tax amount
  • Tip amount
  • Currency
  • Last four digits of a visible payment card
  • Transaction category
  • Line items
  • Line-item descriptions
  • Line-item quantities
  • Unit prices
  • Line-item amounts
  • Suggested categories
  • Confidence scores or processing metadata
  • Failed extraction status
  • User edits and corrections

Extracted and verified data may be stored in Cloudflare D1 or other databases we use to operate ReadyReceipt.

4.5 Verification, Review, and Audit Data

ReadyReceipt includes review and verification workflows. We may collect and store data about those workflows, including:

  • Who uploaded a receipt
  • Who reviewed a receipt
  • Who verified, skipped, rejected, edited, deleted, restored, or exported a receipt
  • Timestamps
  • User IDs
  • Tenant IDs
  • Status changes
  • Audit events
  • Permission denials
  • Security-relevant events

This information helps provide accountability within a tenant, prevent conflicting edits, support customer troubleshooting, and investigate abuse or security incidents.

4.6 Export Data

ReadyReceipt may generate export files in formats such as CSV, QuickBooks-compatible formats, Xero-compatible formats, or other formats.

Exports may contain verified receipt data, line items, categories, dates, vendors, amounts, and other information selected or generated through the service.

Exports may be stored temporarily or persistently in Cloudflare R2 or other infrastructure until deleted according to your settings, user action, or our retention practices.

4.7 Billing Information

Paid subscriptions are processed by Stripe.

We may collect and store billing-related metadata, including:

  • Stripe customer ID
  • Stripe subscription ID
  • Plan or tier
  • Billing status
  • Seat count
  • Usage limits
  • Payment status
  • Invoice status
  • Cancellation status
  • Billing email
  • Billing country or payment-related location signals

We do not store full credit card numbers, CVVs, or complete payment credentials. Payment method details are handled by Stripe.

Stripe may collect and process payment method information, billing address, tax information, fraud-prevention signals, and other payment-related information under Stripe's own terms and privacy practices.

4.8 Usage, Analytics, and Product Telemetry

We use product analytics and telemetry tools, including PostHog, to understand how ReadyReceipt is used, improve features, diagnose errors, detect unusual behavior, and make product decisions.

Depending on our configuration, analytics and telemetry data may include:

  • Email address
  • User ID
  • Tenant ID
  • IP address
  • Browser and device information
  • Operating system
  • Approximate location derived from IP address
  • Page views
  • Feature usage
  • Clicks and events
  • Referrers
  • Error information
  • Session metadata
  • Timestamps
  • Subscription or plan metadata

This analytics data is not anonymous if it is associated with identifiers such as email address, user ID, tenant ID, IP address, or device information. We may use aggregated, pseudonymous, or account-associated analytics to operate and improve ReadyReceipt.

We do not intentionally send receipt images, receipt line items, extracted receipt contents, full payment card numbers, government identification numbers, or sensitive document contents to PostHog.

If we enable session replay, screen recording, or similar analytics features in the future, we will configure masking or exclusion controls for sensitive fields and update this Privacy Policy before using those features in production.

4.9 Security Logs and Technical Data

We may collect security and technical data, including:

  • IP addresses
  • Authentication events
  • Failed login attempts
  • Permission denials
  • Suspicious activity
  • Abuse signals
  • Rate-limit events
  • API errors
  • Application errors
  • Device and browser metadata
  • Request metadata
  • System logs
  • Infrastructure logs

We use this information to secure ReadyReceipt, investigate incidents, enforce our Terms of Service, debug problems, and protect users and the platform.

4.10 Communications

If you contact us, we may collect your name, email address, message contents, attachments, support history, and other information needed to respond.

We may also send service-related emails, billing emails, security notices, usage-limit notices, account notices, and other operational communications.

5. How We Use Information

We use information collected through ReadyReceipt to:

  • Provide receipt upload, storage, extraction, review, verification, and export features
  • Operate tenant workspaces and team permissions
  • Authenticate users
  • Enforce role-based access controls
  • Process subscriptions and billing
  • Enforce plan limits, receipt limits, and seat limits
  • Detect duplicate receipts
  • Generate exports
  • Provide customer support
  • Troubleshoot technical issues
  • Improve product performance and usability
  • Analyze product usage
  • Detect, prevent, and investigate abuse, fraud, attacks, unauthorized access, and security incidents
  • Enforce our Terms of Service
  • Comply with legal obligations
  • Respond to lawful requests
  • Protect ReadyReceipt, CJT Solutions of Texas LLC, our users, and the public

We do not sell receipt images or extracted receipt data.

We do not use customer receipt images to train or fine-tune AI models.

6. AI Processing

ReadyReceipt uses AI-assisted processing to extract structured data from receipt images.

When you upload a receipt, the image and related processing data may be sent to AI inference systems, including Cloudflare Workers AI or other providers we may use in the future. These systems process the image to identify and extract information such as vendor, date, total, tax, payment details, categories, and line items.

AI extraction may be inaccurate, incomplete, delayed, or unavailable. Receipt images may be unclear, damaged, unusual, incomplete, handwritten, cropped, blurry, or otherwise difficult to process.

You are responsible for reviewing and verifying extracted data before using it for bookkeeping, accounting, tax, reimbursement, reporting, or other business purposes.

Our current AI processing provider states that customer content submitted to Workers AI is not used to train AI models or improve services without explicit consent. We do not use customer receipt images to train or fine-tune models. If our AI provider's data-use practices materially change, or if we add a materially different AI provider, we will update this Privacy Policy as appropriate.

7. CJT Access to Customer Data

ReadyReceipt is operated by CJT Solutions of Texas LLC. Authorized CJT personnel may access customer account data, tenant data, receipt images, extracted data, exports, logs, and related metadata when reasonably necessary to:

  • Operate the service
  • Provide customer support
  • Troubleshoot technical issues
  • Investigate abuse
  • Investigate security incidents
  • Enforce our Terms of Service
  • Comply with legal obligations
  • Respond to lawful requests
  • Protect ReadyReceipt, CJT Solutions of Texas LLC, users, or the public

Administrative access may include access through Cloudflare R2, Cloudflare D1, application logs, authentication systems, billing systems, analytics tools, infrastructure dashboards, or other service-provider dashboards used to operate ReadyReceipt.

We do not access customer receipt contents for unrelated purposes. We do not sell customer receipt contents.

8. Subprocessors and Third-Party Services

We use third-party service providers to operate ReadyReceipt. These providers may process information on our behalf.

ReadyReceipt subprocessors and the data they may process.
ProviderPurposeData Processed
CloudflareApplication hosting, storage, database, queues, AI inference, security, logs, email or infrastructure servicesReceipt images, extracted data, tenant data, account metadata, logs, technical data
ClerkAuthentication and user managementName, email address, authentication identifiers, sessions, login metadata
StripePayment processing and subscription managementBilling metadata, payment method information, customer ID, subscription ID, invoices, fraud-prevention data
PostHogProduct analytics, telemetry, error analysis, feature usageUser identifiers, tenant identifiers, usage events, browser/device data, IP address, error data, product telemetry

We may add, remove, or replace service providers as ReadyReceipt evolves. If we make a material change to the categories of providers or data processing described in this Privacy Policy, we will update this Privacy Policy.

9. Safety, Abuse Detection, and Illegal Content

ReadyReceipt is intended for ordinary business receipt processing. You should not upload illegal content, abusive content, child sexual abuse material, exploitative material, malware, or documents you do not have the right to process.

We may use automated tools, hashing technologies, manual review, third-party trust-and-safety services, or other safety systems to detect, prevent, report, or respond to illegal or abusive content.

If we become aware of apparent illegal content, including apparent child sexual abuse material, we may preserve relevant information, suspend or terminate accounts, and report information to appropriate authorities as required or permitted by law.

10. Legal Requests and Required Disclosures

We may disclose account data, receipt data, logs, billing metadata, or other information if we believe disclosure is required or permitted by law, including in response to:

  • Subpoenas
  • Court orders
  • Warrants
  • Law-enforcement requests
  • Tax authority requests
  • Regulatory requests
  • Legal process
  • Emergency requests involving risk of harm
  • Requests necessary to protect ReadyReceipt, CJT Solutions of Texas LLC, users, or the public

We may notify affected users of legal requests when legally permitted and when we believe notice is appropriate. We may delay or withhold notice where prohibited by law, where notice would create a security or fraud risk, or where notice would interfere with an investigation.

11. Cookies, Local Storage, and Similar Technologies

ReadyReceipt may use cookies, local storage, and similar technologies for:

  • Authentication
  • Session management
  • Security
  • Remembering user preferences
  • Theme settings
  • Product analytics
  • Error diagnostics
  • Fraud and abuse prevention

Clerk may use cookies to maintain login sessions. Without essential authentication cookies, you may not be able to use ReadyReceipt.

PostHog or similar analytics tools may use cookies, local storage, or other identifiers to distinguish users, analyze product usage, and diagnose issues.

We do not use advertising cookies, third-party advertising pixels, or social media tracking plugins in the ReadyReceipt application.

12. Data Storage and Security

ReadyReceipt uses Cloudflare infrastructure and other service providers to store and process data.

We implement technical and organizational measures designed to protect data, including:

  • Tenant isolation
  • Role-based access controls
  • Authentication requirements
  • Authorization checks
  • Input validation
  • File-type and file-size restrictions
  • Security headers
  • CSRF protections
  • Logging of security-relevant events
  • Audit trails for sensitive actions
  • Duplicate-detection mechanisms
  • CSV formula-injection protections for exports
  • Access controls for infrastructure and administrative systems

No system is perfectly secure. We cannot guarantee that unauthorized access, data loss, outages, vulnerabilities, or security incidents will never occur.

If we determine that a security incident requires notification, we will notify affected users and regulators as required by applicable law and without unreasonable delay.

13. Data Retention

We retain information for as long as reasonably necessary to provide ReadyReceipt, operate our business, comply with legal obligations, resolve disputes, enforce our Terms of Service, prevent abuse, and maintain security.

Our general retention approach is:

  • Active account receipt images: Retained until deleted by the user, cleared by the tenant, or deleted after cancellation or termination.
  • Extracted and verified receipt data: Retained while the account is active unless deleted by the user or tenant.
  • Individual deleted receipts: May be soft-deleted for a limited recovery period before permanent deletion from active systems.
  • Clear ledger actions: Intended to delete receipt data, line items, and exports from active tenant systems. Some metadata, logs, backups, or security records may remain for a limited period as described below.
  • Exports: Retained until deleted by the user, cleared by the tenant, or deleted after cancellation or termination.
  • Audit and security logs: May be retained for security, abuse prevention, compliance, and accountability purposes.
  • Billing records: May be retained as needed for accounting, tax, fraud prevention, dispute resolution, and legal compliance.
  • Backups and disaster recovery systems: Deleted data may persist for a limited period before being overwritten or purged according to backup and disaster recovery practices.
  • Aggregated analytics: May be retained for product analysis if not reasonably linked to a specific person, receipt, or tenant.

Upon account cancellation or termination, we may retain account and tenant data for a limited recovery and export period, generally 30 days, unless a different period is required for legal, billing, security, fraud-prevention, or operational reasons. After that period, we may delete or de-identify data from active systems.

ReadyReceipt is not intended to be your only copy of tax, accounting, reimbursement, or business records. You are responsible for exporting and preserving records you need.

14. User Controls and Choices

Depending on your role and subscription status, you may be able to:

  • View receipt data
  • Edit extracted data
  • Verify receipt data
  • Delete individual receipts
  • Clear tenant receipt data
  • Generate exports
  • Download exports
  • Manage team members
  • Manage billing
  • Cancel your subscription

You may request account deletion by contacting us at hello@cjt.solutions.

We may need to verify your identity, account ownership, tenant authority, or role before fulfilling certain requests.

We may deny, delay, or limit requests where permitted by law, including where necessary to protect security, prevent fraud, comply with legal obligations, resolve disputes, preserve evidence, or protect other users.

15. Children's Privacy

ReadyReceipt is intended for U.S.-based businesses and authorized business users. It is not intended for children under 13.

We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to ReadyReceipt, contact us at hello@cjt.solutions, and we will take appropriate steps to delete the information.

16. Business Transfers

If CJT Solutions of Texas LLC is involved in a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar transaction, ReadyReceipt data may be disclosed, transferred, or assigned as part of that transaction, subject to this Privacy Policy or a successor policy.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

If we make material changes, we will provide notice by email, in-app notice, website notice, or another reasonable method before or when the changes take effect, unless immediate changes are necessary for legal, security, or operational reasons.

The "Last updated" date at the top of this Privacy Policy reflects the most recent revision.

18. Contact

If you have questions about this Privacy Policy, your data, or ReadyReceipt's privacy practices, contact us at:

CJT Solutions of Texas LLC
DBA / public name: CJT Solutions
Email: hello@cjt.solutions
Product: readyreceipt.cjt.solutions