Security and data
This page covers where your data is, the compliance status of the service, and how to remove data. For the full security overview, see work.studio/security.
Where your data lives
Section titled “Where your data lives”work.studio runs in Amazon Web Services, in the us-west-2 region (Oregon, United States).
work.studio is not SOC 2 certified. A SOC 2 audit is planned. For the current status, see work.studio/security.
Who can reach what
Section titled “Who can reach what”- People in your organization see what their role allows.
- Each of your customers sees only their own connections and data. See Embed authentication.
- The audit log shows who changed what.
How long data is kept
Section titled “How long data is kept”Audit log entries are kept for 365 days while your account is live, then soft-deleted (they no longer appear in the audit log). They’re erased with your organization when it’s deleted.
What reached your triggers (webhook requests, captured messages, schedule times) is kept for 30 days in each trigger’s Deliveries, then deleted:
- The list (time, source, status and reason) and a short preview with credentials, secret-like values, card numbers, email addresses and phone numbers masked. A message’s preview never has its text.
- The full content of deliveries that passed the trigger’s checks, so they can be replayed or used as a sample. It’s kept in your organization’s storage: your own storage bucket when your organization has one set up, otherwise work.studio’s. The content of a refused request is never kept.
- Who sees it: people who can edit the automation see the content. A delivery from a person’s own account, or of a personal automation, is private to that person; admins see only a count. Viewers see the list without content.
Deliveries waiting on a paused trigger are kept until they run, are discarded or expire (7 days by default, at most 30).
The full Designer view has a Data Retention Policies page under Governance › Compliance, but its fields can’t be edited there (“Contact support to modify these settings.”). To change how long your data is kept, contact support@work.studio.
Deleting data
Section titled “Deleting data”| What | How |
|---|---|
| Your whole organization | Account › Delete organization, in the avatar menu. Only an Owner can do this. See Delete your organization |
| One of your customers and their data | Distribute › Customers, open the customer, Delete Customer. See Apps and customers |
| A person who uses your App directly | Your App calls app.account.delete(), or you run npx workstudio apps users delete. Either removes them from all your Apps in that environment. See App SDK |
| A member of your team | Team › Team Members › Remove. See Team and roles |
Delete your organization
Section titled “Delete your organization”- Open Account from the avatar menu and scroll to Delete organization. Only an organization owner can delete the organization.
- Select Delete organization…. Choose Why are you leaving?, type the organization’s name to confirm, check “I understand this permanently deletes the organization and its data for everyone in it.”, and select Email me the confirmation link.
- Follow the link in the email within 24 hours. If nobody does, the request lapses and nothing is deleted. Until then, Withdraw request cancels it.
- Once confirmed, there’s a 30-day grace period: the page says when the organization will be deleted, and everything keeps working until then. An owner can select Cancel deletion during it. When it ends, the organization and all its data, in every environment, are deleted for good.
Export anything you need first.
Getting a copy of your data
Section titled “Getting a copy of your data”Automatic data exports aren’t available. Request Export on the Data Privacy and Data Requests pages answers “Automatic data export is not available yet, so no file has been produced. Contact support@work.studio and we will send you your data by hand within the legal deadline.” and the request shows Not available - contact support. To get a copy of your data, or to answer a request from one of your Apps’ people, email support@work.studio and it’s sent to you by hand.
Files that could run in a browser
Section titled “Files that could run in a browser”A file whose type could run script in a browser, such as HTML, SVG, XML or JavaScript, is kept as a plain download. Its link downloads it instead of opening it, whatever type it was uploaded with, and that includes files stored before this rule. Photos, PDFs, office files, text, audio and video open as usual. Brand logos in SVG are still shown as images.