Exclude fields from an export: sensitive data and GDPR
Updated on
By default, an export removes two kinds of fields: those marked GDPR and eight field types. This applies to FTP / SFTP and Metabase exports. You find them ticked in the Fields to exclude list. Untick a field to keep it in the file. Encrypted fields are Sensitive from the moment they are created: they are excluded automatically.
Are you setting up an FTP / SFTP or Metabase export? In the configuration window, the Exported fields section sets which fields go into the file. It is also described in the article of your export: FTP / SFTP, chapter 5.6 Β· Metabase, chapter 2.1. Only the workspace owner and administrators set up an export.
Fields marked GDPR / confidential
Field types not exported by default
Which fields
Fields marked Sensitive with the GDPR / confidential marking option, encrypted fields (Sensitive from creation), those that inherit it and Link to another table columns
Comments, History, URL, Attachment, Email, Phone, Smart text, External form
A field stays out of the file for two reasons. It is marked GDPR / confidential, or its type is not exported by default. The Fields to exclude list shows these fields, each with its reason.
1.1 Fields marked GDPR / confidential
To keep a personal field out of the file: mark it Sensitive in the table, and keep the GDPR checkbox ticked in the export. You need both. An encrypted field is already Sensitive when it is created: you have nothing to mark.
1
Mark the fields with the GDPR / confidential marking option
Field menu β GDPR / confidential marking β Sensitive. Linked table columns and Link to another table columns inherit the marking, formulas do not. Details: GDPR / confidential marking: mark a field.
2
Keep the Exclude fields marked GDPR / confidential checkbox ticked in the export
Exported fields section β Exclude fields marked GDPR / confidential, ticked by default. Every sensitive field is removed from the file, including those marked later.
3
Check the file with Test config
Test config shows the fields that will really be sent.
Link columns are excluded by default, in both tables. When you create a Link to another table column, TimeTonic also creates a link column in the other table. Both automatically become Inherited GDPR / confidential. No other field plays a part, and nothing needs to be marked in their tables. To export one, untick it in Fields to exclude. If the GDPR checkbox is unticked, the marking removes nothing from the file.
1.2 The eight field types not exported by default
Eight field types are not exported by default: their value is hard to read in a flat file. The Exclude non-exportable field types by default checkbox ticks them in the Fields to exclude list. It also ticks the linked table columns that show one of these fields. To keep one, untick it in the list. A kept attachment goes out as a link.
2. What do the two checkboxes of the Exported fields section do?
Good practice: the source view chooses the file's fields first. A field set to Invisible in the view does not go out β Restrict access to a column by view. The two checkboxes then remove, among the remaining fields, those marked GDPR / confidential and the field types not exported by default. Prepare the view β Set up an FTP / SFTP transfer, chapter 5.2.
The section holds two checkboxes and the Fields to exclude list. Each checkbox ticks a whole group of fields in the list at once. After that, only the list counts: a ticked field does not go out, an unticked field does.
Exclude fields marked GDPR / confidential
Ticks every sensitive field: marked in the table, or inherited. The selection is redone at every run. A field marked later is excluded without touching the export.
Exclude non-exportable field types by default
Ticks the fields whose value is hard to read in a flat file: comments, attachments, history. The full list is in chapter 1.2.
2.1 The four combinations of the two checkboxes
Setting
What goes into the file
No checkbox
Every field of the view, including GDPR fields and field types not exported by default.
GDPR checkbox only
Everything except sensitive fields.
Non-exportable types checkbox only
Everything except these types. GDPR fields go out, and a warning points it out.
Both checkboxes
Everything except sensitive fields and types not exported by default.
Each setting fits a specific use.
No checkbox: the file holds everything
An export created before this release is set this way. Name, email, comments, attachments: everything goes into the file. If fields are marked in the table, the GDPR fields message shows in the section.
GDPR checkbox only: personal data does not go out
Fields marked Sensitive and those that inherit from them are removed. Comments or attachments still go out, in a form that is hard to read in a flat file. Choose this setting if the recipient needs everything except personal data.
Only the types checkbox is ticked: GDPR fields go into the file
Comments, history, attachments and the other types of the list are removed. GDPR-marked fields still go out. The GDPR fields message stays on screen, and every run is logged.
Both checkboxes: the recommended and default setting
Only useful fields without personal data go out. The GDPR fields message disappears. A field marked later is excluded at the next run, without reopening the export.
2.2 What happens if you untick the GDPR checkbox?
By default, the Exclude fields marked GDPR / confidential checkbox is ticked: no warning shows. If the checkbox is unticked and marked fields go into the export, the GDPR fields warning appears. The screenshot below shows its two locations.
1. At the top of the section: exclude or keep
The message lists the marked fields that go into the export. Click Exclude fields marked GDPR / confidential to remove them. Click Keep them in the export to keep them.
2. Under the Fields to exclude list: a reminder
If you keep these fields, a second message lists them again. Every run of the export is then logged.
3. When you save: a confirmation
An Export of GDPR / confidential fields window lists the marked fields that go out. Save anyway confirms. Cancel takes you back to the section.
What to do when this warning appears β chapter 6.
3. Tick the GDPR checkbox or pick the fields one by one: which is better?
For personal data, keep the Exclude fields marked GDPR / confidential checkbox ticked. It also excludes fields marked later in the table. A selection made by hand in the Fields to exclude list stays frozen on the day you made it.
Setting
A sensitive field is added the following month
GDPR checkbox ticked
It is excluded automatically. Nothing to do.
Checkbox unticked, fields ticked by hand
It goes into the file. The list only excludes the fields ticked that day.
Keep field-by-field selection for a file that is too wide, to remove fields unrelated to GDPR.
4. How do you keep a GDPR-marked field in the exported file?
Untick the field in the Fields to exclude list. This choice always wins over the two checkboxes and over chained exclusion.
1
Open the Fields to exclude list
Each field shows its reason: Marked GDPR / confidential, Inherited GDPR / confidential or Non-exportable type.
2
Untick the field to keep
It goes back into the file. The other ticked fields stay excluded.
3
Test, then save
Test config confirms the field is back among the exported fields.
Example: an export to Metabase must contain the customer email. Keep the GDPR checkbox ticked, then untick only Customer email. The other sensitive fields stay excluded.
5. Why does an unmarked field disappear from the exported file?
A field that shows an excluded field is excluded too, even in another table. Formulas are the exception: see below.
Linked table column
Excluded if it shows an excluded field. A linked table column that shows this column is excluded too.
Link to another table column
Excluded by default in both linked tables, with no marking at all (chapter 1.1).
Formula
Never excluded automatically: a formula has no Inherited state. Mark it Sensitive by hand if it copies personal data.
5.1 Chained exclusion example: Customers and Orders tables
The Email field of the Customers table is marked Sensitive and excluded. Result for the fields of the Orders table:
Field
Result
Customers: Email
Excluded: marked GDPR / confidential in the table.
Stays in the file: formula that reads Customer email. Excluded only if you mark it Sensitive.
Orders: Total (excl. VAT)
Stays in the file: formula that reads Quantity and Unit price.
Formulas do not inherit the marking. This is intentional: a formula only offers Sensitive and Not sensitive. It is Not sensitive by default, even if it reads a sensitive field. So it does not appear in the Fields to exclude list and goes into the file. Mark as Sensitive, by hand, every formula that copies personal data. Example: a label that joins name and email. A formula that does not copy the data, such as a TRUE / FALSE, can stay exported.
6. What should you do when the GDPR fields warning appears in the export?
The GDPR fields warning lists the marked fields that still go into the file. It appears if the GDPR checkbox is unticked, or if a marked field is unticked in the list.
1
Read the list of the fields concerned
These are the sensitive fields the export still sends.
2
Choose one of the two buttons Exclude fields marked GDPR / confidential ticks the checkbox of the same name. The fields are excluded and the warning disappears. Keep them in the export keeps these fields in the file. A reminder stays below the list and every run is logged.
3
Confirm when you save
A confirmation window lists again the GDPR fields that still go out. Confirm to save, or cancel to go back to the list.
7. How do you check the file with Test config before scheduling the export?
Test config prepares the file like a real export. It takes into account the two checkboxes, unticked fields and chained exclusion.
1
Click Test config
TimeTonic prepares the file with your settings, without sending it.
2
Check the fields shown
They are the ones that will be sent. An excluded field is missing from the header, it is not exported empty.
3
Save Save or Save and close. As long as a change is not saved, the Close button becomes Cancel and closes without keeping anything.
Export to Metabase: a removed field also disappears from the table in Metabase. Any Metabase question or dashboard that used that field stops working. Refresh the schema in the Metabase admin, then fix the affected questions.
An encrypted field kept in the export comes out as an asterisk: its value is never written in clear.
8. Three practical cases of GDPR / confidential marking and export
An HR table sent to the payroll provider
Last name, First name, Personal e-mail and Social security number are marked Sensitive. The weekly export ticks the GDPR checkbox. The file only holds Department and Cost centre. A Personal phone field added later is excluded from the next run.
A formula that shows a name
The Full label formula joins Last name and Contract number. Last name is marked Sensitive. The formula stays Not sensitive and is not excluded. Mark it Sensitive by hand: the GDPR checkbox then excludes it like the others.
A dashboard that needs the email
The Orders table export keeps the GDPR checkbox ticked. In the list, Customer email is unticked: it goes into the file. Customer contact stays excluded, like Invoice label, marked Sensitive by hand.
9. Frequently asked questions on GDPR / confidential marking and exports
Should I mark an Email field that is already excluded by default?
Yes, if it holds personal data. Email, Phone and URL are excluded for their format, not under the GDPR. If the field types checkbox or the field is unticked, it goes out with no warning. Marked Sensitive, it is excluded under the GDPR. If it goes back into the export, the GDPR fields warning appears.
My old export excludes nothing. Is that normal?
Yes. Exports created before this feature keep their settings: no checkbox ticked, no field ticked. Nothing changes without your action. Open the export, tick the Exclude fields marked GDPR / confidential checkbox, then save. The sensitive fields are removed from the next run onwards.
A field I wanted to keep has disappeared. Why?
It shows an excluded field, or it is a link column. A linked table column is excluded with the field it shows. A Link to another table column is excluded by default. To keep it, untick it in the Fields to exclude list. Your choice wins over the checkboxes and over chained exclusion.
My Metabase dashboard no longer works. Why?
Excluded fields are no longer sent: they disappear from the table in Metabase. Any question or dashboard that used them then stops working. Refresh the schema in the Metabase admin, then fix the questions and dashboards that used those fields.
More fields than expected were excluded. Why?
A linked table could not be read while the export was prepared. Its linked table columns and Link to another table columns are then treated as sensitive, as a precaution. The run log reports it. Run the export again once the table is reachable: the fields come back by themselves.
Does marking hide the field in the application?
No. Every member sees it as before. Marking only acts on exported files, not on the application. To hide data from some members, use an encrypted field or restrict access to the field by view. Both of these settings combine with the marking.
Does the manual CSV export follow these settings?
Partly. You can exclude fields one by one when you download. The two checkboxes do not exist there, so marked fields are not removed automatically. Check the whole list carefully before you confirm, especially for a table that holds personal data.
Go further
Mark a field as personal data
The three states, inheritance and who can change it.