Data Subject Requests

When a customer asks you to delete their data, stop using it, or provide a copy, WasteNot helps you handle the part of that request that relates to your WasteNot organization. These are called data subject requests, or DSRs.

Where to find privacy settings

Open Data & Privacy under Settings. This area is available to your organization's Owner and Admins and contains two sections:

• Data Subject Requests — Create requests and review the results for each email address, phone number, or customer ID.
• Suppressions — Manage identifiers used to block matching data from future imports.

Choosing the right request

Delete: remove existing records

A Delete request removes matching event records already stored in WasteNot for your organization. Events include activity such as orders, email engagement, and SMS messages imported from your data sources.

Deletion does not create a suppression. If you also need to prevent the customer's data from being imported again, create an Opt-out request as well.

Opt-out: block future imports

An Opt-out request adds the supplied identifiers to your organization's suppression list. WasteNot uses this list to filter matching data during imports.

An opt-out does not delete existing event records. If the customer wants their existing data removed too, create both a Delete request and an Opt-out request.

Access: ask for help retrieving data

For a customer who wants a copy of their data, contact support to coordinate an Access request. WasteNot can track this request type, but the request page does not currently provide a downloadable data export. Confirm the response with support before treating the customer's request as fulfilled.

Starting a request

1. Open Data Subject Requests under Settings → Data & Privacy.
2. Click New request.
3. Select the Type: Delete, Opt-out, or Access.
4. Set Due at if you want to record a deadline.
5. Under Identifiers, select the identifier type and enter the customer's email address, phone number, or external customer ID.
6. Click Add identifier for each additional identifier the customer uses.
7. Review the details and click Save request.

Include every known identifier when you start. For example, a customer may use one email address for orders and another for a newsletter. WasteNot processes each identifier separately; supplying one does not automatically find every other identifier belonging to that person. Each request supports up to 10 identifiers.

Once a request is saved, you cannot add identifiers through the request form. If you discover another identifier, create an additional request for it.

What happens after filing

Requests are scheduled to begin processing one day after they are created. This gives you time to review the details before processing starts. The Due date records your deadline; it does not set the processing start time.

To check progress:

1. Open Data Subject Requests.
2. Find the request by its type, creation date, and due date.
3. Click the request to open its details.
4. Review the Jobs table, which contains one row for each identifier.

The request's State shows its progress:

• Pending — Waiting to begin processing.
• Processing — Processing is underway.
• Completed — The processing workflow has finished. Review the individual rows for the outcome of each identifier.

In the Jobs table, check State, Records touched, and Completed for each row. For deletion, Records touched is the number of event records removed for that identifier, not a count of unique customers. A zero can mean that no matching records were found. If a row is cancelled, the request fails, or the result is unexpected, contact support before closing out the customer request.

The original identifiers on the request are scheduled to be cleared seven days after processing completes. The page then displays Redacted in place of those values while retaining the processing details.

Reviewing suppressions

Open Suppressions to review the identifiers on your organization's suppression list. Owners and Admins can also add suppressions directly:

1. Click New suppression.
2. Select the identifier Type: email, phone, or external ID.
3. Enter the identifier in Value.
4. Click Save, then repeat for any other identifiers the customer uses.

Suppression matching depends on the identifiers in your data. Include all known email addresses, phone numbers, and customer IDs, and contact support to confirm coverage if your sources identify the same person in different ways. Suppression changes take effect as they sync through WasteNot's import process.

The Clear PII action hides the original identifier while keeping the stored matching value, so suppression continues to work. Delete removes the suppression entry and allows matching data to be imported again.

Frequently asked questions

Does this delete data from Shopify, Klaviyo, or my ad platforms?

The deletion workflow described here removes matching event records in WasteNot. Handle requests in your original data sources and ad platforms through those services' privacy processes as well.

Can deleted data come back on a later sync?

If the data remains in a connected source, it can be imported again. Pair deletion with opt-out when you need to remove existing records and block future imports for the supplied identifiers.

What if I filed the wrong request?

If the request is still Pending, open its ⋮ menu and choose Edit to change the type or due date. Identifiers cannot be changed through the edit form; if those are wrong, delete the pending request and create a replacement. If processing has already begun, contact support@wastenot.io. Once processing has begun, the request can no longer be edited, and completed deletions cannot be undone from the request page.

Should I delete a completed request?

Keep the request if you need its processing history. The Delete action on a request removes it from your request history; it does not file a customer data deletion request or undo work already completed.