Privacy Policy

When you sign up with Google OAuth, we receive:

• Email address
• Name
• Google account ID

When you connect Google Sheets, we request drive.file access only, not your entire Drive. That means Sheetful can create spreadsheets for templates and read or update spreadsheets you explicitly choose in Google's file picker (or that we create for you). We use this access solely to write your bank transactions and related budgeting data into the spreadsheet you selected.

We do not use Google user data for advertising, and we do not sell it. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can revoke Sheetful's Google access anytime in your Google Account permissions or by disconnecting Google Sheets in Sheetful Settings.

When you connect Microsoft Excel, we request Files.ReadWrite, User.Read, and offline_access. Microsoft's consent screen describes Files.ReadWrite as access to your files, broader than Google's drive.file per-file Sheets permission. Graph does not offer an equivalent "only files this app created" scope that works for personal OneDrive workbooks today. We use this access to create Excel workbooks in your OneDrive and to read and update the workbooks you connect to Sheetful. We do not use it to search, read, or modify unrelated files as a product feature.

You can revoke Sheetful's Microsoft access anytime in your Microsoft account permissions or by disconnecting Excel in Sheetful Settings.

When you connect banks through Plaid, we receive:

• Transaction history (date, merchant, amount, category)
• Account balances
• Account names, types, and institution names

We do not receive or store your bank login credentials. You authenticate with your institution through Plaid.

Disconnecting a bank in Sheetful Settings removes Sheetful's connection: our access through Plaid ends and your bank stops sending data to Sheetful. Rows already written to your spreadsheet stay there. Your bank may still list the authorization under its own connected-apps settings (for example, Citi Online > Profile > Connected Apps); that listing may not appear under the Sheetful name. Changing your bank password does not remove that listing.

Stripe processes Premium subscriptions. We receive:

• Last four digits of your card (for display)
• Billing address and subscription status

We do not store your full card number.

We automatically collect:

• Device type, browser, and IP address
• Pages visited and features used
• Error and diagnostic logs

You can link a phone to your account from Settings, under Phones. Settings shows a link code that works once and expires after 10 minutes. Only a keyed hash of the code is stored, never the code itself.

For each linked phone, we store:

• The phone's public key. The private key stays on the phone and is never sent to us.
• The name you give the phone, sent once when it links. Changing it on the phone later does not change it here.
• Which kind of operating system it runs, and the version of the software that links it
• When it was linked and when it was last used

You get an email each time a phone is linked. The name appears on the Phones card and in that email.

A linked phone can see and edit your transactions, create or remove category rules, and start a sync. It cannot disconnect a bank or a spreadsheet, rebuild a spreadsheet, export your data, or delete your account. The phone never receives your bank login, the access Sheetful holds to your bank, or the access Sheetful holds to your Google or Microsoft spreadsheet.

Remove on the Phones card unlinks a phone and signs it out of Sheetful. A phone also stops working after 60 days without use. Deleting your account deletes your linked phones and link codes.

We share the minimum necessary with subprocessors that help us operate Sheetful. They may not use your data for their own marketing:

• Plaid - bank connections (Plaid policies)
• Google - sign-in and Sheets API (Google Privacy Policy)
• Microsoft - Excel / Graph (Excel users only) (Microsoft Privacy Statement)
• Stripe - payments (Stripe Privacy Policy)

We also use service providers that help us run Sheetful, such as hosting, data storage, email delivery, security, analytics and error monitoring. Each one is bound by contract to protect your data at least as well as this policy requires, and to use it only to provide its service to Sheetful.

We may disclose information when required by law or in response to valid legal process.

We do not sell your personal or financial information for money, and we never sell or share your bank transaction data. Consent-gated analytics cookies (described in Section 7) may be considered 'sharing' for cross-context behavioral advertising, or a 'sale,' under some U.S. state privacy laws. Declining the cookie banner, or turning analytics off later under Cookie preferences, opts you out of that sharing.

