A clear path out, protected against mistakes and unauthorized deletion.

This Account Deletion Policy explains how KOMERRA Technologies Limited handles requests to close an Account, remove a user from a Workspace, delete a business Workspace, erase personal data, disconnect integrations, and remove associated public pages.

It also explains the safeguards used to prevent an unauthorized person, former staff member, compromised Account, or mistaken request from permanently deleting business records.

Account deletion is different from signing out, deactivating a feature, removing a staff member, disconnecting an integration, hiding a public page, cancelling a subscription, or exercising a privacy right concerning a particular category of personal data.

This Policy should be read together with the Privacy Policy, Terms of Service, Data Retention Policy, Refund and Cancellation Policy, Security & Trust page, Data Processing Agreement, Subprocessors page, and any Workspace-specific agreement.

KOMERRA is operated by KOMERRA Technologies Limited, a company registered in the Federal Republic of Nigeria with registration number 9681120.

Questions and deletion requests may be sent to support@komerra.app.

Use “Account Deletion Request” in the subject for a request to close an Account or delete a Workspace.

Use “Privacy Request” where you are requesting erasure, restriction, correction, access, portability, objection, or another personal-data right without necessarily closing the Account.

“Account” means an individual KOMERRA login and user profile.

“Workspace” means the business environment containing business records, members, customers, products, orders, files, documents, settings, Credits, integrations, Mini Store information, Trust Passport information, and related activity.

“Workspace Owner” means a person with the highest available ownership authority for a Workspace.

“Authorized User” means a staff member, contractor, adviser, administrator, or other person granted access to a Workspace.

“Account deletion” means closure of an individual user Account and deletion or anonymization of eligible Account-level information.

“Workspace deletion” means deletion or anonymization of an eligible business Workspace and the tenant-scoped records associated with it.

“Membership removal” means removing a user’s access to a Workspace without deleting the Workspace or other members’ records.

“Personal-data erasure request” means a request concerning personal data under applicable data-protection law, which may be narrower than deletion of the entire Account or Workspace.

“Irreversible deletion” means the stage at which active production records have been permanently deleted, anonymized, cryptographically rendered inaccessible, or otherwise made unavailable for ordinary recovery.

An individual Account and a business Workspace are separate objects.

Deleting an individual Account does not automatically delete a Workspace where another active owner or authorized administrator remains responsible for that business.

Removing a staff member ordinarily removes that person’s future access but does not delete the business records that the person created while acting for the business.

A Workspace may contain records relating to customers, staff members, suppliers, owners, payment transactions, documents, communications, and other people whose rights must also be considered.

KOMERRA therefore determines whether a request concerns the requester’s personal profile, Workspace membership, a solely owned Workspace, a shared Workspace, or particular personal data before taking irreversible action.

Deactivation temporarily prevents access while preserving the Account or Workspace for possible restoration.

Deletion is intended to remove or anonymize eligible information and may become irreversible.

KOMERRA may offer temporary deactivation, session revocation, integration disconnection, public-page hiding, or membership removal where those options better match the user’s objective.

A security restriction, suspension, or temporary lock does not by itself constitute deletion.

A user should select deletion only where permanent closure is genuinely intended.

Deletion may permanently remove information that the business needs for customers, accounting, tax, warranty, delivery, dispute, legal, operational, or historical purposes.

Before submitting a request, review the affected Account and Workspace and complete any reasonable preparation.

Eligible users should export required information before irreversible deletion begins.

Available exports may depend on the user’s role, permissions, plan, feature, record type, provider, and current product capabilities.

An export may exclude secrets, internal security information, another person’s private data, provider-protected data, or information the requester is not authorized to access.

A data-portability request may be submitted separately where applicable.

KOMERRA does not guarantee that deleted information can be reconstructed from documents previously generated, messages previously sent, or records retained by third parties.

A signed-in user may submit an Account deletion request through the available Profile, Account, Privacy, or Security settings.

The request should be initiated from the Account that is to be deleted whenever possible.

