Why client-side is different
With a traditional SaaS chart tool, “privacy” is a policy: the vendor promises to protect the data it holds. With Datastripes it is architecture: on private plans we do not hold the rows in the first place. Data you never upload cannot be breached, subpoenaed from us or used for training.
This also makes the tool fast. There is no upload queue or server round trip, and filtering half a million rows happens at the speed of your laptop.
What is shared when you publish
Publishing creates a chart that other people can see, so something must be shared. Datastripes shares only what the chart needs: typically aggregated values, not the raw file. You can preview the exact published dataset before you click Publish, and password-protect it on Pro. Free public projects are published to the gallery, so use a private plan for sensitive data.
GDPR, HIPAA-style constraints and data residency
Because raw records stay on the user’s device, many projects never involve Datastripes as a processor of personal data at all, which simplifies records of processing and DPIAs. Enterprise customers get a DPA, SSO, audit logs and a self-hosted embed runtime for full data residency. Always confirm your specific use case with your data protection officer.
