Data protection
Deleting your RestQ data
Last updated: 9 September 2026
This page explains how to request deletion of the personal data processed in RestQ, the Android, iPhone and web application by Dazeris Software, S.L.U.
If you just want an address: write to privacidad@dazeris.com with the subject “Data deletion — RestQ”. You do not need to go back to the app or reinstall it, and you do not need to know who to contact within your business: we take care of that.
1. How to request deletion of your data
RestQ is a professional application: accounts cannot be created from within the app. Dazeris creates them at the request of the business that subscribes to the service. Deletion works the same way, which is why the procedure is identical for everyone.
- Write to privacidad@dazeris.com stating the email address you use to sign in to RestQ, the name of the business or store and what you want deleted. We ask for nothing beyond what is needed to locate your account, and we use it for nothing other than handling your request.
- We acknowledge receipt and record the date your request came in.
- We consult your business, which is the controller for accounts and quotes and whose decision these data are. Dazeris processes them on the business's behalf, as a processor, and provides the assistance set out in the data processing agreement.
- We carry out the deletion and confirm what has been deleted and what has been kept, as detailed in the next section. Deleting the account removes the user profile and the membership of the business; we do not present it as a temporary suspension.
- Response time: one month from receipt of the request, under Article 12(3) of the General Data Protection Regulation, extendable by a further two months where the request is particularly complex. In that case we will tell you within the first month.
Diagnostics are under your control, from inside the app
Crash reports are optional and off by default. You can turn them on or off at any time under Settings → Privacy on Android and iPhone. When you turn them off, RestQ stops collecting them and deletes any reports still pending upload from the device. Declining them does not limit any feature of the app. No diagnostics are collected in the web version.
2. What is deleted and what is kept
| Type of data | What happens | Retention |
|---|---|---|
| User profile and membership of the business (display name, store, role and permissions) | Deleted. The deletion operation removes the profile and the membership of the business. | Kept while the account remains active, or until the business orders its deletion. |
| Sign-in data: email address, credentials and IP addresses (Firebase Authentication) | Deleted when the account is deleted. | Logged IP addresses are kept for a few weeks. The remaining authentication data is kept until deletion of the account is requested; Google completes deletion from its live systems and backups within a maximum of 180 days. |
| Quote authorship (internal identifier of whoever created it) | Kept within the quote, but unlinked: once the user is deleted, that identifier no longer resolves to any profile. It contains no one's name or email address. | Follows the retention of the quote itself, under the business's instructions and the service agreement. |
| Quotes and other business working data (products, sizes, options, prices and the free-text name or reference field) | Kept: this is business data, not account data. Only the business can order its deletion. | Kept while the business's subscription remains active and under its instructions. Return or deletion at the end of the service is governed by the data processing agreement. |
| Audit log (users added and removed, permission and price changes, and shops opened, renamed and closed) | Kept. The log is immutable while it exists: entries are neither modified nor deleted one by one. It records the action, its date, the item affected and the internal identifier of whoever performed it; it contains no one's name or email address, and once an account is deleted that identifier no longer resolves to any profile. The price change history is a separate record, in the row below, and that one does keep the name. | Security and traceability record. Each entry is deleted automatically 24 months after its date, and the deletion is recorded in the log itself. An exceptional correction —for example, removing a personal data item filed in error— is noted in the entry itself. |
| Price change history (point value, margins and purchase discounts) | Kept. Each entry records the date, the previous value, the internal identifier and the display name of whoever made the change, and cannot be modified or deleted entry by entry. Once the account is deleted, that name remains on the entries already recorded. | It is the trail with which the store explains why a price changed. Retained for as long as the store keeps the service subscribed, together with the rest of its working data; return or deletion on termination is governed by the data processing agreement. |
| Crash reports already sent to Firebase Crashlytics (stack traces, minidumps and associated identifiers) | Cannot be deleted individually. RestQ does not attach your name, email address or account identifier to these reports, so Dazeris holds no key with which to find yours, and will not ask you for additional data solely to create that link. They are deleted when their retention period expires. | Google keeps them for 90 days before beginning their deletion from live systems and backups. |
| Log messages sent to Crashlytics | Likewise cannot be located individually, for the same reason. | Google does not publish a separate retention period for these messages, and RestQ has no retention setting of its own. |
| Diagnostic reports pending upload, on the device | Deleted when you turn diagnostics off under Settings → Privacy, and also on every launch where no consent is present. | Immediately. |
| Local copy on the device (working data, preferences and session) | Deleted. On Android, automatic backup and device-to-device transfer are disabled, so this copy does not leave the handset. | Cleared on the next launch of RestQ after signing out. |
| Website data (demo request form) and support correspondence | Deleted at the data subject's request. Here Dazeris is the controller, so the decision is ours and does not depend on the business. | Kept for as long as necessary to handle and document the request and, afterwards, blocked for the periods during which legal liability may arise, after which they are deleted. |
3. What we cannot do, stated plainly
- Dazeris does not decide on its own about your account or your quotes. The controller is your business. We carry out the deletion, but the decision on that data is theirs.
- Specific crash reports already sent to Crashlytics cannot be deleted, because they are not linked to your account: that is precisely the measure that prevents a crash from being tied to an identified person. They are deleted once the periods in the table above have elapsed.
- The audit log is not deleted when the account is deleted, as it is a security and traceability record: its entries are deleted automatically 24 months after their date. It contains no names or email addresses, and once an account is deleted its identifier no longer leads to any profile.
4. Contact and complaints
Dazeris Software, S.L.U. · Tax ID B93844595 · Calle Panaderos, 8, 4.º Pta. D · 02400 Hellín (Albacete) · privacidad@dazeris.com
If you are not satisfied with our response, you may lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos).
Full information on what data RestQ processes, on what legal basis and for how long is in the privacy policy.