If Account access is unavailable, the requester may contact support from the email address associated with the Account.

The requester should identify the Account, affected Workspace or Workspaces, intended scope, and whether the request concerns Account closure, Workspace deletion, membership removal, or personal-data erasure.

Submitting a deletion request does not immediately prove identity, ownership, or authority.

Where a requester cannot sign in, KOMERRA may require reasonable evidence connecting the requester to the Account or Workspace.

Verification may include control of the registered email address, telephone verification, previous Workspace information, administrator confirmation, business ownership evidence, or another proportionate method.

KOMERRA will not request a password, bank PIN, card security code, private key, one-time password, or recovery code through ordinary support communications.

Where the registered email Account is also compromised, additional verification may be required before any destructive action is accepted.

KOMERRA may refuse or pause a request where identity or authority cannot be established safely.

Deletion is a high-risk instruction because an unauthorized request could permanently destroy valuable business records.

KOMERRA verifies the requester before approving deletion or disclosure connected with deletion.

Verification should be proportionate to the risk and should avoid collecting more identity information than is reasonably necessary.

KOMERRA may request stronger verification where the Account controls a Workspace, staff access, public business pages, Purchased Credits, verification status, sensitive records, or connected providers.

Identity documents will not be requested automatically where a less intrusive verification method is sufficient.

Information supplied for verification is processed for the deletion review, security, fraud prevention, and legal accountability purposes described in the Privacy Policy.

Identity verification establishes who the requester is. Authority verification establishes whether that person is permitted to delete the affected Account, Workspace, or records.

A staff member may be authorized to use business records without being authorized to delete the business.

A billing administrator may manage payments without being authorized to delete customer records.

A technical administrator may manage integrations without owning the legal entity operating the Workspace.

KOMERRA may require confirmation from an existing Workspace Owner, director, proprietor, partner, trustee, authorized representative, or other appropriate person.

A deletion request may be paused where ownership, employment, partnership, directorship, or authority is genuinely disputed.

A requester may act through an authorized representative where applicable.

KOMERRA may request evidence that the representative has authority to make the specific deletion or privacy request.

General access to an email Account, device, business premises, social page, or staff role does not automatically establish authority to delete the Account or Workspace.

KOMERRA may communicate directly with the Account holder or Workspace Owner where necessary to confirm the instruction.

Verification information will be limited to what is reasonably necessary for the request.

Where the requester is the verified sole owner of a Workspace and no other person has an independent ownership right, the Account and Workspace may be eligible for coordinated deletion.

The request remains subject to review for pending transactions, disputes, legal obligations, fraud concerns, third-party rights, provider dependencies, and records that must lawfully be retained.

Deleting the sole owner’s Account without addressing the Workspace could leave the Workspace without an authorized controller.

KOMERRA may therefore require the requester to confirm whether the Workspace should also be deleted or transferred.

A shared Workspace is not deleted merely because one owner, administrator, or member requests deletion of their individual Account.

Where another active owner remains, the requester’s membership and eligible Account-level information may be removed while the Workspace continues.

Business records created by the departing user may remain as records of the business, subject to minimization, attribution, retention, and applicable privacy requirements.

Where appropriate, the departing user’s name or direct identifier may be replaced with a neutral identifier while preserving the integrity of business, audit, accounting, or security records.

A Workspace Owner may be required to transfer responsibilities before the requester’s Account can be fully closed.

Removing a staff member is generally an access-management action rather than Account or Workspace deletion.

A Workspace Owner or authorized administrator may remove the staff member’s Workspace membership according to available permissions.

Membership removal revokes future access to the relevant Workspace but does not erase orders, documents, messages, approvals, audit events, or other records lawfully belonging to the business.

The removed user may still request deletion of eligible Account-level personal data through their own KOMERRA Account or support.

A staff member cannot delete a Workspace merely because they created records or were previously given administrative access.

A Workspace Owner who wishes to leave while the business continues should transfer ownership through the approved process rather than delete the Workspace.

