Soareth Agency Data Hub ← Back to website

Privacy and refund policy

Personal Expenses Studio/Tracker - SpendVista

Read how SpendVista handles sign-in and personal expense information, and how to request a refund for your purchase.

Effective date:
Where expense records are storedIn your own Google Sheet
How sign-in worksGoogle sign-in, with optional email and password sign-in
Publisher accessSoareth does not receive your expense records
01

About SpendVista

SpendVista is a personal expense tracker published by Soareth Agency Data Hub. Each installation is designed for one owner. The setup wizard creates the tracker’s Google Sheet and bound Apps Script project in the buyer’s own Google account.

02

Information SpendVista handles

Depending on how you use the app, it processes:

  • Account and sign-in information: your email address, selected username, Firebase user identifier, sign-in provider, and related account metadata supplied by Firebase Authentication.
  • Expense information: dates, categories, subcategories, descriptions, amounts, and currencies that you enter.
  • Tracker settings: your selected default currency and category names and subcategories.
  • Setup information: the owner email, username, and spreadsheet ID needed to connect your app copy to your Sheet.

If you choose email-and-password sign-in, Firebase Authentication handles the password. SpendVista does not put your password in the expense Sheet.

Firebase Authentication may also process technical information, such as IP address and browser or device details, to provide sign-in and help prevent abuse. See Firebase’s privacy information.

03

How information is used

SpendVista uses your information to authenticate the configured owner, save and organize expense entries, apply your tracker settings, and calculate the dashboard and reports. The Apps Script server checks the Firebase sign-in token and owner email before handling expense-data requests.

Expense entries are not sent to Firebase as a database and are not sent to a Soareth-hosted expense-record system. The app uses Firebase for authentication.

04

Where information is stored

  • Expense records and tracker settings are stored in the Google Sheet created in your Google Drive.
  • Setup metadata is kept in the bound Apps Script project or its script properties so the app can identify its owner and Sheet.
  • Sign-in account information is handled by the publisher’s Firebase Authentication project. Soareth can see account metadata available in that project, such as email address and sign-in provider. Soareth does not receive your expense rows or see your password.

Google Sheets and Apps Script provide the spreadsheet and app services. Google and Firebase process information under their own terms and privacy policies: Google Privacy Policy and Firebase Privacy and Security.

05

Permissions during installation

The desktop setup wizard asks you to authorize Google Sheets and Apps Script access to create and configure your SpendVista copy in your own Google account. It uses these Apps Script API scopes for two installation steps:

  • https://www.googleapis.com/auth/spreadsheets: creates and configures the Google Sheet used by your tracker.
  • https://www.googleapis.com/auth/drive.file: lets the installer access the Google Drive files it creates for your installation.
  • https://www.googleapis.com/auth/script.projects: creates the Sheet-bound Apps Script project and writes the SpendVista files and manifest into that project. Google requires this scope for project creation and content updates; a read-only project scope cannot perform these writes.
  • https://www.googleapis.com/auth/script.deployments: creates the web-app deployment for the project so you can open and use your installed tracker. Google requires this scope to create a deployment.

The installer uses these permissions during setup and targets the Apps Script project it creates for your installation. They are not used for routine expense entry after setup. The installer uses your Google authorization locally to make requests to Google APIs; it does not send your OAuth access token or the contents of your Sheet to Soareth.

06

Google user data sharing, transfer, and disclosure

During setup, the installer sends Google the requests needed to create your Google Sheet, create and populate its bound Apps Script project with SpendVista files, and create the app deployment in your account. Google processes and stores the Sheet, script project, and deployment to provide those Google services, under Google’s own privacy and security terms. The installer does not send your OAuth access token or expense records to Soareth.

SpendVista keeps expense entries and tracker settings in your Google Sheet. Soareth does not receive or sell those records or Google user data. We do not share Google user data with advertisers, data brokers, or information resellers, and we do not use it for advertising, credit or lending decisions, or to develop, improve, or train AI or machine-learning models.

Service providers: Firebase Authentication processes sign-in information such as your email address, Firebase user identifier, and sign-in provider so the app can authenticate you; it does not receive your expense rows. Paddle processes purchase, payment, and order-support information as the merchant of record; the installer does not provide Paddle with your Google API data or expense records. These providers process information under their own terms and privacy policies.

We may disclose information if required by applicable law or valid legal process, or when necessary to protect users, the service, or our legal rights. Any such disclosure is limited to what is required for that purpose.

07

Data protection and account security

  • Protected transmission: the installer communicates with Google APIs over HTTPS/TLS. Its Google authorization is used on your device to make the setup requests and is not sent to Soareth.
  • Account-controlled storage: your Sheet, bound script project, and deployment are held in your Google account and protected by Google’s service safeguards and account access controls. You control who can access or share those resources.
  • Owner checks: the app verifies the Firebase sign-in token and checks the owner email configured for that installation before handling expense-data requests.
  • Limited publisher access: Soareth does not keep a copy of your expense rows and cannot access your Sheet or script project unless you choose to share them.

Keep your Google account secure and review the Sheet’s sharing settings. You can revoke the installer’s Google access in your Google Account security settings. Revoking access does not automatically delete the Sheet, script project, deployment, or Firebase sign-in account.

08

Retention and deletion

Your expense records remain in your Sheet until you delete them in SpendVista, remove the rows from the Sheet, or delete the Sheet. Deleting the Sheet does not automatically delete your Firebase sign-in account.

To request deletion of your SpendVista Firebase sign-in account or ask a privacy question, contact Soareth at libuganda@gmail.com. Google and Firebase may retain technical or service records under their own policies.

09

Changes to this policy

This policy may be updated if SpendVista’s features, data handling, or refund terms change. The effective date at the top of this page will be revised when an update is published.

10

Refund policy

This policy covers the one-time digital purchase of SpendVista and its downloadable setup package when sold through Soareth Agency Data Hub. The checkout will identify the product and total price before you place your order.

30-day refund window: You may request a full refund within 30 calendar days of the transaction date. You may submit a request even if you have already downloaded or tried to install the product. This guarantee does not limit any additional or non-waivable rights available under the consumer-protection laws that apply to you.

How to request a refund: Use the support link in your Paddle receipt or visit Paddle Buyer Support and select the refund option for your transaction. Paddle may ask for the email address used at checkout or the transaction details to locate your order. Paddle processes the payment and refund request.

Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns.

Product or installation problem: If SpendVista has a material defect, is not as described, or a persistent technical issue prevents you from accessing the advertised features, contact Soareth at libuganda@gmail.com. We will make a reasonable effort to help resolve the issue. You may still submit a refund request through Paddle, and applicable legal rights are not conditional on contacting us first.

Refund processing and access: If Paddle approves a refund, it will generally be returned to the original payment method where possible; the time for the funds to appear depends on the payment provider and bank. After a refund, your permission to use SpendVista ends. Stop using the app and delete installer copies under your control. A refund does not automatically delete a Google Sheet, Apps Script project, or Firebase sign-in account in your own account; you remain in control of those resources and can delete them separately.

Refund requests are handled under this policy, Paddle’s buyer terms and refund procedures, and applicable law. If your local law provides greater protection or a different withdrawal period, those mandatory rights apply.