Data deletion and account closure

1. Who handles your request?

For your QORLYNT user account, our contract/billing records and our own support requests, contact Smart TB Tech UG (haftungsbeschränkt), Oberviehhausen 7, 84533 Haiming, Germany; support@qorlynt.com; telephone +49 8678 4499811.

If you booked with or contacted a business using QORLYNT, that business generally controls the related contact/appointment data. Contact it directly or ask us to identify the relevant business. As processor, we assist with authorized handling; you do not need your own QORLYNT login.

Business administrators may act on company data only within their authority. Removing a staff member from an organization does not necessarily delete their entire user account or other memberships.

2. Request deletion, including without portal access

Send your request to support@qorlynt.com, preferably from a known account/contact address. Identify QORLYNT, the relevant business/account, your relationship to it and the desired scope: specific data, a contact, support ticket, user account or the entire organization’s dataset. Free-form wording is sufficient; no special form is required.

If you no longer have access to the previous e-mail address, tell us so we can arrange appropriate alternative verification. Do not send passwords, PINs, API keys, access tokens or full payment details. Identity document copies are not required as a blanket rule.

The e-mail button only opens your mail application. Your actually sent message constitutes the request; no immediate deletion is triggered. You may expressly request contract cancellation in the same message.

Signed-in users can also initiate deletion of their personal account under “My profile & security”. This requires a recent sign-in and confirmation of their own e-mail address and the word “DELETE”.

Self-service is blocked if the stored membership status identifies the person as the sole owner of an organization. If authorized, that person can first appoint another owner. If their membership has expired or this is not possible, contact us by e-mail to have the erasure request assessed; a statutory erasure right remains unaffected.

Technical processing continues after the request; an identity-provider error may require manual review. A specific subject line, your own QORLYNT account or use of the email button is not required for a valid request. Provide only the details needed to identify the data concerned. If you initially seek only access, rectification or restriction, say so; such a request is not treated as an instruction to erase.

3. Stop messages or disconnect integrations

A contact block or supported STOP ends further communication covered by that block. Messages already sent or in transit cannot reliably be recalled. The contact and necessary evidence may remain.

Authorized users can disconnect individual channels or calendar connections. QORLYNT disables associated access for future normal use; the current process may retain encrypted credential records marked as revoked. Pending or uncertain calendar changes may require resolution first.

Disconnecting does not delete provider events/messages already transmitted and does not necessarily revoke every external app permission. Where needed, also review Google/Microsoft permissions, Meta Business integrations or Telegram bot authorization. Specifically request removal of remaining credential records if that is your intention.

Deleting a separately configured external integration removes its configuration, tokens and external identifier mappings and stops further actions through that connection. Contacts and appointments already created remain separate business records. Events, processing receipts, error records, usage data and copies held by recipients must also be examined for a comprehensive erasure request. Deleting an integration does not itself terminate a separately purchased add-on subscription.

4. Individual contacts and configured retention

The portal contact-cleanup function removes or clears contact fields, chat links, message content, media links and task content within its defined scope. Future active bookings may initially block self-service cleanup and require separate resolution. This does not exclude a statutory erasure request.

Technical contact identifiers, historic booking references, synchronization, execution or evidence records may remain. Clearing a media link does not automatically remove the uploaded file from object storage. A separate media-deletion feature is not currently available; identify affected uploads in your deletion request. The function therefore does not demonstrate complete anonymization of all data. Specify if you require comprehensive deletion; we then assess further datasets.

Configurable content retention affects certain message, AI and related operational data. It does not automatically delete contacts, all appointments, contract documents, backups or external-provider data. Normalized contact rows in unfinished import jobs are a separate dataset: cancelling removes uncommitted preview rows, and regular cleanup removes staging data after seven days. Anonymizing a contact removes matching staged rows and may end affected open jobs. Contacts already committed require separate erasure. Later re-imports or continuing calendar imports may reintroduce data; stop the relevant source where necessary.

5. Complete account or organization deletion