The incoming owner may be required to verify their Account, authority, and acceptance of applicable terms.

KOMERRA may prevent ownership transfer while a security incident, payment dispute, court order, fraud review, or genuine control dispute remains unresolved.

An ownership transfer does not automatically transfer personal credentials, private authentication methods, or unrelated user information.

After a valid transfer, the former owner may remove their membership or request deletion of their individual Account.

Where a Workspace has no other eligible owner and the verified owner requests Account deletion, KOMERRA may require coordinated Workspace deletion or another lawful ownership arrangement.

KOMERRA will not knowingly leave an active business Workspace under the control of an unauthorized person.

The Workspace may be restricted while ownership and deletion are resolved.

Public pages may be hidden where continued publication would be misleading, unauthorized, or unsafe.

A customer whose information appears in a business Workspace should ordinarily direct an access, correction, objection, or deletion request to the business that collected and controls the information.

The customer’s request does not normally require deletion of the business’s entire KOMERRA Workspace or the business owner’s Account.

Where KOMERRA acts as a processor for the business, KOMERRA will assist the business with eligible requests according to the Data Processing Agreement and applicable law.

KOMERRA may forward a customer request to the relevant business after taking reasonable steps to identify the correct Workspace.

KOMERRA may act directly where the request concerns information for which KOMERRA independently acts as controller, such as platform Account, security, billing, or support information.

KOMERRA may act as a data controller for Account administration, platform security, billing, fraud prevention, verification, support, service operation, and similar purposes.

A business generally acts as controller for customer, staff, supplier, order, communication, product, delivery, and other information it places in its Workspace.

KOMERRA generally processes that Workspace information on the business’s documented instructions.

Deletion obligations therefore depend on the relevant information, purpose, legal role, Workspace instruction, and applicable law.

Deleting an individual KOMERRA Account does not authorize KOMERRA to disregard the lawful instructions or legal obligations of another controller.

Deletion requests enter a review process before irreversible action begins.

The review is intended to confirm identity, authority, ownership, scope, shared records, pending transactions, security concerns, legal obligations, provider dependencies, and the rights of other people.

The review may include Account information, Workspace roles, ownership history, authentication events, payment records, Credit balances, integrations, public pages, disputes, support cases, and relevant legal restrictions.

A review does not mean that KOMERRA intends to refuse the request.

Where the request can be completed only in part, KOMERRA will identify the general categories that can be deleted, anonymized, restricted, or retained.

Where supported, KOMERRA may display a deletion status such as Requested, Verification Required, Under Review, Scheduled, Processing, Completed, Cancelled, or Restricted by Legal Hold.

A request marked as Requested or Under Review has not yet resulted in irreversible deletion.

A request marked as Processing may already have triggered revocation, cleanup, provider instructions, or deletion jobs that cannot safely be reversed.

Completion means that the applicable active-system deletion and anonymization work has been performed, subject to protected backups and permitted retained records.

Where the product displays a cancellation option, the verified requester may withdraw the request before irreversible deletion begins.

A cancellation request may also be submitted to support where the original request has not progressed beyond the reversible stage.

KOMERRA may require renewed identity verification before accepting cancellation where the Account may be compromised.

Cancellation is not guaranteed after deletion jobs, provider revocations, anonymization, or irreversible cleanup have begun.

Once irreversible deletion is complete, the original Account, Workspace, files, identifiers, or history may not be recoverable.

KOMERRA may apply temporary restrictions while a high-risk deletion request is reviewed.

Restrictions may include revoking sessions, preventing ownership transfer, disabling new staff invitations, pausing exports, hiding public pages, freezing integration changes, or requiring additional authentication.

Protective restrictions are intended to prevent unauthorized deletion, record tampering, fraud, or transfer of control.

They do not necessarily mean that the requester violated the Terms of Service.

A Workspace may have pending orders, deliveries, refunds, warranties, complaints, customer balances, or other obligations when deletion is requested.

KOMERRA may ask the business to export, complete, transfer, cancel, or otherwise address those obligations before deletion.

