Organization Settings

View and modify details at the Organization level, such as Org name and Data Retention settings

Organization Name

View and Change the name of the Organization.

Organization ID

View and copy the Organization ID. This could be helpful when making API requests.

Data Retention & Privacy Policies

This is where you can manage how Forget API persists your Deletion Request data. With every Deletion Request that gets raised through Forget API, an identifier (email, user ID etc.) must be provided. Therefore, each Deletion Request contains a piece of identifiable information for a user.

These settings allow you to specify exactly how Forget API manages that idenfitable customer data that is stored in Forget API’s system.

Please note: All Data Retention and Hashing happens at midnight (UTC) every day.

Request Data Retention

This setting dictates how long after a request completes, that the Deletion Request is stored in Forget API’s system, specifically the Identifier information.

When a Deletion Request is deleted from Forget API’s system, we will delete (nullify) the identifier of the Deletion Request and remove any audit log payloads for any sub-request. This action is irreversible.

Deletion Policy: From the dropwdown, you can select the following options

• Never Delete - This will tell Forget API to never delete the request from Forget API’s system.
• Delete from Forget API - This will tell Forget API, that after a Deletion Request is completed, to delete the information of the Deletion Request.

Days after request completion: This option is only applicable if the previous dropdown is set to Delete from Forget API. From the dropwdown, you can select the following options

• Immediately - This will delete the request during the next opportunity where Forget API processes Data Retention rules (midnight UTC)
• 3 Days - Forget API will wait 3 Days after the request has been completed to remove the request information from its system
• 7 Days - Forget API will wait 7 Days after the request has been completed to remove the request information from its system
• 15 Days - Forget API will wait 15 Days after the request has been completed to remove the request information from its system

Identifier Privacy Policy

This settings allows you to dictate if you would like Forget API to hash the identifier used for a Deletion Request. Once the identifier value is hashed, the value can not be identified as a specific user, but for auditing purposes you will be able to prove that requests for a given user have been completed. See the User Lookup section for more details.

Hashing Policy: From the dropwdown, you can select the following options

• No Hashing - This will tell Forget API to not hash the identifier for deletion requests.
• Hash Identifier - This will tell Forget API, that after a Deletion Request is completed, to hash the identifier of the Deletion Request.

Days after request completion: This option is only applicable if the previous dropdown is set to Hash Identifier. From the dropwdown, you can select the following options

• Immediately - This will hash the identifier during the next opportunity where Forget API processes hashing rules (midnight UTC)
• 3 Days - Forget API will wait 3 Days after the request has been completed to hash the identifier of the Deletion Request
• 7 Days - Forget API will wait 7 Days after the request has been completed to hash the identifier of the Deletion Request
• 15 Days - Forget API will wait 15 Days after the request has been completed to hash the identifier of the Deletion Request