Privacy Policy

1. This website

This static website has no forms, login, analytics, advertising, tracking scripts, embedded media or browser-storage features. Its own files do not set cookies. It does not receive the private application's receipts, financial records or Google OAuth tokens.

The hosting provider, Cloudflare, processes website requests, including information such as IP addresses and request headers, to deliver and protect the site. Provider-managed operational logging and security controls are separate from these static pages. See Cloudflare's Privacy Policy. We do not claim that visiting a hosted website involves no technical data processing.

2. Google authorization and permissions

The OAuth application is named SALLY Claims Read Only. Two separate connections serve different purposes. A connection's name does not limit the permissions Google actually grants.

Reader connection

The implemented Reader lists configured Drive folders, reads file metadata and downloads original receipt files for local review. Its current configured and granted permissions include:

• drive.readonlyRead and download Drive files.
• spreadsheets.readonlyRead Google Sheets spreadsheets; present in the grant, although the inspected receipt-reading path does not use Sheets.
• drive.metadataRead and manage Drive file metadata; this is write-capable permission even though the inspected Reader uses read operations.
• drive.fileAccess files created by or specifically authorized for the application.

The broad Drive permissions are not restricted by Google to the receipt folders. The implemented Reader applies folder and operation restrictions locally. The current permission grant is therefore broader than the Reader's intended read-only behavior.

Organizer connection

The separate Organizer has drive permission, which permits viewing and managing Drive files. The inspected Organizer uses approved folder configuration to find or create folders, maintain folder naming and move receipts into year/month folders. It is not read-only. The inspected path does not delete receipt contents, but its Google permission grant is broader than those individual operations.

Google handles sign-in and consent. SALLY's local workflow service stores OAuth credentials and tokens encrypted in its credential store and uses refresh tokens for continued access while valid. The public website has no access to that store. This is not a guarantee that every local record or backup is encrypted.

3. Data accessed and processing

Receipt processing can include original images or PDFs, file identifiers, names, folder relationships, checksums and receipt details such as merchant, date, amount, currency and expense category. Local review records may also contain owner-entered explanations, assignments and approval history.

The inspected receipt extraction uses Windows OCR locally to create suggested fields. Suggestions require review; they are not proof of a correct financial transaction. No external AI extraction service was found in the inspected receipt path. This statement does not describe every possible AI feature or a future integration.

Google processes Drive API requests. The receipt workflows run through the owner's local automation service and local SALLY modules. Cash Advance's separate Drive intake is implemented but not activated; if authorized, it downloads assigned evidence into a review queue and requires manual review before posting.

4. Use, sharing and Google Limited Use

Google user data is used for the owner's visible receipt, expense-review, organization and evidence-export features. The inspected integration has no advertising, data-sale or external AI-training step. Google user data is not used to develop, improve or train generalized AI or machine-learning models.

SALLY's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google data is not sold or transferred for advertising, data brokerage or creditworthiness decisions. Human review in the described workflow is performed by the owner.

The owner can export reports and original evidence as PDF, spreadsheet and ZIP files. If the owner shares those files or places them in a synchronized or backed-up location, those copies are subject to the chosen recipients' and providers' handling. These exports are not published by this website. A new use or transfer beyond the disclosed integration must be assessed, disclosed and authorized before it is enabled.

5. Storage, retention and deletion

Original Drive files remain in Google Drive; Organizer operations can change their folder location. Downloaded evidence, extracted text, financial records, intake journals, hashes, approval history and exported packages are stored locally. Existing workflows may also retain execution information or local logs, depending on their settings. Copies may remain in owner-managed backups or synchronized folders.

No uniform automatic deletion period is established for these records. Evidence and previously exported Cash Advance bundles are deliberately retained for traceability; historical bundles are not overwritten by revisions. The owner controls retention and deletion through the relevant application, file, backup and Google account controls. Deleting one copy does not remove other copies.

6. Revoking access and connection health

The owner can review or remove SALLY's Google access in Google Account third-party connections. Removing the application's access may affect both connections in the same Google project. Access can also expire or be revoked by Google.

Revocation prevents future authorized API access; it does not automatically erase receipts already downloaded, financial records, exports, workflow logs or backups. Reader and Organizer health are checked separately. A successful token refresh is not treated as proof that receipt processing is operational.

7. Questions and changes

For questions about the private integration, use the support contact displayed in its Google OAuth consent information. This site does not provide a public account or data-request form.

This policy must be reviewed when permissions, processing or sharing change. Additional consent will be obtained where required before using Google data in a newly disclosed way.