Deletion does not cancel the business’s contracts or legal responsibilities to customers, suppliers, staff members, regulators, or other parties.

A business must not use Account deletion to conceal non-delivery, avoid a refund, destroy evidence, or escape a lawful obligation.

Account or Workspace deletion does not automatically create a refund for Purchased Credits, subscriptions, plans, or completed actions.

Unused Purchased Credits are handled under the Refund and Cancellation Policy and applicable law.

Promotional Credits, included usage, trial Credits, gifts, and bonuses ordinarily have no cash redemption value.

KOMERRA may delay final deletion where a payment remains pending, disputed, charged back, reversed, or under fraud review.

Payment, refund, tax, accounting, provider, and Credit-ledger records may be retained where required for lawful business and compliance purposes.

KOMERRA may temporarily suspend deletion of relevant information where the information is reasonably required for an active legal claim, regulatory requirement, court order, investigation, security incident, payment dispute, chargeback, fraud review, or defense of rights.

A legal hold applies only to information reasonably connected with the relevant purpose.

Information subject to a hold should be restricted from unrelated use and protected according to its sensitivity.

When the lawful retention need ends, the information will return to the applicable deletion or retention process.

A legal hold does not permit indefinite retention without review.

The right to deletion or erasure is important but may not apply to every record in every circumstance.

KOMERRA may retain limited information where processing remains necessary for a legal obligation, establishment or defense of legal claims, fraud prevention, security, accounting, tax, regulatory reporting, contractual performance, or another lawful purpose.

KOMERRA may also preserve information where deletion would unlawfully interfere with another person’s rights or remove records that another controller is required to maintain.

A refusal or limitation should identify the general reason and available review or complaint path without exposing confidential security information or another person’s data.

Once deletion is approved and reaches the applicable processing stage, KOMERRA begins coordinated cleanup across relevant systems.

The exact process depends on whether the request concerns an individual Account, one Workspace membership, a sole-owned Workspace, a shared Workspace, a public page, particular personal data, or the entire relationship.

Deletion may involve direct record removal, relationship cleanup, anonymization, token revocation, access restriction, object deletion, provider instructions, cache expiry, search-index cleanup, and scheduled backup expiry.

Different systems may complete their portions of the process at different times.

Eligible Account-level information may include the user’s name, email address, telephone number, avatar, profile preferences, personal notification settings, and other profile fields.

Where deletion is approved, this information is deleted or anonymized unless a lawful retention ground applies.

An email address or telephone number may remain in restricted suppression, fraud-prevention, security, or legal records where necessary and lawful.

A deleted Account is not ordinarily available for normal sign-in or profile access.

Active access sessions and refresh credentials associated with the deleted Account are revoked.

Password hashes, passkey associations, multi-factor authentication secrets, backup codes, recovery credentials, and applicable identity links are deleted or rendered unusable.

API keys, personal access tokens, device credentials, and other Account-controlled credentials are revoked where applicable.

Security records concerning previous authentication activity may remain in minimized form for a limited period where needed for fraud prevention, investigation, or legal claims.

Deleting the KOMERRA Account does not automatically remove passkeys or credentials stored locally by a browser, operating system, password manager, or device provider.

The user’s active Workspace memberships are removed when the individual Account is deleted, unless a transfer or another controlled process is required first.

Shared Workspace records are not automatically deleted merely because the user’s membership ends.

The deleted user’s display name may be removed or replaced in historical records where doing so does not undermine accounting, security, audit, or legal integrity.

The remaining Workspace owners may continue to access records that lawfully belong to the business.

For an eligible sole-owned Workspace, deletion may cover customers, products, orders, inventory records, reminders, business preferences, documents, reports, notifications, activities, and other tenant-scoped business records.

Records may be deleted through database relationships, explicit cleanup operations, anonymization, or another controlled method appropriate to the data structure.

Records lacking automatic cascading relationships must be included in explicit deletion or anonymization procedures.

