Erasing a user, and your users' data

Delete everything Tamr holds for one of your users with one API call, and how long Tamr keeps conversations, orders and webhook deliveries.

When one of your users asks to be forgotten, Erase a user deletes what Tamr holds for them, with a secret key that has the diner:sdk permission. Wire it to your own account deletion.

It deletes the user's profile with Tamr, their sessions, conversations, ratings, the orders you sent, unspent launch codes and the webhook deliveries that named them. An open chat finds its session gone on its next request. It is safe to call again: erased is false when there was nothing.

What Tamr knows about your users

  • Tamr knows your user only by the id you put in sub and externalUserId. Never send a name, email or phone number there.
  • Orders you send are kept for 12 months from placedAt, then deleted. A restaurant's agreement with Tamr can set a shorter period. A rating outlives its order only as an anonymous rating of the dish.
  • Webhook deliveries are kept for 30 days.
  • Conversations, from your app or any other channel, are kept for 365 days after they close, then deleted. The restaurant can choose a shorter period in its privacy settings, and an agreement with Tamr can set a fixed one.
  • Erasing a user deletes all of the above for them at once. A diner can also ask Tamr directly to forget them.
  • This data falls under the restaurant's privacy policy, with Tamr as processor, as for its QR menu guests.