Privacy policy
Last updated: 25 October 2026
What this policy covers
Weceipt is operated by Horizona Limited. This policy covers the Weceipt website, iOS and Android apps, and connected receipt-management services. Gmail connections, Google Sheets and Drive exports, and subscription management are provided through the web workspace. Contact support@weceipt.io about privacy, access or deletion requests.
Information we collect
Account information includes your email address, account identifier and any name or profile information supplied through sign-in. We store the receipt images and PDFs you upload or import, extracted expense details, your corrections, notes, groups, categories, export templates and preferences. Our hosting and authentication providers also process technical information such as IP addresses, request details and security logs to operate and protect the service.
Receipt records can include merchant, date, currency, totals, tax, description, printed receipt or invoice number, custom fields and original or cropped images. We also store team membership and invitations, subscription and usage records, and the version and time of recorded AI-scanning consent. Only provide receipt or spreadsheet information that you are authorised to use.
How we use information
We use this information to authenticate you, save and synchronise your workspace, recognise receipt details, calculate currency conversions, generate downloads, provide support and prevent abuse. Weceipt does not sell your personal information or use receipt or Gmail information for advertising.
Connecting Gmail
Gmail access is optional and separate from signing in with Google. If you connect an inbox, Weceipt requests Gmail read-only permission. The API permission can read your mailbox; our importer searches for messages matching your import settings and reads message details and supported PDF or image attachments to find receipts. We store the connected email address, encrypted refresh credentials, import checkpoints, message and attachment identifiers, file fingerprints and import status. These records support background importing and prevent duplicates. Selected attachments are stored as original files and sent to Google Gemini to extract expenses. We do not use Gmail access to send, modify or delete emails. Email-body-only receipts are not currently imported.
Weceipt’s use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. Google API data is used only for receipt management and export features requested by users, not for advertising or sale.
You can pause imports, change the mailbox search and import date, or disconnect a mailbox. Disconnecting removes its saved credentials and import records from Weceipt and stops future imports; receipts already imported remain in your workspace. Revoke Google permissions separately in your Google Account if you want to withdraw the Google authorisation itself.
Writing to an existing Google Sheet
If you choose this feature, Weceipt reads the spreadsheet and worksheet tab you select, including headings, existing cell values, formulas, formatting information, protections and export markers, to prepare a preview, insert new receipt rows and fill mapped cells in previously exported receipt rows. Replacing non-empty cells requires your confirmation. We use the same narrow drive.file permission and Google Picker to let you grant access to specific files. Manual mapping is processed in your browser. If you click Suggest with AI, worksheet headings and up to 100 representative sample rows and bounded row/summary formula examples (with each text cell limited to 160 characters) are sent through our server to Google Gemini to suggest column mappings and amount conventions. Previously exported Weceipt rows are excluded from those samples. If you choose Prepare rows with AI, we also send the selected receipts’ extracted fields (including merchant, date, totals, categories and notes), the payment context you enter and the chosen column rules to Gemini to prepare editable receipt-specific rows. Receipt images, inbox metadata and Google Drive access tokens are not included in this request. Payment context can be retained with a saved ledger setup. The proposed rows remain in your current browser session until you confirm sending them. These suggestions do not write to your spreadsheet; you review and apply them before previewing and sending rows. Suggestions may include fixed values observed in your sample, row formulas and optional shared totals changes. Formula replacements and shared totals require separate confirmations. Google Gemini processing terms described below also apply to these samples. Saved mappings, spreadsheet identifiers, tab identifiers and column settings are stored in your Weceipt account. We add project-visible metadata with receipt identifiers derived from a hash to exported spreadsheet rows to detect previous exports. A footer bookmark may also be added to follow totals as rows move. Existing Google Sheet copies or entries are not deleted when you remove a receipt or a saved mapping in Weceipt. You can revoke access in your Google Account.
Saving to Google Drive
Google Drive exports are optional and require a separate permission. We request the drive.file scope to create export folders and files, rather than access to your entire Drive. When you choose Save to Google Drive, selected receipt files, manifests and any included expense spreadsheet are uploaded directly from your browser to the Google account you authorise. A short-lived Drive access token is held in browser memory, not saved in our database or browser storage. Closing or reloading the page clears it. Exports create new copies; later edits or deletions in Weceipt do not update or remove those copies. You control and can delete exported files in Google Drive. This feature does not automatically synchronise files and does not send files to AI for recognition.
Teams and invitations
Team owners and admins can access and review receipts submitted to their team, including receipt files, extracted fields, notes and the submitting account identity. Employees can access their own submissions within that team, not other employees’ receipts. Joining a team does not grant the team access to your separate personal workspace or personal mailbox credentials.
To invite an employee, we store the invited email address, team and inviter identifiers, invitation-token hash, expiry and acceptance or revocation status. The invitation email includes the team name, inviter information and a join link or code. A valid invitation still requires the invitee to sign in with the matching verified email before joining. Team owners should invite only people they are authorised to contact.
Account and invitation emails
Resend delivers verification, password-reset and team-invitation emails for us. We send it the recipient email address and message content, including the necessary verification, reset or invitation link and relevant team or inviter details. Resend processes delivery and related technical records. Treat these links and codes as confidential. These are service emails, not permission to send marketing emails.
AI processing and service providers
Receipt images or PDFs, recognition instructions and relevant category labels are sent to Google Gemini for analysis. Before the native app first uploads a receipt for AI scanning, it asks for your consent; cancelling does not upload that photo for scanning. Production scanning and ledger AI features use a dedicated Weceipt Google Cloud project with active billing. Under Google’s Paid Services terms, prompts, receipt files and responses are not used to improve Google’s products or train its models. Google may retain requests temporarily for safety, abuse prevention and legal obligations. Weceipt does not use Google API data to train general-purpose AI models.
Firebase provides authentication. Google Cloud provides primary application hosting, the Cloud SQL database and private Cloud Storage receipt files. Our retained Cloudflare/Sites host can process requests when serving the fallback website and forwarding account requests to Google Cloud. Currency conversion requests sent to Frankfurter contain currencies and dates, not receipt images or merchant details. These providers may process data outside your country.
Advertising measurement
On our website, Google Ads measurement is optional and starts only after you choose Allow measurement. Google may receive ad click identifiers, browser and technical information, event times, and verified sign-up or first subscription payment events, including payment value and currency. We do not send receipt content, Gmail or Google Drive data, email addresses, or card details to Google Ads. We do not enable personalised advertising or enhanced conversions.
Choose No thanks to keep advertising measurement off. You can change or withdraw permission using Privacy choices on the website. Your choice is remembered for up to 180 days; optional campaign attribution is kept in your browser for up to 90 days. Google manages its own measurement records under its privacy policy. The native apps do not include this advertising tag.
We separately count new verified accounts and first paid subscriptions in our internal portal. These account-linked business records are checked by our server and Stripe. Campaign source is attached only with permission; otherwise it is unattributed. These records are removed when your account is deleted. Staff and test accounts are excluded from conversion totals.
Storage and security
Saved receipts and workspace data are stored online under your account. Access to receipt files requires authentication and account ownership checks. Gmail refresh credentials are encrypted before storage. Your browser also stores preferences, authentication state and, when needed, unsynchronised drafts. Clearing browser storage does not delete your cloud workspace. No online service can guarantee absolute security.
The mobile apps use your camera or system photo picker only when you choose to capture or select a receipt. The selected photo is copied into app storage as a recoverable draft; the upload copy is reoriented and stripped of EXIF metadata. This does not change the original in your photo library. Draft files and account session data can remain on the device between attempts; account deletion clears the current account’s local drafts on that device. Cloud deletion cannot erase downloaded copies or data on other offline devices.
We keep account-linked service operation records such as feature or request type, result status and processing time to diagnose failures, enforce allowances and protect the service. Authorised internal staff can use account, receipt, billing and operation information for support, maintenance and security. We do not use these records for advertising or cross-app tracking.
Retention, deletion and your choices
You can delete your account from Profile → Delete account in the app, or sign in at weceipt.io/delete-account without reinstalling the app. We require a recent sign-in and explicit confirmation. Deletion removes your personal workspace, receipts and original files, saved settings, account identity and stored connected-mail credentials, and revokes stored Gmail refresh access. An active Weceipt subscription is cancelled as part of deletion; this does not issue an automatic refund. If cleanup is interrupted, account access is blocked and the service retries automatically.
If you own a team, deleting your account also deletes that team and its workspace and removes employee access. If you submitted receipts to a team owned by someone else, those business records remain in that team’s workspace with your account attribution removed. Copies already exported to Google Drive, Google Sheets, downloaded files or another person’s records are not deleted by Weceipt. Deletion does not remove original messages from Gmail.
Current live account data is removed during cleanup. Routine database backups and file recovery copies currently rotate on approximately seven-day retention settings. Security and legal audit records may remain longer, including required cloud audit logs for up to 400 days. We retain a minimal hashed deletion marker to stop old sessions or delayed requests from recreating deleted account data. Stripe may retain invoices and transaction records required for financial or legal obligations. These retained records are not used to restore your account or for advertising.
Subscriptions and payments
Stripe processes subscription payments, billing details and invoices. Weceipt stores the Stripe customer and subscription identifiers, plan, payment status and usage allowance. Weceipt does not store full card numbers or card security codes. Manage payment methods, invoices and cancellation from Billing in your account.
Sharing and access
We share information with service providers as needed for the features described above and may disclose information when required by law or necessary to protect the service. Do not send receipt content to support unless you want it reviewed. Access by Weceipt personnel is limited to authorised support, maintenance, security or legal needs. Google’s separate AI processing terms are described above.
Access, corrections and privacy requests
You can review and correct receipt details, download your records, manage connected services and delete your account. For access, correction or other privacy rights requests that are not available in the product, contact support@weceipt.io using your account email. We may verify your identity before acting. Applicable rights and exceptions depend on your location and legal obligations. Weceipt is intended for adults aged 18 and over.
Changes and contact
We may update this policy as the service changes and will update the date on this page. Material changes to email access or AI processing will be explained before new consent is requested where applicable. Questions or requests: support@weceipt.io.