Deletion tooling must preserve tenant boundaries so that deletion of one Workspace does not affect another Workspace.

KOMERRA may retain restricted business records where a lawful retention ground applies.

Eligible invoices, quotations, receipts, delivery notes, reports, exports, templates, and generated files stored only within the deleted Workspace are deleted according to the applicable process.

A document previously downloaded, printed, emailed, messaged, or provided to another person remains in the possession of that recipient and cannot necessarily be deleted by KOMERRA.

A business may be legally required to retain certain accounting or transaction documents even after its Workspace closes.

Where KOMERRA retains a restricted transaction record, unnecessary profile and presentation information should be minimized where practical.

Eligible private uploads associated solely with a deleted Account or Workspace are scheduled for deletion from active object storage.

These may include avatars, logos, product images, attachments, payment evidence, identity documents, and other files.

Files shared across retained records, legal holds, disputes, or other authorized Workspaces may require separate assessment.

Time-limited signed links and access credentials are revoked or allowed to expire.

Copies already downloaded, forwarded, cached, or retained by an authorized recipient are outside KOMERRA’s direct control.

A Mini Store associated solely with a deleted Workspace stops being available through KOMERRA.

Product listings, customer-facing business information, payment instructions, policies, and associated public content are removed from active publication.

Pending Mini Store orders and customer obligations remain the business’s responsibility even after the public page is disabled.

Customers may retain copies of confirmations, messages, documents, and transaction information previously provided to them.

Search engines, social platforms, archives, or browser caches may continue displaying previously indexed material temporarily outside KOMERRA’s direct control.

A Trust Passport associated solely with a deleted Workspace stops being publicly available through KOMERRA.

Verification indicators, business details, published policies, trust signals, and public activity information are removed from active publication.

KOMERRA may retain restricted evidence showing that a check occurred where necessary for fraud prevention, regulatory accountability, disputes, or legal claims.

A deleted Trust Passport must not continue to imply that the business remains active or verified on KOMERRA.

Where a Business Customer created a customer-facing Account for a Mini Store, deletion of that customer Account should be assessed separately from deletion of the seller’s business records.

The customer may request deletion of eligible profile information, while the seller may still need to retain transaction, warranty, delivery, refund, tax, or dispute records.

The seller remains responsible for responding to the customer’s privacy request as controller where applicable.

KOMERRA may anonymize the customer’s Account identity while preserving a restricted transaction record where lawful retention is necessary.

Deletion may disconnect authorized WhatsApp, Instagram, Facebook, email, SMS, payment, storage, verification, analytics, or other connected providers.

KOMERRA-controlled access tokens, refresh tokens, webhook subscriptions, integration credentials, and connection metadata are revoked or deleted where applicable.

Disconnecting a provider through KOMERRA does not necessarily delete information stored independently by that provider.

The user or business may need to close or delete information directly with the relevant provider.

Messages or files previously transmitted to external recipients or providers may remain in those systems according to their own policies and legal obligations.

Account deletion does not retract an email, SMS, WhatsApp message, social message, invoice, receipt, reminder, or other communication already delivered to a recipient.

The recipient may retain the communication according to their own needs, rights, and obligations.

KOMERRA may delete eligible stored copies and message metadata within its control, subject to lawful retention requirements.

A recipient should be contacted directly where a correction, withdrawal, or deletion request must also be communicated to them.

Eligible AI prompts, generated drafts, extraction results, summaries, recommendations, and temporary processing records associated solely with the deleted Account or Workspace are deleted or anonymized according to applicable retention rules.

Approved business records created from AI-assisted workflows are treated according to the rules governing the resulting order, customer, document, communication, or other record.

Deleting an AI conversation does not automatically delete a final business record that was separately reviewed and approved.

Provider-side copies are handled according to the applicable provider terms, KOMERRA’s subprocessor arrangements, and lawful deletion instructions.

Security, safety, billing, or diagnostic metadata may remain in minimized form where a lawful retention need applies.

