Receipts and expense trails are sensitive. Receni is built so security, privacy, and user control are part of the product—not an afterthought buried in settings.
These badges summarize concrete practices—not paid seal programs. They reflect how we design, ship, and support Receni today.
TLS everywhere
App traffic uses modern HTTPS so data in motion stays encrypted between your devices and our services.
No data brokerage
We do not sell receipt or expense data. The product is funded by subscriptions—not by monetizing your paperwork.
You confirm saves
Parsed fields are reviewed by you before they count as saved. Nothing is silently written to your ledger.
Account-level controls
Dedicated flows help you delete data or close an account when you are done—no runaround.
Policy-backed promises
Our Privacy Policy and Terms define retention, rights, and acceptable use—written to match how the app actually behaves.
Hardened delivery
We ship updates regularly, monitor dependencies, and treat security findings as release-blocking when they affect customers.
Our commitment
Serious security means predictable behavior, honest limits, and fast follow-through when something looks wrong.
Transparency
Plain-language pages and policies so you know what is collected, why, and for how long.
Defense in depth
Transport security, access controls, and careful feature design stack together—no single checkbox “security theater.”
Continuous improvement
Threats evolve; so do we. Dependency hygiene, reviews, and customer feedback all feed the security roadmap.
From the moment a receipt hits your phone to the moment you export a CSV, we think about exposure, mistakes, and recovery paths.
Capture
Images and uploads stay inside the app until you choose to parse or sync. Prefer well-lit scans to reduce retries that send extra bytes.
Review
AI suggestions are exactly that—suggestions. You can edit fields before save, which limits incorrect data ever reaching your history.
Sync
Cloud sync keeps devices aligned. Encrypted transport reduces exposure on the wire; server-side storage protections are described in our Privacy Policy.
Export
CSV exports are generated for you. Treat downloaded files like any financial export: store them securely and share only with people you trust.
Deeper detail on the principles behind Receni. When anything here conflicts with a legal document, the legal document wins—but we work hard to keep them aligned.
Features ship with threat modeling appropriate to the sensitivity of receipts and totals. When trade-offs appear, we bias toward fewer surprises for users—not toward shipping faster at the cost of clarity or control.
Receni focuses on what is needed to scan, categorize, budget, and sync. We avoid collecting unrelated profile fields, and we steer marketing analytics toward aggregated patterns rather than invasive tracking.
Connections between the mobile apps and our APIs use TLS. That protects payloads—including receipt images and parsed fields—while they move across networks you do not control, such as café Wi‑Fi.
Sign-in and session handling follow common industry practices for consumer finance-style apps. Rotate credentials if you suspect compromise, and use device passcodes or biometrics for an extra local barrier.
We monitor service health and abuse signals. If you discover a vulnerability or suspicious behavior tied to Receni, contact us at support@receni.com with enough detail to reproduce—we treat credible reports seriously.
This page is a plain-language overview. For retention windows, cookies, international transfers, subprocessors, and your statutory rights, rely on the Privacy Policy and Terms of Service linked below.
Policies & your controls
Legal text is not exciting—but it is how we hold ourselves accountable. Pair it with in-product controls when you want a fresh start.