🛡 SECURITY & GDPR

Exports, PII and device hygiene

A practical hygiene guide for safely sharing CSVs and reports that contain customer data.

Updated:

Customer data is protected by strict access control inside the panel. The moment a file is exported, that protection ends and responsibility shifts to the person who downloaded it. Export hygiene is invisible but critical.

An export is not a permission; it is a transfer of responsibility. The downloader becomes part of the privacy chain from that moment on.

Deciding to export

Before any CSV export, check if a panel filter already meets the need. If a real export is needed, log the reason and the recipient — it pays back during audit.

Sharing channel

  • Use a secure storage link, never plain email.
  • Add a 24-48 hour expiration to the link.
  • Track who downloaded it.
  • Never post in a general Slack channel.
  • Do not keep customer data on the device beyond 30 days.

Device hygiene

Delete the file when the work is done. Empty trash, check automatic cloud sync, and remove copies from mobile devices.

Kontrol listesi / Checklist

  • Export reason is logged.
  • Sharing uses a secure channel.
  • Link has an expiration.
  • File deleted after use.
  • Added to monthly access review.

SSS / FAQ

How do I show a customer their own data?

Customers can request their data; respond manually with a privacy-compliant process.

Can I cap the number of exports?

Effectively yes through role-based access and monthly review. A clear export policy with the team helps.

Did this not solve it?

Write to our support team — we reply within 2 hours. Our median reply time is 12 minutes.

Contact support