Eligible Business Memory entries, preferences, approved facts, summaries, and retained AI context associated solely with a deleted Workspace are deleted or anonymized.

Temporary model interpretation should not remain as a permanent business fact after the underlying Workspace is deleted.

Shared records, legal holds, security evidence, or records independently required by another controller may require separate treatment.

KOMERRA may retain de-identified information that cannot reasonably be linked back to the deleted Account, Workspace, customer, or business.

Deletion workflows should address applicable search indexes, vector indexes, retrieval stores, caches, analytics tables, recommendation stores, queues, and derived data systems.

A record should not remain available through search or AI retrieval merely because its primary database record was deleted.

Caches may expire according to controlled cache lifetimes rather than disappearing at the exact moment the primary record is removed.

Where deletion jobs fail, the failure should be visible for retry and operational review.

Derived information that has been irreversibly aggregated or de-identified may remain where it can no longer reasonably identify the Account, business, or individual.

Account-level notification preferences and active notification records are deleted or anonymized where eligible.

Operational emails or notices already delivered cannot be withdrawn from the recipient’s email provider.

KOMERRA may retain a minimal suppression record where necessary to respect an unsubscribe, objection, complaint, or instruction not to send marketing communications.

A suppression record should be limited to what is needed to prevent the prohibited communication from recurring.

Ordinary support conversations may be deleted or anonymized when they are no longer required.

Support records connected with a payment dispute, security event, legal claim, fraud investigation, privacy request, regulator enquiry, or serious complaint may be retained for the applicable lawful period.

Unnecessary attachments and identity information should be removed or minimized where the continuing record does not require them.

Deletion requests and the actions taken in response may themselves be retained as accountability records.

KOMERRA may retain a narrow audit record where deletion of the entire record would undermine security, financial integrity, accountability, legal claims, or referential integrity.

Where possible, the original user name, email address, telephone number, avatar, password material, and other unnecessary identifiers are removed or replaced with a neutral or pseudonymous reference.

A retained audit reference should not be used to recreate the deleted user’s ordinary profile.

Access to retained audit records is restricted to authorized purposes and personnel.

Audit retention does not mean that every activity event is retained indefinitely.

Certain relational systems may require a minimal anonymized user reference after deletion so that payment, security, audit, or transaction records remain structurally valid.

This reference should not contain the original name, ordinary email address, telephone number, avatar, password hash, multi-factor secret, passkey, or recovery credential.

The reference may contain a random identifier, deletion date, deletion status, or similarly limited information needed for integrity and accountability.

It must not be used as an active Account or to permit sign-in.

Payment-provider references, invoices, refunds, chargebacks, Credit purchases, Credit deductions, taxes, and accounting records may be retained where required for financial reconciliation, legal compliance, fraud prevention, or defense of rights.

Retained financial records should contain only the identity information reasonably necessary for the applicable purpose.

Full payment-card numbers and card security codes should not be contained in ordinary KOMERRA business records.

Deletion of the Account does not require an independent payment provider to delete records that the provider must retain under its own legal obligations.

Identity or business-verification information is deleted when it is no longer necessary and no lawful basis for retention remains.

KOMERRA may retain a limited record that a verification occurred, its result, date, provider, or reason where necessary for fraud prevention, legal claims, regulatory accountability, or prevention of repeated verification abuse.

Full identity documents, facial images, NIN information, and sensitive verification evidence should not be retained merely because a minimal verification outcome is sufficient.

Verification providers may maintain independent records according to their legal obligations and applicable agreements.

KOMERRA may retain statistics, measurements, patterns, and other information that has been aggregated or de-identified so that it no longer reasonably identifies the deleted user, business, customer, or Workspace.

Examples may include overall service performance, error rates, general usage trends, capacity planning, and non-identifying product analytics.

De-identified information must not be combined with other information for the purpose of reconstructing the deleted identity.

Information that can still reasonably identify a person or business remains subject to applicable deletion and retention requirements.

KOMERRA may use service providers for hosting, databases, storage, monitoring, communications, AI processing, verification, analytics, support, and payments.

