Request deletion
Email our Privacy Officer at corporate@rtrsystems.com, or support@rtrsystems.com, with the subject Privacy deletion request. Include the email address on your RTR account, the organization or restaurant involved, and the information you want deleted. Don't send passwords, verification codes, tokens or unnecessary sensitive documents.
We reply within 30 days. Requests are free.
Disconnecting a connected system
An owner or administrator can disconnect any connected system for a restaurant in RTR's Connections screen. RTR deletes the stored token or login and stops reading from that system. Records already read stay with your organization's records until you ask us to delete them or your service ends. Disconnecting Clover in RTR does not uninstall the RTR app in Clover; uninstall it there too if you no longer use it.
Uninstalling the RTR app on Clover
Uninstalling the app from a Clover merchant ends RTR's access to that merchant's Clover data. To uninstall:
- Log in to your Clover dashboard with an account that has the Access App Market permission.
- From the left, select More > App Market, then My Apps.
- Find the RTR app and select Options > Uninstall app, then complete Clover's confirmation steps.
(Steps from Clover Help.)
| When | What happens |
|---|---|
| At uninstall | Clover notifies RTR. RTR stops reading that merchant's Clover data and, once Clover confirms the access has ended, deletes the merchant's Clover token from WorkOS Vault. The restaurant shows Clover as disconnected in RTR. |
| Days 1 to 30 | Export period. The merchant's owner or an administrator can email support@rtrsystems.com for a copy of the records RTR holds from its Clover account, in a common file format such as CSV. |
| Day 30 | RTR permanently deletes the data it received from Clover for that merchant from its production systems: payments and refunds, merchant details, and any employee records read from Clover. |
| By day 60 | Backup copies containing that data have expired. |
Error reports that happen to include technical details from that merchant expire within 90 days. Cashout records your organization keeps in RTR under its written agreement with us, such as closed cashouts and tip shares, stay available to your organization under that agreement and are deleted when your RTR service ends, as described below.
Uninstalling the app does not delete your RTR account or your organization's other restaurants.
Ending your RTR service
An owner or administrator can end the service by emailing support@rtrsystems.com. Any notice period or fees are set by your order.
| When | What happens |
|---|---|
| When the service ends | Sign-in stops for your organization's users. RTR stops reading your connected systems and deletes the stored tokens and logins for your connected systems. |
| Days 1 to 30 | Export period: ask us for a copy of your organization's records. |
| By day 60 | Your organization's records are deleted from RTR's production systems. |
| By day 90 | Backup copies have expired. |
We keep information longer only where a law requires it, and only for that reason. We confirm deletion in writing on request.
How we review requests
We may ask for information reasonably needed to verify your identity and locate the records. If a restaurant controls the records, such as your punches or tip shares, we will send your request to it or tell you how to contact it; the restaurant decides. RTR remains responsible for requests about its own records, such as your account or a demo request. We explain the outcome, including anything that must be kept and why, within 30 days.
Access changes are different from deletion
Removing a sign-in connection, phone number or organization membership stops access; it does not delete records. Cashout, tip-payment and security records stay with the restaurant's records until its service ends or it asks us to delete them; see the retention schedule. A request about one organization does not close your access to another.
How we delete
We delete information from our production database and our providers' systems, and let backup copies expire on their cycle; we do not restore deleted data from backups except to recover the service after a failure, and we delete it again if that happens. Where we anonymize information instead of deleting it, we remove or aggregate it so it can no longer identify anyone. See the privacy policy for our full retention schedule.