Last updated: 30 October 2026
Binslot is an inventory add-on that runs inside your own Google Sheets™ spreadsheet. Your inventory data stays in that spreadsheet. We do not have a server or a database that holds it, and we cannot read it.
The short version. Binslot reads and writes the spreadsheet you install it in. Nothing you record — products, quantities, locations, suppliers, movements — is copied anywhere else. The only information that ever leaves your Google account is a licence key, sent over an encrypted connection to our payment provider to check whether a subscription is active.
Rafael Pereira de Araújo da Silva, Bragança Paulista, SP, Brazil (“we”, “us”), the developer of Binslot. Contact: [email protected].
Binslot asks for seven Google permissions. Each one exists for a feature you can see in the interface, and none is used for anything else.
| Permission | What it is used for |
|---|---|
spreadsheets.currentonly |
Read and write the inventory tabs, but only in the spreadsheet you have open and only while you have it open. This permission gives Binslot no access to any other spreadsheet in your Drive. |
drive.file |
Reach that same spreadsheet in the two situations where it is not open on screen: the daily low stock check, which runs on a schedule, and the companion phone page, where a scan made on a phone has to land in the file. This permission covers only files you have opened with Binslot or selected for it — never the rest of your Drive, which Binslot does not list, search or open. |
script.container.ui |
Show the Binslot side panel and its dialogs inside Google Sheets™. |
script.external_request |
One outbound call only: sending a licence key to our payment provider to check whether a paid subscription is active. No spreadsheet content is included. See “Licence checks” below. |
script.scriptapp |
Create and delete the scheduled check that powers low stock alerts, and only while you have alerts switched on. Turning alerts off on every spreadsheet deletes it. |
script.send_mail |
Send the low stock e-mail you asked for, from your own Google account, to the addresses you typed into the alert settings. Binslot sends no other e-mail and never mails anyone else. |
userinfo.email |
Write the e-mail address of the person who recorded each movement into the audit column of your own spreadsheet, so you can tell who did what. It is not transmitted to us. |
Settings tab
inside that same spreadsheet, and in the add-on storage Google keeps for your account. Both are inside
Google, not on our infrastructure.If you activate a paid subscription, Binslot sends the licence key you pasted to our payment provider,
Dodo Payments, to confirm the subscription is valid. The request travels over HTTPS to
live.dodopayments.com and contains the licence key and nothing else: no spreadsheet content,
no product names, no quantities, no e-mail address. The answer (valid or not) is cached inside your
spreadsheet so the check runs at most once a day.
Dodo Payments acts as merchant of record: it processes the payment and stores the billing details you give it at checkout, under its own privacy policy. We never see or store your card details.
If you never activate a licence, Binslot makes no outbound requests at all.
Binslot is built so that there is as little to protect as possible: the data stays in your file, under your Google account. Concretely:
drive.file it reaches only
the spreadsheet you use it in.Settings tab and the add-on
storage are deleted when you delete the spreadsheet or uninstall the add-on from your account.Data obtained through Google Workspace APIs is not used to develop, improve, or train generalized or non-personalized artificial intelligence and/or machine learning models. Binslot contains no AI or ML features, and no spreadsheet content is sent to any such service.
Binslot’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained through those APIs is used only to provide and improve the features you can see in Binslot’s interface, is never transferred to others except as necessary to provide those features, and is never used for advertising, for credit decisions, or for training AI or ML models.
Two open-source libraries are loaded from public content delivery networks so that barcode and QR codes
can be drawn and read in your browser: JsBarcode and qrcode-generator (jsDelivr),
and ZXing for reading a code from a photo. They run entirely in your browser, receive no
inventory data, and send nothing anywhere. Loading a file from a CDN discloses your IP address to that
CDN, as any web page does.
Binslot is a business tool and is not directed at children under 13. We do not knowingly collect information from them.
You can remove Binslot’s access to your Google account at any time:
Removing access stops all alerts and deletes the scheduled check. Your spreadsheet keeps all of its data. To delete the data, delete the spreadsheet — it is yours, in your Drive.
Because we hold no copy of your data, requests to access, correct, export or delete it are things you carry out yourself in your own spreadsheet — including export, which Binslot offers as CSV from the Import / export screen. If you believe we hold anything about you and want it removed, write to [email protected] and we will answer within 30 days. This covers requests under the LGPD (Brazil) and the GDPR (European Union).
If we ever become aware of an incident affecting data handled by Binslot, we will notify affected users by e-mail at the address associated with their subscription, and the relevant authorities where the law requires it, without undue delay.
If this policy changes we will update the date at the top and, for any change that affects what data is accessed or where it goes, tell you inside the add-on before the change takes effect.