Where required and applicable, KOMERRA will instruct relevant processors to delete, return, anonymize, or restrict eligible personal data associated with the approved request.

A provider may retain limited information where it has an independent legal obligation or lawful basis to do so.

KOMERRA cannot promise deletion from a third party that received information independently from the user, business, customer, recipient, or another controller.

Material subprocessors are described through the Privacy Policy, Data Processing Agreement, Subprocessors page, or applicable enterprise agreement.

KOMERRA can remove eligible Mini Store, Trust Passport, and other public content from its active services.

Search engines, social networks, browser caches, web archives, and third-party websites may continue displaying a cached or copied version temporarily.

KOMERRA may update indexing instructions or submit removal requests where appropriate, but it does not control every independent third party.

The requester may also need to use the third party’s own removal process.

Protected backups may retain a copy of deleted information until the applicable backup expires, is overwritten, or is securely destroyed through the normal backup cycle.

Backup copies are not intended to remain available for ordinary production access after deletion.

Access to backups is restricted to recovery, security, continuity, legal, or other authorized purposes.

Where a backup containing deleted information is restored following a disaster or serious failure, applicable deletion records should be reapplied so the deleted information is not returned to normal active use.

Backup retention periods should be documented through the Data Retention Policy and actual infrastructure configuration.

KOMERRA cannot necessarily delete information that has already been downloaded, printed, exported, emailed, messaged, copied, screenshotted, or stored by another person.

KOMERRA cannot delete records held independently by a bank, payment provider, government authority, customer, supplier, employee, professional adviser, search engine, social network, or other controller.

Deletion does not invalidate a transaction, document, contract, payment, customer obligation, legal claim, or communication that occurred before deletion.

Deletion does not remove information that the requester independently published or provided outside KOMERRA.

KOMERRA processes eligible deletion and erasure requests without undue delay, taking account of identity verification, authority, request scope, system complexity, shared records, provider involvement, legal obligations, and security risk.

Some active-system actions may complete before provider, archive, cache, or backup deletion finishes.

Where additional time or information is reasonably necessary, KOMERRA will seek to communicate the request status and what remains outstanding.

KOMERRA will not represent deletion as complete merely because the user interface has hidden the Account or public page.

KOMERRA will provide or display confirmation when the deletion request is accepted for processing where appropriate.

A further confirmation will be provided when the applicable active-system deletion or anonymization work is complete.

The confirmation may identify whether the Account, Workspace, memberships, public pages, integrations, files, and other relevant categories were deleted, anonymized, disconnected, or retained on a restricted basis.

Where a category cannot yet be deleted, the response should identify the general category and lawful reason without exposing internal security information or another person’s data.

A completion confirmation does not mean that protected backups have already reached the end of their rotation.

After irreversible deletion, KOMERRA may be unable to restore the Account, Workspace, customer records, documents, files, public pages, settings, integrations, AI context, or activity history.

Registering again with the same email address or business name does not restore the deleted Account or connect the new Account to the previous Workspace automatically.

Previously issued documents or records held by customers and other recipients may continue to exist independently.

The requester is responsible for exporting required records before irreversible deletion begins.

A former user may be able to register a new Account after deletion, subject to current eligibility, verification, abuse-prevention, security, and product rules.

A new Account begins without the deleted Workspace’s records, Credits, settings, integrations, verification status, or history unless a lawful and documented restoration process applies.

KOMERRA may retain a restricted suppression or anti-fraud reference where necessary to prevent repeated abuse, unauthorized trials, chargeback fraud, or circumvention of enforcement.

Deletion cannot be used to evade a lawful restriction or unresolved obligation.

A person may request deletion while an Account is suspended or under investigation.

Suspension does not automatically eliminate the right to request deletion of eligible personal data.

KOMERRA may retain relevant evidence while it remains necessary for security, fraud prevention, legal claims, provider disputes, or regulatory obligations.

Deletion does not erase the existence of a prior enforcement decision where a limited record remains lawfully necessary.

