Mark the fields that hold personal data as Sensitive: they are excluded from your exports. They stay visible in the application. An encrypted field is Sensitive from the moment it is created: you have nothing to do. Here is where to find the GDPR / confidential marking option and what each state means.
1. Where is the GDPR / confidential marking option?
Open the field menu or its configuration window: the result is the same. Only the workspace owner and administrators can change the marking. Other members see it but cannot change it.
1
Open the field menu
Click the header of the field you want to mark.
2
Choose GDPR / confidential marking
A submenu lists the states available for this field type.
3
Select a state
Sensitive or Not sensitive. Four types also offer Inherited: linked table column, Link to another table column and two selects. These selects, single or conditional, are fed by another table. The setting is saved immediately.
A field marked Sensitive shows a shield in its header. You can then spot the sensitive fields of a view at a glance.
1.1 How do you mark several fields at once?
In the Organize fields window, you mark all the fields of the table in one place.
1
Open the table menu
Click the ⋮ button to the right of the tabs.
2
Choose Organize fields
The window lists the fields of the table, one row per field.
3
Set the GDPR / confidential column
It shows the state of each field. The GDPR / confidential filter, at the top of the window, shows only the marked fields.
4
Click Save
The markings apply to the whole table.
1.2 What does the GDPR / confidential column of Organize fields show?
This column shows a checkbox for fields with two states. It shows three icons for fields that also offer Inherited. Only the encrypted field is ticked as soon as it is created: it is Sensitive from the start.
What you see
Field type
Meaning
Action
Empty checkbox
Plain field: text, number, date, single-select, formula
Not sensitive. The field goes into exports.
Tick the box to mark it Sensitive.
Ticked checkbox
Plain field or formula, ticked by hand
Sensitive. The field is excluded from the export if the GDPR checkbox is ticked in that export.
Untick the box to go back to Not sensitive.
Ticked from creation
Encrypted field
Sensitive by default. The field is excluded from the export if the GDPR checkbox is ticked in that export.
No action needed: the marking is automatic.
Three icons
Linked table column, Link to another table column, single or conditional select fed by another table
The blue icon is the current state.
Click an icon to change the state.
The three icons, from left to right:
Icon
State
What it means
Chain link
Inherited
The field is sensitive as soon as a field it reads is sensitive. It is the default state of a linked table column or a Link to another table column.
Shield with padlock
Sensitive
You mark the field yourself. It is excluded from the export if the GDPR checkbox is ticked, whatever fields it reads.
Crossed shield
Not sensitive
The field goes into exports, even if the field it reads is Sensitive. Choose this state when the field shows no personal data.
Example: in the Customers table, Contact, Email and Phone are ticked. In the Orders table, the Customer email linked table column shows the chain link in blue: it is Inherited.
2. What do the Sensitive, Not sensitive and Inherited states mean?
Every field has a default state, based on its type. You do not have to go through your current tables.
Plain field: Not sensitive
Text, number, date, checkbox, single-select. Two possible states: Sensitive or Not sensitive.
Formula: Not sensitive
Two possible states: Sensitive or Not sensitive. A formula never inherits from the fields it reads.
Linked table column, Link to another table column, single or conditional select fed by another table: Inherited
This field becomes sensitive as soon as a field it reads is sensitive. Three possible states: Inherited, Sensitive or Not sensitive.
Encrypted field: Sensitive
An administrator can set it to Not sensitive.
Example: the Invoice label formula joins the order number, the customer company and the contact's email. It is Not sensitive by default, as in the screenshot. Because it copies an email, set it to Sensitive.
Change the state only for fields that hold personal data.
State
Meaning
Default for
Inherited
The field becomes sensitive as soon as a field it reads is sensitive. Nothing to set: TimeTonic handles it.
Linked table columns, Link to another table columns, single or conditional selects fed by another table. Never formulas.
Sensitive
You state that the field holds personal data. It is excluded from the export if the GDPR checkbox is ticked.
Encrypted fields. An administrator can set them to Not sensitive.
Not sensitive
The field does not hold personal data: it goes into exports. A linked table column set this way is exported, even if the field it reads is Sensitive.
Plain fields and formulas.
Only four types offer Inherited: linked table column, Link to another table column and two selects. These selects, single or conditional, are fed by another table. A plain field or a formula only offers Sensitive and Not sensitive. If you duplicate the field or the table, the marking is copied too.
3. What is the logic behind GDPR / confidential marking?
Marking is a setting of the field, like its name or its type. It hides nothing. Members who could see a Sensitive field in the workspace still see it. They read, filter and edit it as before.
Marking is only for exports: it flags the fields that must not leave TimeTonic. It applies to the whole field, to every member and to every export of the table.
It does not hide the field
To hide a field from some members, use encryption or view rights, not marking.
One setting for all members
Only the owner and administrators can change it. It is not a personal preference.
The export decides
Marking flags the fields to exclude. Each export excludes or keeps them, based on its GDPR checkbox.
It is up to you to spot the personal fields. TimeTonic does not detect personal data: mark it yourself. Email, Phone and URL are excluded by default because of their format, not under the GDPR. Mark Sensitive any field that holds personal data, whatever its type. A name typed into a text field is only excluded if it is marked. Where the option is → chapter 1.
4. How does a field inherit sensitivity from another one?
A field set to Inherited is sensitive as soon as a field it reads is sensitive, even in another table. A linked table column that reads a sensitive field becomes sensitive. A second linked table column that reads the first one becomes sensitive too. You have nothing to set.
Linked table column
Sensitive if the field it shows is sensitive. If that field is itself a linked table column, TimeTonic goes back to the original field.
Link to another table column
Automatically Inherited GDPR / confidential, like the link column TimeTonic creates opposite it, in the other table. No other field plays a part, and nothing needs to be marked. Both are therefore excluded from exports by default. To export one, untick it in the Fields to exclude list.
Single-select fed by another table
Sensitive if its source field, in the other table, is sensitive.
Conditional select fed by another table
Sensitive if its source field, in the other table, is sensitive.
Formula
Does not inherit: its menu does not offer Inherited. Mark it Sensitive by hand if it copies personal data.
4.1 Use case: which fields to mark in two linked tables?
Two tables are linked: Customers and Orders. You want to export Orders without personal data. Here are the fields to mark, in four steps.
1
Mark personal data at its source
Open the Customers table. Spot the fields that identify a person: Contact, Email, Phone. Mark them Sensitive.
2
Nothing to do on linked table columns
In Orders, the Customer email linked table column reads the Email field. It becomes sensitive on its own, by inheritance. In Organize fields, its chain link is blue.
3
Review each formula
A formula never inherits from the fields it reads. Invoice label copies the customer's email: mark it Sensitive by hand. Total (excl. VAT) computes an amount: leave it Not sensitive.
4
Check in the export
The Exclude fields marked GDPR / confidential checkbox is ticked by default (chapter 5). The Fields to exclude list must show Customer email and Invoice label.
Result, with the GDPR checkbox ticked in the export:
Field
Type
Your action
In the export
Customers: Email
Plain field
Mark Sensitive
Excluded
Orders: Customer email
Linked table column
None: it inherits
Excluded, by inheritance
Orders: Invoice label
Formula that copies the email
Mark Sensitive by hand
Excluded
Orders: Total (excl. VAT)
Formula that computes an amount
None
Exported
Formulas do not inherit the marking. A formula offers two states: Sensitive and Not sensitive. It is Not sensitive by default, even if it reads a sensitive field: so it goes into the export. Mark as Sensitive every formula that copies personal data, such as a label that joins name and email. A formula that does not copy the data, such as a TRUE / FALSE, can stay exported.
4.2 Take a field out of inheritance
Set it to Not sensitive. It no longer depends on the field it reads: it goes into exports. Fields that read it do not become sensitive because of it. Conversely, choose Sensitive to keep the field sensitive, even if its source changes.
Example: a linked table column reads a field marked Sensitive out of caution. Its value is not personal, such as a department code.
5. How do I exclude marked fields from my exports?
In a new export, marked fields are excluded by default. You can change this choice in each export.
1
Open an export
An existing export, or a new one, in the FTP / SFTP transfers or the Metabase export.
2
Go to the Exported fields section
It sits in the configuration window of the export.
3
Check the Exclude fields marked GDPR / confidential checkbox
It is ticked by default. The marked fields are then ticked in the Fields to exclude list, with their reason. Untick the checkbox only to export these fields.
Marked fields no longer go out, including those marked later. An export created before the marking is not changed: open it to tick the checkbox. Mark first the formulas that copy personal data.
6. Frequently asked questions on GDPR / confidential marking
Should I mark an Email field that is already excluded by default?
Yes, if it holds personal data. Email, Phone and URL are excluded because of their format, not under the GDPR. If the field types checkbox or the field is unticked, the field 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.
I marked the field in my table, but it is still visible to a member. Is that normal?
Yes. GDPR / confidential marking only acts on exports. Members still see the field in the application. They read, filter and edit it as before. To hide data from some members, use an encrypted field. Marking is only used to exclude the field from an exported file.
I cannot change the marking. Why?
Only the workspace owner and administrators can change the marking. The setting applies to all members: it is not a personal preference. For an ordinary member, the GDPR / confidential marking option is read-only. Ask an administrator to mark the field for you, or to give you that role in the workspace.
The Inherited option is not offered on my field. Why?
Your field is a plain field or a formula. Only four types offer Inherited: linked table column, Link to another table column and two selects. These selects, single or conditional, are fed by another table. A plain field or a formula only offers Sensitive and Not sensitive. Choose Sensitive if it holds or copies personal data, so that exports can exclude it.
My formula reads a sensitive field but is not excluded. Is that a bug?
No. A formula does not inherit the marking: this is a product choice. It stays Not sensitive until you mark it. Mark it Sensitive by hand if it copies personal data, such as a label that joins name and email. The GDPR checkbox of the export then excludes it like the other fields.
Go further
Choose the exported fields (FTP / SFTP)
Chapter 5.6: tick the GDPR checkbox in the export window.