After verifying identity, authority and scope, we coordinate necessary return/export and deletion. Depending on scope, this includes authentication, memberships, company/contact data, appointments, messages, AI caches, automations, connections and support copies. An e-mail initiates handling, not a guaranteed immediate automatic full purge.

Self-service deletion of a personal account first blocks further sign-ins and revokes sessions. After successful handling by the identity provider, the personal e-mail address, display name and profile preferences in the QORLYNT user account are removed or anonymized, memberships revoked and attributable e-mail addresses in accepted invitations cleared. Technical references may remain under a pseudonymous identifier; operational company data, billing records and backups must be assessed separately by purpose, responsibility and retention. Deleting a personal account does not automatically erase company data or cancel a subscription. Deleting an entire organization can affect other team members and current bookings. We therefore clarify whether the request concerns one user or the full company dataset. Later deletion cannot undo actions already transmitted.

A contact export is not a complete platform export. Request any additional data you need before final deletion. Statutory portability and switching rights remain. Legally required deletion is not made conditional on paying outstanding amounts as a blanket rule.

6. Response period and outcome

Statutory periods apply to data-subject requests: we respond without undue delay, generally within one month of receipt. Where complexity or request volume permits an extension, we explain the reason and extension of no more than two further months within the first month.

Identity/authority checks protect against unauthorized requests and must not make exercising rights unnecessarily difficult. We ask specifically for missing necessary information.

We explain the action taken and any remaining data and reasons. If we refuse or limit a request, we explain the reasons and complaint/judicial remedy options. A response deadline is not a blanket promise that every backup copy worldwide disappears on the same day.

Where Article 17 GDPR requires erasure and no exception applies, erasure takes place without undue delay. The response period does not permit routinely waiting a month. Data-subject requests are normally free of charge; a reasonable fee or refusal for manifestly unfounded or excessive requests is permitted only under Article 12(5) GDPR. The controller bears the burden of demonstrating that exception.

7. Legally retained records and backups

Necessary accounting, tax and business records may remain under statutory duties, and necessary evidence for establishing or defending specific legal claims. Not all messages, contacts or audit records automatically share the same statutory retention period. Scope and duration must be justified for each remaining dataset.

Records retained for a limited purpose are not used for ordinary customer communication and access is restricted. Simply marking data as deleted is insufficient if unlawful use remains possible.

Live-data deletion and backup deletion are separate. Versioned backups can have different expiry dates for current and older object versions; complete removal may occur later. Required deletions must be reapplied after restoration. On request, we explain relevant backups and their cleanup status.

A record needed to honor a marketing objection or messaging block may be retained in a form limited to what is necessary so that later imports do not override it. Such a record must not be used as a pretext for further advertising or for retaining complete conversation histories.

8. Data held by connected services

Deleting data in QORLYNT does not automatically delete data at WhatsApp/Meta, Telegram, Google, Microsoft, OpenAI, Twilio, Stripe, external mail/media providers or other connected services. Delivered messages, external calendar events, accounts, invoices and payment methods may remain.

Where we control the relevant processing, we meet necessary deletion/notification duties toward our processors and recipients. For processing on customer instructions, we assist the responsible business. Independent provider processing is subject to that provider’s additional rights and deletion procedures.

Revoking provider authorization, removing a QORLYNT connection and deleting historic provider data must each be assessed separately.

9. Cancellation, privacy rights and questions

Data deletion alone is not automatically subscription cancellation. Conversely, cancellation does not immediately delete all data. Explicitly tell us if you want both; statutory rights remain independently applicable.

Our privacy policy explains further rights, legal bases and the option to complain to the Bavarian supervisory authority. Questions: support@qorlynt.com; technical support: support@qorlynt.com.

A request clearly seeking final closure of the entire paid platform account and cessation of use is also treated as cancellation at the earliest permissible date. We clarify any uncertainty about scope. Section 14 of the terms and mandatory statutory rules additionally govern provider switching and the related contract termination, retrieval period and erasure.