A person must not repeatedly delete and recreate Accounts to evade restrictions, obtain repeated included usage, manipulate promotions, or conceal abuse.

A user does not need to delete the entire Account to exercise every privacy right.

Depending on the circumstances, a person may request access, correction, portability, restriction, objection, withdrawal of consent, or deletion of a particular category of personal data.

A narrower request may preserve useful Account or Workspace functionality while resolving the privacy concern.

KOMERRA will assess the requested right according to its role as controller or processor, the relevant lawful basis, the rights of other people, and applicable law.

A requester’s Account or Workspace may contain information relating to customers, staff members, suppliers, co-owners, recipients, or other people.

KOMERRA will not disclose or delete another person’s data merely because it appears beside the requester’s data.

The rights and freedoms of other data subjects must be considered when fulfilling access, portability, or deletion requests.

Where possible, KOMERRA may separate, redact, restrict, anonymize, or preserve only the portion necessary to protect each person’s rights.

KOMERRA may deny, defer, or partially fulfil a request where identity or authority cannot be verified, the request is fraudulent, another person’s rights would be unlawfully affected, or retention remains legally necessary.

KOMERRA may also ask the requester to clarify an excessively broad or unclear request.

A denial or limitation should explain the general basis and identify any available reconsideration or complaint route.

KOMERRA may withhold information that would expose security controls, confidential provider material, another person’s data, or an active investigation.

A requester may seek reconsideration where they believe the request was misunderstood, evidence was overlooked, authority was established, or information was retained without an applicable reason.

The reconsideration request should identify the original request or case reference and explain the disputed part of the outcome.

New supporting information should be included where available.

KOMERRA may assign a different authorized reviewer where appropriate.

Protective or legal restrictions may remain in place while reconsideration is pending.

A data subject may lodge a complaint with the Nigeria Data Protection Commission where they believe their personal-data rights have not been handled appropriately.

We encourage the requester to contact KOMERRA first so the Account, Workspace, and records can be identified and the matter can be reviewed promptly.

Contacting KOMERRA first does not remove a person’s right to contact the Commission or another competent authority.

KOMERRA will cooperate with lawful regulatory enquiries and preserve relevant deletion-request records where required.

Deletion tools and administrative workflows must enforce authentication, authorization, tenant context, ownership, auditability, and protection against cross-Workspace deletion.

Destructive jobs should use verified identifiers and should not depend solely on values submitted by a browser or AI model.

Deletion operations should be idempotent where appropriate so retries do not affect unrelated records.

Failures should be logged, visible to authorized operators, and safe to retry.

Privileged deletion actions should create audit records identifying the request, scope, reviewer, execution status, and applicable reason.

An AI feature may help explain the deletion process, classify a request, identify relevant records, or prepare a support response.

AI must not independently approve Account ownership, authorize Workspace deletion, override a legal hold, or execute irreversible deletion without the required deterministic checks and authorized workflow.

Identity, authority, tenant ownership, deletion scope, and legal restrictions must be evaluated through trusted application and administrative controls.

A model-generated conclusion that deletion is safe is not sufficient authorization.

KOMERRA may update this Policy when its Account structure, Workspace model, deletion tools, providers, data categories, legal obligations, backup arrangements, or product features change.

Material changes will be communicated through an appropriate website, application, Account, or email channel where required.

A policy update will not reduce a deletion or erasure right that cannot lawfully be excluded.

The deletion process used for a request should reflect the actual systems, providers, data flows, and legal obligations in effect when the request is processed.

Send Account, Workspace, membership, or personal-data deletion questions to support@komerra.app.

Use “Account Deletion Request” for full Account or Workspace closure.

Use “Privacy Request” for deletion or restriction of particular personal data without closing the entire Account.

Include the Account email, business name, affected Workspace, your role, intended scope, reason for the request, and whether access to the Account remains available.

Do not send passwords, one-time passwords, recovery codes, private keys, card security codes, bank PINs, or unnecessary identity documents through ordinary email.