Nothing saved behind your back
Every change waits, highlighted, until you press Save. Then it goes through the same validation, fieldtypes, revisions and permissions as the entry page. The addon stores nothing of its own and never contacts us.
Where your data goes
Between your Statamic server and the browser of the Control Panel user who opens a sheet. The addon makes no other network requests. It never contacts Karelia Labs: it has no telemetry, no analytics and no account with us. Statamic itself checks licence keys with statamic.com; that is part of Statamic, not of the addon.
What is stored
The addon has no storage of its own on the server. This is all it keeps.
| Data | Where and why | How long |
|---|---|---|
| Which columns a user shows for each collection | The user's browser (local storage). Remember the layout | Until the user clears the browser's data for the site |
| The most entries loaded into one sheet | The site's config file. Run the addon | Until changed |
Personal data
The addon adds no personal data. Entries in a sheet may contain personal data, such as authors or user fields; they are loaded into the browser of a user who is allowed to view them, while the sheet is open. Saved changes are recorded by Statamic as on the entry page, including who changed the entry last. CSV exports are files on the user's own computer. Your site is the controller of this data.
Permissions
The addon adds one Statamic permission under Users, Roles, and checks Statamic's own entry permissions on the server for every cell.
| Permission | Why the app needs it |
|---|---|
| Use the spreadsheet | Open the spreadsheet and the Edit in Spreadsheet action |
| Statamic's entry permissions | View, edit and publish rights for each collection, and the right to edit other authors' entries, decide what a user sees and can change |
Access control
Every request is checked on the server. A user sees only entries they may view and can change only entries they may edit. Changing the publish status needs publish rights, and changing the author needs the right to edit other authors' entries. On multi-site installs, the user needs access to the site. A request that breaks a rule is refused for that entry, and the cell shows why.
Untrusted input
Every value is treated as untrusted. Each entry is validated by its blueprint's rules on the server, and processed by its fieldtypes, before it is saved; a failed entry is not changed at all. A new slug that would give two entries the same URL is refused. Imported CSV files are parsed in the browser and become ordinary unsaved changes. Exported CSV cells that begin with =, +, - or @ are written so that spreadsheet programs do not run them as formulas.
Dependencies
The server side depends only on Statamic and Laravel, installed by Composer. The Control Panel script bundles RevoGrid and its Vue 3 wrapper (MIT license), pinned to a fixed version; their notices are in THIRD-PARTY-NOTICES.md in the package. It loads only when a sheet is opened.
Logging
The addon writes nothing to logs during normal use. An unexpected error while saving an entry is reported to Laravel's log as any error would be. Content is never logged by the addon.
Sub-processors
None. We receive no site data, so there is nothing to pass on. Licences and payments are handled by Statamic and Stripe. For the other parties involved in our own support and bookkeeping, see the privacy policy.
AI and language models
None. The addon contains no language model and sends no content to any.
Vulnerabilities
Report a suspected vulnerability to support@karelialabs.atlassian.net. Please include what you found, how to reproduce it and which version is affected, and give us a reasonable time to fix it before you publish details. We read every report.
Deleting data
The addon keeps nothing on the server. A user's column choice disappears when the browser's data for the site is cleared. Removing the addon with Composer removes it completely.