On this page
1. Local workflow
- The browser reads supported Excel and CSV files you select, or data you choose to paste. Clipboard access is used for the requested input operation, not for continuous clipboard monitoring.
- Joining sheets, appending sheets, comparing values, applying filters, previewing results, selecting columns, and exporting results are designed to take place on the current device.
- Source rows and preview values stay in the active page’s memory during spreadsheet operations.
- Downloaded results and Data Recipes remain wherever you save or synchronize them.
2. Information outside the workspace
- Ordinary requests needed to load the website, which can expose an IP address, browser headers, timestamp, and requested assets to deployment infrastructure.
- Language and theme preferences stored in the browser.
- Google-linked account, authentication session, profile, and plan information processed by Supabase.
- Messages, screenshots, or attachments intentionally sent to support.
- Payment information processed by Paddle, and limited transaction and subscription information used by JOIN SHEET to provide plan access.
3. Safeguards and operational practice
The architecture reduces the need to transmit source rows, but no product can remove risks from an infected device, malicious extension, screen capture, clipboard monitoring, unsafe download folder, cloud-sync client, or another person with device access.
JOIN SHEET does not claim ISO 27001 certification, SOC 2 attestation, end-to-end encryption, zero knowledge, or absolute security.
4. User responsibilities
- Use a supported, updated browser on a trusted device.
- Confirm that local browser processing and local export are permitted by your employer, contract, and applicable sector rules.
- Keep independent copies of important files and review exported results.
- Do not place passwords, full card numbers, or confidential source values in an ordinary support email.
- Use synthetic data when testing a problem. Browser extensions, operating-system clipboard history, and synchronized folders are governed by their own settings; JOIN SHEET cannot disable or erase their copies.
5. Incident handling
We assess credible reports, contain confirmed issues, preserve appropriate records, and notify affected people or authorities where the applicable law requires it. Public incident updates will distinguish verified facts from investigation status.
Use the Vulnerability Disclosure page for a suspected product security flaw and the Privacy requests section on the Contact page for a personal-data concern.
6. Changes to the boundary
A feature that sends source rows or cell values off the device will not be described as local processing. Before activation, we will clearly explain the destination, purpose, controls, and any required choice or contract protection.
The provider register identifies active account and payment integrations and will be updated before integrations for analytics, error diagnostics, or additional support platforms are enabled.
7. Local processing does not mean offline access
Each result-save request requires an online check and a recorded click before export can start. If that record cannot be confirmed, export is blocked and you must retry. Spreadsheet data stays on your device; the online record contains click identifiers, the server timestamp, and verified account, plan and billing information.
Website delivery, sign-in, account checks, and paid access may need an internet connection. A network or provider failure may affect those features even while source rows remain local.
Closing or refreshing the active page can discard work. Keep the page open during an access-recovery attempt, preserve any downloadable result or recipe, and use Contact Support if recovery fails. Local processing is not a guarantee that company firewalls or data-loss-prevention tools will allow the site.