Privacy Policy
Effective date: November 7, 2026 · Version 2.2 · Leer en español
Optional-feature update. This edition adds optional email transaction processing. Mail access remains disabled until provider setup, approvals and the required privacy notices are complete. Existing mailbox access is never inferred from this update, signup or Google sign-in. We do not change existing plan prices or automatically authorize any new processing.
In short
- The controller of your data is VstreamX Studio Inc. (Canada). You reach us at admin@xplitx.com.
- We process what you need to use XplitX: your account, what you record (expenses, payments, budgets, receipt photos), your plan, and the technical logs needed to run and protect the service.
- We do not sell your data, we show no advertising, and we use no analytics tools or advertising trackers in the app or on the website.
- AI features, Google Calendar sync and summary links are optional: they are used only when you decide to.
- Your data lives on Google Cloud (Firebase) in the United States. Payments are processed by Stripe (web) or Google Play (Android app).
- You can export your data and delete your account from Settings → Privacy & data. We answer any request within 30 days at most.
1. Who is responsible
The controller of your personal data is VstreamX Studio Inc., a company incorporated in Canada, with its office at Office B - 1043 Rosser Ave, Brandon MB R7A 0L5, Canada ("VstreamX", "we"). The individual accountable for this policy and for compliance with Canada's privacy law (PIPEDA) is Ricardo Javier Sandoval Sandoval, Chief Financial Officer of VstreamX Studio Inc. Any question or request about your data reaches admin@xplitx.com.
2. What this policy covers
This policy covers the web application (app.xplitx.com), the Android application
distributed on Google Play (com.xplitx.app), the website xplitx.com, the emails
we send to operate the service and the support we give you by email. The Android app and the web are the same service and
the same account; section 9 describes what happens only on Android. It is part of the
Terms of Service.
3. Which data we process
Optional email connections also process the categories specified in section 8A, including mailbox identity, connection credentials, message metadata, transaction text and your rules. They remain separate from ordinary sign-in data.
| Category | Examples | Where it comes from |
|---|---|---|
| Account | Name, email address, password (Firebase Authentication stores it as an irreversible digest; we never see it), language, email-verification status, user id. If you sign in with Google: the basic identity data you authorise (name, email, photo). We do not receive your Google password. | You; Google if you choose to sign in with Google. |
| What you record | Expenses, income, recorded payments, categories, notes, budgets, goals, calendar due dates, rules, templates, payment accounts you name (without credentials), receipt photos and PDFs, "guest" participants you create, and the visibility you give each record (personal, group or specific people), verified on the server. | You and the other members of your groups. |
| Groups and invitations | Members, roles, space name, invitations sent and received (invitee's email, status, expiry). | You and whoever administers the group. |
| Plan and payments | Active plan, subscription state, Stripe customer and subscription identifiers, or the Google Play product, state and purchase token. Never your card number. | Stripe or Google Play. |
| Use of paid features | Monthly counters of receipt readings and AI credits, to apply your plan's allowances. | Generated by the service. |
| Google Calendar (optional) | Encrypted authorisation, account and calendar identifiers, preferences and references to events sent (section 8). | Google, only if you connect sync. |
| Summary links (optional) | Link metadata, a digest of the secret and abuse counters with pseudonymised IP addresses (section 6). | You and whoever opens the link. |
| Technical and security | Server access and error logs (date, action, user id, IP address, user agent), App Check attestation tokens (reCAPTCHA Enterprise on the web, Play Integrity on Android), per-user and per-IP usage limits, an audit log of actions on your account and of staff access. | Generated when you use the service. |
| Support | What you write to admin@xplitx.com and what we need to answer you. | You. |
We do not collect location data, contacts, other installed apps, advertising identifiers or biometric data. We do not knowingly process special categories of data (health, religion, sexual orientation, etc.); if you type them into a note or an expense title, they are treated like any other record of yours, and we ask you not to do so with other people's data.
4. What we use it for and on what basis
Automatic email transaction identification and preparation of private suggestions use your separate, revocable email-feature authorization. Sending minimized text to OpenAI additionally requires your AI-assistance choice (section 8A). Neither permission is inferred from acceptance of this policy.
| Purpose | Which data | Basis |
|---|---|---|
| Providing the service: creating your account, splitting expenses, working out balances, reports, budgets, calendar, exports | Account, what you record, groups | Performance of the contract (the Terms) |
| Managing your plan and charges | Plan and payments, use of paid features | Performance of the contract; legal obligations (tax and accounting) |
| Sending you operational emails: verification, password reset, invitations, security notices and notices of changes to the service | Email, name, the event that triggers it | Performance of the contract; legitimate interest in keeping you informed |
| Sending you reminders and digests you turn on (pending debts, daily digest of overdue items) | Email, preferences, balances | Your consent (Settings → Notifications); you can turn them off at any time |
| AI features you start (section 5) | The receipt photo, your question with financial aggregates, or optional short voice dictation | Your consent, action by action |
| Syncing Google Calendar (section 8) | Dates and generic titles of due dates | Your consent, revocable |
| Keeping the service secure: attesting the app, limiting abuse, detecting unauthorised access, auditing actions | Technical and security | Legitimate interest in protecting users and the service; legal obligations |
| Handling your requests and complaints | Support, account | Performance of the contract; legal obligations |
| Improving XplitX | Aggregated or anonymised usage statistics (never your identifiable content) | Legitimate interest |
| Complying with the law and defending rights | Whatever the specific obligation requires | Legal obligation; legitimate interest |
What we do not do: we do not sell or rent your data; we do not share it with advertisers; we show no advertising; we make no automated decisions with legal effects about you; we do not use your data to train AI models and we do not allow our providers to do so.
5. Artificial-intelligence features
- Receipt reading. When you choose to scan a receipt, the app compresses the image and our server sends it to OpenAI (a vision model) to extract the merchant, date, totals, taxes and items. The image you keep as an attachment stays on your expense; the copy sent to OpenAI is used only for that reading. If OpenAI does not respond, the app can read the receipt locally on your device (Tesseract), without sending the image to anyone.
- Rotceh assistant. Instant mode prepares basic answers on your device. In AI mode, sending a message sends your question and up to four short recent conversation turns to OpenAI to understand your request. A separate model receives the interpreted concern and server-calculated personal financial aggregates from the spaces you explicitly select. It does not receive saved individual records, receipts, merchant/participant names or account identifiers. Drafts contain only details you supplied; you choose the space and review the normal entry form before pressing Save. Rotceh cannot execute payments, invitations or administrative actions. Legacy AI reviews may use Google Gemini as fallback. Conversations are scoped to the signed-in user and space in browser-tab session storage; wider-space conversation is memory-only. Both clear on sign-out.
- Voice dictation (web and Android 1.3 or later). Only after you start recording and finish dictation, our server sends up to two minutes of audio to OpenAI for transcription. You can review and edit the resulting text before sending it to Rotceh. XplitX handles raw audio in service memory and does not save it to databases, object storage or application logs; provider retention under its API policies still applies. Cancelling before upload discards the recording. Transcription and an AI answer or draft each use a separate plan credit on success. Voice duration is measured separately from text-model tokens. Android 1.3 or later requests optional microphone permission only when you choose dictation; older packages do not support this feature.
- Providers. We use OpenAI's and Google's business (API) services, not their consumer products. Under those terms, what we send is not used to train their models; the providers may keep requests for a limited period to detect abuse and for security, under their policies. The access keys live on our server; your device never talks directly to OpenAI or Gemini.
- Control. No AI feature runs without an action from you. Receipt readings and AI credits are limited by your plan, and you can stop using them without losing anything.
6. Expense summaries shared by link
An expense author may explicitly publish a limited summary after previewing it. It contains the title, date, currency, total, participant count and optionally one unidentified share. Review the title: it may contain personal details you entered. Receipts, items, participant identity fields, emails, wallets and other expenses are excluded. Anyone holding the link can view and forward it. The link does not verify identity or permit editing, payment recording or group membership.
Authors choose 24 hours or 7 days and may revoke a link. Replacement, expense edits or deletion, and removal of author access invalidate it. We retain verification metadata and a secret hash rather than the original secret. Expired metadata is removed by a daily batch job. Abuse counters use pseudonymized IP addresses and expire by window. Reading a summary does not call an AI provider. Your authenticated privacy export includes your link metadata without reusable link secrets.
7. QR invitations with reserved shares
This is separate from a view-only summary. A group owner who authored the expense may consent to an invitation QR. Before sign-in it shows title, date, currency, total and people count, plus the inviter's chosen display name and group/circle name as invitation context. It does not publish the participant roster, receipts, wallets or notes. Verified signed-in people may choose a fixed share and explicitly join the group and, when specified, its expense circle. No payment is recorded. Existing participants open their expense without taking another share. Package group/member limits still apply.
The owner may revoke or replace the 24-hour or 7-day invitation. Revocation stops future claims without removing people who already joined. Financial, people, title, date or visibility changes invalidate it; claims and payments preserve agreed amounts. We store a secret hash and invitation/claim metadata, not the original link. Draft reservation metadata expires after 24 hours and is cleaned in daily batches, and may remain longer if cleanup is backlogged. Guests referenced by saved expenses and their financial history are retained with those records. Guest identity records, including inactive ones, may remain for reconciliation; deleting temporary reservation metadata does not erase them. Authenticated export and deletion include the issuer's temporary metadata. Opening/sharing a QR makes no AI call; receipt scanning uses the package's AI limits.
8. Google account and optional calendar
Google sign-in and Calendar authorization are separate, optional functions. When you connect automatic sync, Google authorizes XplitX to create/update a separate XplitX calendar even when the app is closed. Your renewable authorization is encrypted on the server; the encryption key is held in Secret Manager and restricted to the sync service. We retain Google/calendar IDs, preferences, sync status and selected-event references. Google tokens are not stored in browser storage. Google may require renewed consent.
New events created after connection and later changes sync automatically. Earlier history is not silently copied; select events from a displayed period to send/update them manually. Selected events also follow later XplitX edits while sync is active. Planned payments are projected up to one year ahead without creating financial transactions. Only all-day dates and generic titles are sent by default; sending written titles requires a separate choice. Amounts, notes, receipts and participant details are excluded. We do not read Gmail or other calendars, or import Google edits. Earlier manual links require reconnecting to enable automatic sync.
While connected, XplitX updates its copies and removes copies of deleted or no-longer-visible events. Pause stops background updates but still allows manual selection. Disconnect, departure and account deletion stop access and delete stored authorization; existing Google copies remain under your Google controls. Revoke permission in your Google account and delete copies in Google Calendar when you choose. You can manage access in your Google account. Private deadlines and connection metadata join your data export; reusable tokens, like other credentials, are excluded. After account deletion, a revocation marker without credentials is retained for up to seven days to prevent pending operations restoring the connection. Google API data is used only for these authorized functions, without advertising, sale or AI training, in accordance with Google's API Services User Data Policy and its Limited Use requirements.
8A. Optional email transaction import, rules and AI assistance
Your choice. Creating an account or acknowledging this policy does not connect a mailbox. Before connection we explain the data, purposes, background access, recipients, limits and controls. You separately authorize automatic transaction-email processing and complete Gmail or Microsoft authorization. You may separately enable or decline AI assistance. Declining either optional choice does not prevent ordinary account creation or manual expense entry.
Access and data. We request Gmail read-only permission or Microsoft Graph delegated Mail.Read, with the authorization needed to maintain the connection in the background. These permissions can technically allow mailbox-wide reading, including message bodies; bank and folder filters are application restrictions, not provider-enforced boundaries on that permission. XplitX checks sender, subject, dates, message identifiers and available authentication results to find likely financial notifications, and retrieves relevant message text when needed. We do not request permission through this feature to send, edit or delete mail or access contacts. We do not fetch email attachments, remote images or links in the first release.
We process the mailbox identity, encrypted authorization credentials, sync checkpoints, your source and categorization rules, transaction description, amount, currency, transaction date and type, relevant transaction reference and, where present, masked account or card details. We avoid retaining unrelated message content and remove credentials, verification codes and unnecessary identifiers from text before optional AI processing. Incidental unrelated information may be encountered while identifying relevant messages; it is not used for an unrelated purpose. Do not connect a mailbox you are not authorized to use.
Purposes and control. We use this information to identify transactions, avoid duplicates, apply your rules, prepare private suggestions and operate and protect the connection. My Finances exposes the review queue, connection status, last successful check, usage and Manage import rules. Settings provides the full controls for the same underlying preferences. A rule may suggest a category, tags, wallet or group, or exclude a source; it never expands access permission, changes your consent, saves an expense or publishes it. Group destinations and access are rechecked when you approve.
Optional AI and recipients. Familiar formats use ordinary extraction rules. Only if you separately enable AI assistance may relevant, minimized transaction text be sent to OpenAI's business API for extraction of an unfamiliar format. Google Cloud/Firebase hosts the processing and suggestions; Google and Microsoft operate their mailbox and authorization services under their own terms. We do not route imported email to Gemini or other AI providers under this consent. A material change of recipient or purpose requiring new consent will be presented first. Data processed for this feature may be transferred to the United States and Canada; Microsoft or Google mailbox processing also depends on your provider's account terms and regions.
We do not sell email-derived data, use it for advertising or creditworthiness decisions, or use or disclose it to develop, train or improve general-purpose or non-personalized AI/ML models. We do not build a staff training or evaluation corpus from production mail. Separately volunteered, redacted test samples require distinct, specific permission and provider-policy review and cannot be used for general-purpose model training. We disable optional AI-provider data sharing and request no stored application response state. This is not a zero-retention promise: OpenAI's ordinary API abuse-monitoring logs may retain content for up to 30 days, with longer retention in the legal or security circumstances described in its API data controls. Any approved stricter arrangement will be described accurately before use.
Human access and sharing. Your mailbox, source evidence, pending suggestions and import rules are private to you. We restrict human access to the limited cases allowed by applicable law and provider policies, including documented permission to inspect a specific message for support, necessary security investigations, or legal obligations. Staff do not routinely read inboxes to maintain rules. On explicit approval, only the financial fields and audience you select enter a group record; the original email, source evidence and credentials stay private. Existing access rules govern that approved record.
Retention for this feature. Full message bodies are processed transiently in memory rather than stored by XplitX. Unapproved suggestions and any minimized source excerpt expire after 30 days; dismissing a suggestion deletes its content. Content-free duplicate keys are kept for at most 90 days while connected. Authorization is retained only while connected; disconnection deletes it and pending imported content. A credential-free revocation marker may remain for up to seven days to stop in-flight work restoring access. Consent and withdrawal records are kept for the life of your account and removed on final account erasure unless a specific legal obligation requires limited retention. Approved expense fields follow the ordinary financial-record retention in section 14. Backup remnants follow the disclosed backup cycle; erasure markers must be reapplied before restoration. AI-provider retention is separate as described above.
Withdrawal, export and deletion. You can pause collection, disable AI assistance, edit or disable rules, disconnect a mailbox, delete pending imported data and export your suggestions, rules, connection metadata and consent history without credentials. Disconnecting stops new processing and cancels queued work; revoke access in your Google or Microsoft account as well if desired. Withdrawing AI permission prevents subsequent AI submissions but cannot undo a completed transmission. Disconnection leaves approved expenses in place unless you separately delete them under the normal personal/shared-record rules. Account erasure includes this connection and its private imported data, subject only to disclosed legal exceptions and the shared-record rules. For this optional feature, the separate authorization here governs; merely using XplitX is not authorization to access email.
Our use and transfer of Google Workspace data follow Google's user-data policy and its Limited Use requirements. These additional restrictions also apply to data derived from your messages. Contact admin@xplitx.com for rights requests or concerns.
9. The Android app
The Android app is the same web application inside a native container. It processes the same data, under the same rules, and adds only the following.
- Permissions. The app declares only Internet (essential), network state (to know whether there is a connection), camera and, from version 1.3, microphone and audio settings for optional dictation. Camera and microphone access are requested only when you choose the corresponding capture action. If you deny either, you can still enter information manually. The app does not ask for location, contacts, SMS, calls, notifications or general access to your files. When you save or share an export or a receipt, the file is handed to the Android picker you choose; the app does not read other files on the device.
- Device integrity (Play Integrity). So that everyone's accounts stay protected, before talking to our servers the app asks Google Play for an integrity verdict: whether it is a genuine Google Play installation on a certified device. For that, Google processes signals from your device and your installation under the Google Privacy Policy; we receive only a short-lived token saying whether the check passed. We obtain no permanent identifiers of your device.
- Data on your device. The app keeps in its private storage your session (a renewable access token) and a local copy of the data you have viewed, to open quickly and to let you look at it offline. That storage belongs to the app alone: Android does not share it with other applications. Android's automatic backup is disabled for XplitX, so neither your session nor your data is uploaded to Google Drive. Signing out ends the session on the server and clears the conversation with Rotceh; uninstalling the app removes the whole local copy.
- No trackers. The app includes no advertising or analytics SDK, sends no push notifications and collects no advertising identifiers. Technical errors are logged on our server as on the web (section 3).
- Google sign-in. Works the same as on the web; the authorisation completes in a secure tab of the device's browser.
- Purchases. Subscriptions inside the app go through Google Play (section 10).
- Google Play and Google. Google knows that you installed the app, your version and your purchases, under its own privacy policy. We do not receive your Play identity or your payment data from Google.
- Deleting the account from the app. Settings → Privacy & data → Delete my account (section 17).
10. Purchases through Google Play
- When you buy a plan in the Android app, the payment is processed by Google Play. Google is the merchant: it receives your payment details, issues the receipt and handles refunds and cancellations. We never receive your card number.
- So that the purchase can be linked to your account without revealing your identity to Google, the app sends Google an obfuscated identifier: a cryptographic digest (SHA-256) of your user id, which Google cannot reverse. Our server compares it with the one Google recorded to confirm the purchase is yours.
- We store on your profile: the product bought, the base plan, the subscription state, the purchase token (and the previous plan's token, if you changed), the date of the last event and that obfuscated identifier. Google sends us notifications when your subscription renews, is cancelled, enters a grace period or expires, and our server asks Google for the state with its own credentials. Google's full responses are not stored in our database.
- Google Play applies its own privacy policy to your purchase history and your payment data.
11. Payments through Stripe (web)
If you buy a plan from the web application, Stripe processes the payment and stores your payment method under its own privacy policy. We store your Stripe customer and subscription identifiers, the plan, its state and the period dates; Stripe notifies us of changes (renewal, non-payment, cancellation) through signed messages. You can see your invoices and change your payment method from the Stripe portal in Settings → Plan.
12. Providers that process data for us
For optional email import, Gmail API and Microsoft Graph provide the selected mailbox connection under their own terms; Google Cloud/Firebase processes the suggestions; OpenAI processes minimized transaction text only with the separate AI choice (section 8A). Microsoft is an additional recipient for Outlook connections. Its processing locations and terms must be checked for the account concerned; no Canadian-only storage promise is made.
We do not share your data with third parties except with these providers, which process it on our behalf and under contract, and except where a law or a competent authority obliges us (in which case we will tell you if the law allows it).
| Provider | What for | Where |
|---|---|---|
| Google Cloud / Firebase (Google LLC) | Database (Firestore), authentication, file storage (Cloud Storage), server functions, technical logs, app attestation (App Check with reCAPTCHA Enterprise and Play Integrity), web hosting. | United States (us-central1) |
| Google Workspace (Gmail) | Sending the service's operational emails. | United States |
| Google Play (Google LLC) | Distribution of the Android app, in-app subscription billing, subscription-state notifications. | United States and the country of your Google account |
| Google Calendar API | Only if you connect sync (section 8). | United States |
| OpenAI, L.L.C. | Receipt reading and the Rotceh assistant, only when you use them (section 5). | United States |
| Google Gemini API | Fallback for the Rotceh assistant if OpenAI fails (section 5). | United States |
| Stripe, Inc. | Payments for subscriptions bought on the web (section 11). | United States |
| Google Fonts | Only on the website xplitx.com: your browser downloads the typeface from Google's servers, which receive your IP address. The application does not use Google Fonts. | United States |
If we add a provider that processes personal data (for example, an error-monitoring service), we will add it to this table before enabling it.
13. Where your data is processed
Email access and the optional email-to-AI transfer require the specific choices in section 8A. The general description of international processing in this section does not itself grant those permissions.
We operate from Canada and host the data on Google Cloud in the United States. Our providers also process data in the United States. If you live in another country (for example, in Latin America), your data is transferred to the United States and to Canada to provide the service to you; by using XplitX you consent to that transfer. The laws of those countries may allow their authorities to access the data in the cases they establish. We protect transfers with contracts with each provider and with the measures in section 15.
14. How long we keep it
For email-import data, use the specific retention and withdrawal rules in section 8A. Those rules do not extend full-message retention to the lifetime of the account or the general audit-log period.
| Data | Period |
|---|---|
| Account, personal spaces, user files, preferences | As long as your account exists. Deleted when you delete the account (section 17). |
| Shared expenses and their receipts in groups with other members | As long as the group exists, even if you delete your account: they back the other people's balances. They disappear when the group is deleted or when the last member leaves. |
| Plan, subscription and charge records | For the life of the subscription and afterwards for as long as Canadian tax and accounting obligations require (up to 7 years). |
| Conversation with Rotceh | Only in your session's memory; cleared when you sign out. |
| Image sent to OpenAI to read a receipt | We keep it only as the attachment you decide to keep; OpenAI retains it under its API policy (a limited period for abuse and security). |
| Summary links | 24 hours or 7 days as you choose; expired metadata is removed by a daily job. Abuse counters expire by window. |
| Google Calendar authorisation | Until you disconnect or delete the account; afterwards, a revocation marker without credentials for up to 7 days. |
| Invitations | An invitation can no longer be used once it is accepted, expires or is cancelled; we keep the record that it existed (invitee email, status, dates). |
| Server technical logs | Operational logs are removed in the provider's normal cycle (weeks). The audit records of actions on your account and of staff access are kept, for now, without a fixed period, as evidence of what was done and who did it; they are used for nothing else. |
| Support | Up to 24 months after the request is closed, unless a complaint is open. |
| Backups | System backups are overwritten in the ordinary cycle; a deleted item may persist in them for a limited time and is not restored to production except to recover the service. |
15. How we protect it
- Encryption in transit (TLS) and at rest on Google Cloud. Google Calendar authorisations are additionally encrypted with our own key kept in Secret Manager. We do not offer end-to-end encryption: we need to read your records to work out balances.
- Access rules by user, role and record visibility, enforced on the server on every read and write.
- App attestation (App Check): only the genuine web application and the Google Play app on a certified device can talk to our servers.
- Provider keys (OpenAI, Gemini, Stripe, Google) live on the server, never on your device. Messages from Stripe and Google Play are verified before being applied.
- Automatic sign-out after 15 minutes without activity; per-user and per-IP usage limits against abuse; an audit log of actions on accounts and of staff access.
- Android backup disabled for the app (section 9).
- If a security breach creates a real risk of significant harm to you, we will notify you as soon as possible and, as PIPEDA requires, report it to the Office of the Privacy Commissioner of Canada and keep a record of it. If you believe your data was exposed, write to admin@xplitx.com.
16. Your rights
Email controls include separate withdrawal of background access and AI assistance, deletion of pending imported content and export of your rules, suggestions and consent history (section 8A). These rights do not require a paid subscription.
Wherever you live, you can:
- Access and export: Settings → Privacy & data → Export my data downloads a JSON package with your profile, your budgets, your memberships, the entries related to you and the metadata of your links and connections (without reusable credentials).
- Correct: edit your profile and your records inside the app. What another person recorded is corrected by that person or by whoever administers the group.
- Delete: section 17.
- Withdraw consent: disconnect Google Calendar, turn off reminders in Settings → Notifications, stop using the AI features or revoke a summary link. Withdrawing it does not affect what was processed before.
- Object and restrict: if you believe processing based on our legitimate interest should not apply to you, tell us and we will review it.
- Portability: the export is a structured, machine-readable format.
- Know: ask which data of yours we hold, with whom we share it and why.
For anything the app does not cover, write to admin@xplitx.com from your account's email address (or tell us how to verify your identity). We answer within 30 days at most; if we needed longer because of the request's complexity, we would tell you within that period, with the reason. Handling a request is free unless it is manifestly repetitive. We will not treat you differently for exercising your rights. If a person appears in a member's records without having an account (for example, a guest participant), they can exercise these same rights by writing to us.
17. Deleting your account
Account erasure also stops email jobs and removes mailbox credentials, private import rules, pending suggestions, private source evidence and feature consent records, subject to the specific limited exceptions in section 8A. Approved shared entries follow the shared-record rules.
From the app (web or Android): sign in → Settings → Privacy & data → Delete my account → type the confirmation word. It is immediate and irreversible. It removes your sign-in identity, your profile, your membership of groups, your personal spaces (expenses, budgets, goals, calendar, rules), your user files, your preferences, your usage counters, your Google Calendar authorisation and your summary links.
What is kept and why: shared expenses and their receipt photos in groups that have other members, because they back those people's balances (your name stops being linked to an active account); the audit records and the charge records for the periods in section 14; and a marker without credentials for up to 7 days that stops a pending operation from restoring the Google Calendar connection.
If you own a group with other members, the app will ask you to transfer the group first, so the others do not lose their access. If you cannot, write to admin@xplitx.com and we will resolve it with you within 30 days at most.
Without access to the app: write to admin@xplitx.com from your account's email address with the subject "Delete my account". We will verify it is you and delete it within 30 days at most.
Deleting the account does not cancel a subscription: cancel it first in Settings → Plan (Stripe) or in Google Play → Subscriptions. Uninstalling the Android app does not delete the account either.
18. Cookies and storage on your device
- Application (web and Android). We use the browser's or the container's storage for the essentials: keeping you signed in (Firebase Authentication), a local copy of the data you have viewed to open quickly and look at it offline (Firestore cache), and your preferences (theme, language, sidebar, recent searches, dismissed notices, active space). reCAPTCHA Enterprise, which protects the web application, may set its own technical cookies under Google's policy. There are no advertising or analytics cookies.
- Website xplitx.com. It uses no cookies and no analytics. It loads its typeface from Google Fonts (section 12).
- You can clear the storage from your browser or by uninstalling the app; next time you will have to sign in again.
19. Minors
XplitX is for people aged 18 and over. We do not knowingly collect data from minors. If you believe a minor created an account, write to us and we will delete it.
20. Access by our staff
Email-derived data has the additional human-access restrictions in section 8A. Ordinary staff access for general administration does not authorize reading messages or pending transaction suggestions.
Only authorised staff can access user data, and only for the support you ask for, security, operating the service or legal compliance. Every staff access is recorded in an audit log. Support access does not widen the visibility you gave your records towards other members.
21. Changes to this policy
If we change this policy materially (new data, new purposes, new providers with access to personal data, new periods), we will tell you inside the app and by email at least 15 days before the change takes effect. The effective date above identifies the version in force; earlier versions can be requested by email.
22. Contact and complaints
VstreamX Studio Inc. · Office B - 1043 Rosser Ave, Brandon MB R7A 0L5, Canada · admin@xplitx.com. Accountable individual: Ricardo Javier Sandoval Sandoval, Chief Financial Officer.
If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or to the data-protection authority of your country of residence.