The retention period lets you automate the anonymization of a service request submitter’s name, email address and phone number. The setting applies to the entire organization: it is not configured separately for each service request type or public form. It can also affect requests that are still in progress and cut off email communication with their submitters.
Setting the retention period
Make the change in the browser using an account with permission to edit service request settings. A local administrator has this permission.
- Open Manage tasks → Service requests → Service request settings and select the Settings tab.
- In the Basic info section, enter a whole number of at least 1 in the Submitter personal data retention (days) field. An empty field means automatic anonymization is disabled.
- Select Update service request setting at the bottom of the form.
- Reopen the settings and check that the intended number of days was saved.
Choose a period that keeps the submitter’s contact details available for as long as they are needed to handle the request. Enabling a short retention period or shortening the period may cause old requests to be processed as early as the following night. Saving the setting does not anonymize data immediately.
When are requests processed, and which requests are included?
Processing is queued each night at midnight in the organization’s time zone. The queue may delay completion. Automatic processing applies to active Spotilla customer accounts with a retention period set.
The cutoff is calculated by subtracting the configured retention period from the start of the processing day. Only requests created before the cutoff that have not yet been marked as anonymized are included. A request’s age is based on its creation time, not its completion time or last modification.
For example, with a one-day retention period, processing on 5 October 2026 uses 4 October 2026 at 00:00 in the organization’s time zone as the cutoff. A request created on 3 October can be processed if it meets the other conditions. A request created exactly at 00:00 on 4 October or later is not yet included in this run.
The request’s status does not restrict processing: open, in-progress, on-hold, completed, cancelled and forwarded requests may all be included. A single run processes up to 10,000 requests per organization, so a large backlog may require several nights.
Exception for user accounts
A request is not anonymized if the submitter’s stored email address matches the email address of any user account in the organization. The comparison ignores capitalization and leading or trailing spaces. It is not limited to active user accounts.
The exception is based on the address, not how the request was submitted. The standard creation form in the Android and iOS apps fills in the submitter’s name and email address from the signed-in user’s details, so these requests are usually excluded from processing. A request submitted through a public form is also excluded if its email address matches a user account.
What does anonymization change?
The submitter’s name and email address are replaced with anonymization values, and the phone number is cleared. For a Finnish-language customer account, the name becomes GDPR Tyhjennetty and the email address becomes gdpr.tyhjennetty@spotilla.com. The replacement values depend on the customer account’s language.
External email addresses in conversations associated with the processed request are also replaced, unless an address matches a user account in the organization. The anonymization time is recorded on the request and in its change history. The request’s last modification time also changes, and the submitter’s fallback name stored in the creation event is replaced.
The request is not deleted, closed or reassigned. This setting does not clean its title, description, additional fields, comments, conversation text or attachments. These may still contain personal data.
Limits of history cleanup
For processed requests, history cleanup removes the name, email and phone values stored in the creation event, as well as the corresponding fields in record copies stored in modification and deletion events. However, it does not remove the old and new values recorded for contact detail changes in modification events. If contact details have been changed, personal data may therefore remain in the change history visible to the customer.
History cleanup is performed separately after the request’s contact details have been replaced and the anonymization time has been recorded. History cleanup can fail without undoing the request’s anonymization marker. The marker alone therefore does not prove that history cleanup has finished, and a subsequent nightly run does not automatically retry the cleanup.
A request already marked as anonymized is excluded from subsequent runs even if its contact details are later changed. The marker indicates earlier processing and does not guarantee that the current contact details are still anonymized. This feature is also not a general cleanup of the history of requests that have already been deleted.
Effect on communication
No email is sent to the replacement addresses used for anonymization. Conversation notifications and notifications about status, responsibility and completion that rely on the original address stop for that address, even if the notification is enabled in the settings. Notifications can still be sent to other remaining recipients according to their settings.
Anonymization does not itself invalidate a previously sent conversation reply link. The link can still open the reply page if it is valid, the request exists and its status is not Completed, Cancelled or Forwarded. If needed, read about follow-up communication for a public service request.
Checking the result
- After processing, open Manage tasks → Service requests → Service requests and refresh the table data, for example by reopening the page.
- Open the column visibility selector using the column icon at the end of the table’s column headers. Show the Personal data anonymized at column, which is hidden by default. A timestamp in this column indicates that the request has been processed; an empty value means the request has not been marked as anonymized. The timestamp does not confirm that the separate history cleanup has finished.
- Open the request’s details using its title link. On the Basic info tab, check the submitter’s replacement name and email address and the empty phone number.
The request detail views in the Android and iOS apps display the replacement contact details retrieved from the server. A dash is shown for an empty phone number. Check the anonymization time in the browser table described above.
The confirmation that the setting was saved does not by itself indicate that processing has finished. If a request you expected to be anonymized has not yet been processed, check its creation time, the retention period and the email exception for user accounts. Also allow for delays in the run and a large processing volume. If a timestamp is shown but the contact details do not match the replacement values, they may have been changed after processing.
Disabling the feature
To disable automatic anonymization, clear the retention period field and save using the same Update service request setting button. This prevents processing in future runs but does not restore contact details or history data that have already been replaced. Increasing the retention period does not restore data either. Disabling the public form alone does not stop anonymization.
Publishing the public form and configuring its options are covered separately in Public service request form settings.