Publisher information

Privacy Policy

Last updated: 9 October 2026

This policy covers the original stage-start test and the current Farmer’s Helper development preview. The preview adds stock records, linked activities, corrections, plans and a dedicated Calendar display. Public installation and purchase are not yet available; Google has verified the central app’s branding and data access; Marketplace publication and product release checks remain pending.

Who we are

Smarter Spreadsheets is operated by Adam Hunter in Ontario, Canada. For privacy questions, support, or a request to access, correct or delete information held by us, email adamhunter9@gmail.com. Adam reads and responds to this mailbox.

Information the add-on uses

Farmer’s Helper uses a spreadsheet you create with the add-on or explicitly select through Google’s file picker. The development preview processes stock names, amounts and units, locations, receipt and activity dates, sources and relationships, notes, the name you enter as the person recording an action, assessments, plans and corrections. Workbook, record and operation identifiers connect these records and support recovery without repeating a saved operation.

Google Apps Script and the Sheets API process the records. Main business records remain in your Google spreadsheet and follow its sharing settings. The add-on does not copy its server source into your workbook, maintain a separate central farm-record database or send workbook records to this website.

Google permissions

The development preview uses access to specific files opened or created with the app (drive.file). Selecting a workbook in Google Picker grants access to that file; creating a workbook with the app grants access to the new file. The preview also uses access to the current spreadsheet (spreadsheets.currentonly) to identify the open workbook, inspect a blank starter and obtain its time zone. Direct Sheets API reads and writes use the specific-file permission. The dialog permission (script.container.ui) displays the integrated entry forms.

The original publisher test used broader spreadsheet access. The current central add-on uses the narrower permissions described here; the old all-spreadsheets permission is not requested. Google verified the central app’s branding and data access on 9 October 2026. This is not yet a public release; Marketplace publication remains pending. Review Google’s actual permission screen before consenting. No access to every Drive file, Gmail messages or contacts is requested by the development preview.

Marketplace configuration includes Google’s default email and profile permissions. The application does not look up your account email or profile, build a user directory or use these details for advertising.

Calendar display

The development preview implements a dedicated secondary display calendar, using calendar.app.created. This permission lets the app create secondary calendars and read, create, change and delete events on calendars it created. It does not grant access to your existing personal calendars. Native customer tests with Calendar granted have passed; the installed-customer test with Calendar alone declined remains incomplete.

When you connect and select an item for display, the app copies its planned action, stock name and date into an event, with a link to the source workbook. Private event metadata contains workbook/item identities and a revision marker. Connection and recovery identities are retained in user-specific Apps Script properties; farm notes are not stored there. Plans and completed work remain authoritative in the spreadsheet. Calendar edits do not change those product records.

The app creates private events without guests, invitations or reminders. Your own Google Calendar sharing choices can affect who can see them. Disconnect stops app refreshes and retains the calendar and existing events. Removing a displayed item removes its app event while preserving product history. Revoking access does not delete existing calendars or events; you can manage or delete them in Google Calendar.

Browser recovery storage

Entry forms retain unresolved drafts and recovery references in your browser’s local storage. These can include entered names, notes, amounts, dates, workbook/record identifiers and operation details. Current preview drafts expire 24 hours after their most recent draft save. The original stage-start test uses a seven-day expiry from creation. Expired entries are removed on the form’s next use; a closed browser cannot perform cleanup.

Confirmed outcomes and deliberate discard clear the corresponding recovery entry. Clearing browser storage also removes recovery information. None of these actions reverses a write already committed to the spreadsheet. Check the saved reference before entering the same operation again.

Diagnostics and retention

Application diagnostics are intended for technical operation and recovery, rather than collection of farm records. Google may process execution, exception, security and audit information. Uncaught exceptions can contain identifiers or error details; do not enter unnecessary sensitive personal information.

The publisher’s previously inspected Cloud Logging configuration retains default application logs for 30 days and required audit logs for 400 days. Those logs are separate from spreadsheet records and may be affected by later provider or project settings. Uninstalling does not immediately remove Google-managed logs or backups.

Spreadsheet records remain until you or another authorized person edits or deletes them. Per-user workbook grants, app-created workbook identities and Calendar connection/event identities support access and recovery. The application does not use one global customer-workbook pointer. No Google user data is used to develop, improve or train generalized artificial-intelligence or machine-learning models.

Support emails

If you email us, we receive your email address, message and any attachments you choose to send. Adam uses these to answer your request and resolve support or privacy issues. Send only the information needed and redact business or personal details from screenshots. Do not send passwords, security codes, authorization codes, access tokens, payment details or a complete customer workbook.

Support correspondence is retained for as long as reasonably needed to handle your request, maintain necessary business records, resolve disputes or meet legal obligations. You may request deletion by email. We will delete information we no longer need, subject to applicable obligations and the email provider's backup and deletion processes. No fixed automatic mailbox-deletion schedule is currently represented by this policy.

Service providers and sharing

Google provides Drive, Sheets, Calendar, Apps Script, authorization, logging and the Gmail support mailbox. OpenAI's Sites service hosts this website and may process technical information such as IP address, browser details, requests, security logs and sign-in/session information where sign-in is enabled. Providers may process information in countries other than yours under their own service and privacy terms. See Google's privacy policy and OpenAI's privacy policy.

We use information to operate the features described here, answer requests, maintain security and comply with law. We do not sell Google user data, use it for targeted advertising, or transfer it to data brokers. Any disclosure of Google user data is limited to delivering the requested features with appropriate consent, necessary security purposes, legal requirements, or a business transfer with prior consent as required by Google's rules. We do not routinely ask for access to customer spreadsheets or read their contents for support; any such access requires your specific agreement, except where access is necessary for security or legal compliance.

Google API Limited Use

Farmer’s Helper's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Website cookies and security

This website's own code does not include advertising trackers, analytics scripts, a checkout or a contact form. The hosting service may use technical cookies or similar measures to deliver, authenticate and secure the site. We use the authorization and security controls provided by Google and our hosting provider. No system can guarantee absolute security.

Your choices

You control your spreadsheet and its sharing permissions. You can uninstall the add-on through Google Sheets' add-on management and remove its access through your Google Account's third-party connections. These are separate actions. Revocation prevents further authorized operations; it does not undo a write already dispatched or erase previously saved records, provider logs or support emails. You can clear browser recovery storage and contact us about information held by Smarter Spreadsheets.

The service is intended for people managing their own work and business records, not for children under 13. Please avoid entering unnecessary sensitive personal information into the workflow.

Changes to this policy

We will update this page and its date when practices change. Material new uses of Google user data will be disclosed before they begin, and additional consent will be requested where required. Contact adamhunter9@gmail.com with questions.