• Session cookie (NextAuth sign-in)
• CSRF protection
• Cookie preference (sf_cookie_consent)

We use a single analytics tool, served from our own domain. Until you make a cookie choice, and whenever you decline (or your browser sends a Global Privacy Control signal, which we honor), our analytics tool runs in cookieless mode: it counts page visits in memory only, stores nothing on your device, sets no cookies, and identifies no one. Only after you click Accept do we enable browser analytics. Google Analytics is not enabled on sheetful.io.

Global Privacy Control is honored as an opt-out: when your browser sends the signal we record your choice as declined and confirm on screen that we saw it. If you then deliberately turn analytics on using the control below, that later choice stands, and the on-screen note says so.

Error monitoring runs from the moment a page loads, before you make a cookie choice, because it is how we keep the service working. We remove the IP address field from error reports before they are sent. Session replay is off. No recording of your screen is made or sent.

Declining analytics does not block use of Sheetful. Separately from cookies, we record a small number of service events on our servers tied to your account, such as that an account was created, that a spreadsheet or a bank was first connected, that a first sync completed, and that a subscription started, changed, was cancelled, or a payment failed. These involve no advertising, no cookies, no bank or institution name, and none of your transaction contents.

One of these events is different in kind: it records that you asked to connect a bank, whether or not you finished. The completed events above describe something that already happened to your account; this one describes an attempt. It carries only an identifier for your account and nothing else: no institution name, no identifier from your bank, and none of your transaction contents.

Five things can be written to your browser before you answer the cookie banner. The campaign parameters from the link you arrived on (utm values and Google click ids), with the page you first landed on and the domain of the site that sent you, are kept in session storage so we can tell which link brought you here if you later sign up; session storage is cleared when you close the tab. If you arrived through a referral link, a referral cookie (_sheetful_ref) holds that link's referral code for 30 days, out of reach of the page's scripts, so the person who shared it can be credited if you sign up. A short key records that you have already been shown a particular upgrade notice, so you are not shown it twice. Your cookie choice itself is kept in local storage and in a cookie, so the choice is remembered on your next visit. If you choose Create your sheet on the try page, the file you dropped is kept in that tab's session storage for up to 30 minutes so it can go into your sheet after you sign in; it is deleted once it is imported. None of these identify you to us: the campaign parameters and the notice key die with the tab, the referral cookie holds only a code, and the cookie choice persists only so that we do not ask you again. The session-storage values are not sent anywhere on their own; the landing page, the referring domain and the campaign tags reach us only when you click to sign in, as described under "When you create an account" below. When you click Sign in, a five-minute cookie carries these values to the sign-in step, whether or not you have answered the cookie banner; it is out of reach of the page's scripts and is deleted once it is read. Before you accept, the only things that leave your browser are the cookieless page count described above, the analytics tool's own configuration request, and the error and performance reports our error monitoring sends (described under Analytics above), apart from what you send by signing in.

When you create an account, we record on it how you found Sheetful: the page you first landed on, the domain of the site that sent you (never the full address), and any campaign tags in the link (utm source, medium and campaign). We use this only in aggregate to understand which channels bring people to Sheetful; it is not shared with anyone.

You can turn optional analytics on or off for this browser at any time using the control below, the cookie banner (Accept or Decline), or Cookie preferences in the site footer.

California residents may request access, deletion, and information about our data practices. We do not sell personal information for money; for consent-gated analytics cookies that some state laws treat as sharing or a sale, see Sections 3 and 7 - declining or disabling them is the opt-out.

Residents of Colorado, Connecticut, Texas, Utah, Virginia, and other states with comprehensive privacy laws may have similar rights to access, correct, delete, and opt out of targeted advertising. Exercise them from Settings or by emailing support@sheetful.io; we respond to verified requests as those laws require. If we decline a request, you may appeal by replying to our response, and we will answer the appeal as your state's law requires.

Where GDPR applies, you may have rights to access, portability, erasure, restriction, and objection. Contact support@sheetful.io to exercise these rights.