Handling Data Privacy

Data Privacy is handled by masking the data. Own doesn’t change or delete records from backups. When you request records from a backup, either directly in the application or via API, the records are masked.

If the backup is exported from the Own application, the records won't be masked. You're responsible for masking your own data outside of the Own application.

Our approach of keeping the data and masking it just-in-time during restore (and all other data-access operations) ensures the backup integrity is unharmed, and significantly reduces the likelihood of a failed restore.

Own identifies Personally Identifiable Information (PII) by scanning the field type, field label, and field name, as well as looking to see if the field has a common PII ending, for example country code.

Once identified, we send an email to the customer listing the fields identified and stating we're going to mask them.

Picklist fields are nullified. If the picklist is restricted, then it is assigned the last value in the list.

In Salesforce, customers can use the PII Compliance Classification Tool to mark their custom fields as PII, in order to be detected by our PII identification process.

If the PII Compliance Classification Tool is used to mark a custom field as PII after backups with that field have been created, the Data Privacy mask won’t be retroactively applied to existing backups. Only backups created after the field was marked will mask the field.

We detect any custom field marked with a compliance flag.

For BYOS customers, if you request records directly from your storage account, these records won’t be masked. If you terminate the relationship with Own, you’re responsible for masking your own data.