Sheet Zaber — Terms of Service

Sheet Zaber (sheet.zaber.tech) publishes one tab of one Google Sheet you own as one REST endpoint under /api/v1, served with the Google permission of the account that registered the sheet. It is a thin, authorized proxy in front of your own spreadsheet — not a database, backup or cache: your rows stay in Google Sheets and we keep only account, configuration and log metadata (see /privacy). There is no billing, subscription, trial or paid tier in the product, so there is nothing to pay and nothing to refund; the service is free of charge.

These terms are between you and Osayeed Zaber, who operates the platform through a single owner account and is established in Dhaka, Bangladesh. Bangladeshi law governs; §11 states the forum.

Two roles exist. owner is one account, granted only to the configured owner email at first sign-in, with no self-promotion path. Everyone else is user, and runs their own surface: register sheets, build endpoints, issue and revoke their own keys, read their own logs and analytics. You are the operator of your own endpoints and answerable for them.

No account exists until you redeem an invitation code during registration; signing in with Google alone creates none. Codes are single-use by default, can expire, can be revoked, and are known to the platform only as a hash. A code is issued to you: one Google identity gets one account, and circulating an invitation is a misuse of it, for which the operator's remedy is revocation of the code and of the accounts that followed. The operator may stop issuing invitations, or end the service, at any time. No entitlement to access is implied.

You are responsible for everything done under your account and with every key issued to it. A key (sz_live_ plus 32 hex characters) is shown exactly once; only its hash and a short preview are stored, so nobody can recover a lost key for you — plan to rotate rather than to retrieve. Regenerating a key revokes the old one and mints a new secret. Send the key in the Authorization: Bearer header; keys in query strings are not accepted, because URLs leak into logs and referrers. Keep keys server-side, out of browser code, mobile binaries, repositories and logs. You can scope a key to read or read-write, restrict it to specific endpoints, set an expiry, and revoke it — revocation takes effect on the next request.

You agree not to:

• register or reach a sheet you have no right to read or write. The platform tests this instead of trusting you: registration calls the Sheets API with your own connection, and a sheet your account cannot access is never created.
• attempt to reach another user's data, tokens, keys or endpoints, or raise your own role. No path accepts a user-supplied token, and refused attempts are audited.
• publish personal data you have no right to expose through an endpoint you created, or share your keys.
• breach Google's terms for the Sheets API — your grant is the one being used, and Google's quotas sit in front of ours.
• attack, abuse or attempt to defeat the rate limits, authentication or logging of the service.
• put behind an endpoint anything you would not want the operator to see metadata about: tab titles and row and column counts are stored; cell contents are not.

• Rate limits, per key by default: 1000 requests/hour and 10000/day, in fixed windows, with a per-endpoint hourly override and an extra per-client-IP hourly window. Fixed windows can admit a burst at a boundary. Exceeding a limit answers 429 with Retry-After.
• Body size: at most 1,000,000 bytes, rejected with 413 before parsing.
• Writes: POST takes one JSON object or an array of up to 500 objects, each setting at least one real column. PATCH, PUT and DELETE take exactly one object.
• Reads: limit 1–1000 (absent means all rows — an unbounded read pulls the whole tab from Google), offset, fields projection, a full-text q, and where[column]=value filters. Row numbers are never returned.
• Schema drift: an endpoint validates columns against a snapshot taken when you registered the tab. A header you add later in Sheets is invisible until you refresh the tabs; an unknown column is refused with the list of real ones.
• Google's quota (roughly 60 read and 60 write requests per minute per user) applies upstream and surfaces as 503 with Retry-After passed through.

Refusals all use one shape, { "error": { "code", "message", "category" } }:

No uptime SLA, support-response window, incident notification or status page exists, so none is implied. The deployment is one application and one single-region Postgres instance (Singapore) maintained by one person. Two states are expected behaviour rather than outages: while the OAuth client remains in Google's Testing state, stored permissions expire after 7 days and calls answer 503 until reconnection; and a sheet that becomes inaccessible to your permission answers 422. Questions about an account or a refusal: support@zaber.tech.

The operator may disable an account, change a role, revoke an invitation or revoke a key. Disabling takes effect on the next request: sessions are re-validated against the account row every time, so the dashboard closes and the keys stop passing the ownership check. Each action is audited, including refused attempts. Account closure is an owner action, not a button: it removes your account together with your connections, registered sheets, endpoints and keys. What does not go with the account is its history — the request-log rows and the operator's audit rows that describe it survive, because the platform exists to answer later what happened to an API, how it happened and who used it (see §8 of /privacy). Closure cannot be carried out on the account that issued invitations, on the operator's own account, or on the only remaining owner. You can end your use at any time by revoking your keys, removing your registered sheets, revoking the app's access in your own Google account, and asking support@zaber.tech to delete the account. Removing our copy of a permission is not revoking it at Google — do both.

Your spreadsheet content stays yours and stays in your spreadsheet; the operator claims no ownership of it and keeps no copy of it (see /privacy). The application, its code and its branding belong to Osayeed Zaber. These terms grant you the right to use the service for its intended purpose while your account is active — no resale, sublicence or right to republish the software.

The service is provided as is and as available, without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement. The project documentation is the specification you rely on; the operator does not warrant that the implementation matches it in every respect, and asks you to report a difference rather than assume one. To the extent the law allows, the operator is not liable for lost data, lost profit or any indirect or consequential loss arising from use of the service — including losses from the last-write-wins behaviour, Google outages and quotas, permissions expiring, rate limits, and misuse of a key you issued. The service is provided free of charge, and that is the bargain offered.