Concepts
Data structure - a named tree of the tables that hold personal data. In the tree, each table stands below the table it belongs to. QUALIA's structure TENANT holds the Contact, the Customer, the Contact Business Relation and the Posted Sales Invoice tables, so "Tanja Weiss and everything that belongs to her" is one object the app can show, export, delete or anonymize.
Table guideline - the rule for one table, kept once for the whole company: which action runs (Delete or Anonymize) and after how long (the Action Date Formula). Posted Sales Invoice has the guideline "Anonymize after 10 years, dated from Posting Date".
Action Date Formula - how long a record may be kept. "5Y" means five years. A contact created on 12 June 2024 with "5Y" has the action date 12 June 2029. If the table's guideline names a date field (Posted Sales Invoice: Posting Date), the action date is that field plus the formula: the invoice posted 30 November 2018 with "10Y" may be anonymized from 30 November 2028.
Action type - Delete or Anonymize. Delete removes the record. Anonymize keeps the record and overwrites the personal fields with default values, so that the bookkeeping stays intact and only the personal data is gone. A posted invoice cannot be deleted, so Posted Sales Invoice is anonymized. With Dynamic Action Type, a record that would be deleted is anonymized instead when a related record that must be kept points to it (a contact that became a customer).
Record type - a template of values (protection class, protection level, Action Date Formula, Action Type) that a new table guideline copies. STANDARD (SK-1, level 3, 5Y, Delete) is used by every guideline of QUALIA's setup.
Protection class and protection level - two lists that say how sensitive data are: classes SK-1 "Normal need for internal data" up to SK-3 "Very high demand for secret data". Under a class you number the levels and enter the description of each level yourself in Protection Levels: the app does not define what a level means, so the wording is yours. The setup wizard's demo data, for example, name the levels from "Low protection need" to "Maximum protection need". QUALIA's setup works with level 3 of class SK-1, the one the record type STANDARD uses. Both the class and the level are assigned in the record type.
Scheduled action (planned action) - an entry the app creates for a record in a personal-data table: the action (Delete or Anonymize) and its action date. When Max Keller creates contact Tanja Weiss and customer Mietwerke Berlin GmbH, the app schedules "Delete 2029-06-12" for both. An action can be reset from Suspended to Waiting; moving it to a later date is described in chapter 3.
Suggestion (action suggestion) - a proposal to delete or anonymize one master data record with its whole structure. The app only suggests a record when the action date has been reached for every record in the structure; you check the suggestion and then Delete and Anonymize executes it.
Requesting person (data subject) - the person who asks about her data. The requesting person holds her name, address and e-mail and is linked to the Business Central record she is about (data structure, table and record). Lena Hartmann records Tanja Weiss as requesting person RQ-0001 and links her to Contact 1000.
Request - what the person asks for, in one of the app's four types: Information, Adjust (the person wants wrong data corrected), Export or Delete, with the verification code and date that prove her identity (for example PASSPORT, 14 June 2026). Each request gets a status (INI, AWAIT, WAIT, PROC, REJ, DONE) so the data protection officer keeps an eye on the deadline.
Verification code - how the requester's identity was checked (PASSPORT, ID_CARD, VIDEOCALL). The code and the date are documentation; no process inside the app performs the check itself.
GDPR details - on the Customer, Vendor, Contact, Employee and Resource cards, the origin of the record: a data source code (WEB), the campaign if the source allows it (Q3-2026), the collection reason (CONTRACT) and whether the record is excluded from segmentation.
Data processing consent and data processing purpose - a consent is a declaration the person gave (EMAIL "E-mail marketing"); a purpose is what may happen with the data (NEWSLETTER, MARKETING). Documenting the consent adds the purposes of its consent to the record; revoking it removes them again - and a purpose granted by two consents only disappears when the last of them is revoked.
Exclude from Segment - a flag on the contact's GDPR details saying the person may not be put in marketing segments. The app sets it automatically when no remaining purpose allows segmenting; it never removes it again if a user set it by hand.
Reschedule reason - why an action is moved to a new date. AUTO is used for automatic moves; DELAY ("Customer delay") is used when an action is moved because the customer asked for more time.
Job queue - the Business Central scheduler (with the JOBQ account) that the app uses to create scheduled actions, create and process suggestions and import details and consents automatically. If the job queue is off, these tasks can also be started by hand from the GDPR ToolBox Setup page or from the lists.
