Skip to content
KumoBunkerKumoBunker
How it worksWhy usWho it's forPricingUse casesContact Sign in Start free trial
USDSGD
Sign in Start free trial
  1. Legal
  2. Privacy Policy

Privacy Policy

ProviderKumify Pte. Ltd., incorporated in Singapore
Unique Entity Number (UEN)202647131C
Websitehttps://www.kumobunker.com
Version1.3 - Emergency Mail standby server and outgoing-mail filtering added; reviewed 16 November 2026
Prepared15 November 2026
Effective dateOn publication by Kumify Pte. Ltd.

On this page

  • 1. Important Definitions & Scope
  • 2. Information We Collect
  • 3. How We Use Information
  • 4. Data Retention & Deletion
  • 5. Data Security & Sub-processors
  • 6. International Data Transfers
  • 7. User Rights & Disclosures

1. Important Definitions & Scope

1.1 Who we are and what this Policy covers

Kumify Pte. Ltd. ("Kumify", "we", "us" or "our") operates KumoBunker, a cloud-based email backup and recovery service (the "Service"). This Privacy Policy explains how we handle information relating to our website, trials, customer accounts, support services and connected email mailboxes.

The Service supports lawful personal, household and business use. This Policy applies to customers, account administrators, authorised users, website visitors, people contacting us, mailbox owners, and individuals whose information appears in backed-up email.

Singapore data protection framework. Kumify is subject to Singapore's Personal Data Protection Act 2012 ("PDPA") and applicable subsidiary legislation. The PDPA is the primary Singapore data protection framework for this Policy. We apply the obligations relevant to our actual role in each processing activity, including accountability, appropriate purposes and notification, consent where required, access and correction, accuracy, protection, retention, overseas transfers and breach notification. Other laws, including the GDPR, UK GDPR or CCPA, apply additionally only where their legal scope covers the relevant activity. References to them do not displace the PDPA or represent that every Customer is subject to those laws.

1.2 Key definitions

  • Customer: The individual or organisation subscribing to or using the Service, including through a trial.
  • Authorised User: A person permitted by the Customer to access or administer an account or use its backup and recovery functions.
  • Account Data: Information we handle to establish and administer our relationship with Customers and users, including contact details, subscription and billing records, support communications, authentication records, website request logs and operational usage metrics.
  • Service Data: Email messages, attachments, headers, sender and recipient details, folder structures, timestamps, message flags, search indexes, recovery points and other mailbox information copied, generated or stored to provide the Service. Mailbox connection credentials and settings are also handled under the protections applicable to Service Data.
  • Personal Data: Under the PDPA, data, whether true or not, about an individual identifiable from that data or from that data and other information to which the organisation has or is likely to have access. Where another applicable law uses a broader definition, that definition applies for its purposes.
  • Organisation: A person or body falling within the PDPA's definition and responsible for the obligations applicable to its activities, subject to statutory exclusions and exemptions.
  • Data Intermediary: An organisation processing Personal Data on behalf of and for the purposes of another organisation, excluding an employee of that other organisation. The PDPA's specific allocation of data intermediary duties applies where the processing is under a contract evidenced or made in writing and the relevant statutory conditions are satisfied.
  • Controller: Where that terminology is used by an applicable law, the person or organisation determining the purposes and essential means of processing Personal Data.
  • Processor: Where that terminology is used by an applicable law, a person or organisation processing Personal Data on behalf of a Controller under its instructions.
  • Subprocessor: A provider engaged to process Service Data on behalf of a Processor.
  • DPA: A data processing agreement addressing the parties' respective duties for processing Service Data.

Account Data and Service Data describe different processing purposes. We do not reclassify backed-up email bodies, attachments or search indexes as Account Data to use them for our own commercial purposes. A mailbox address may appear in both categories, but its use is governed by the purpose for which it is processed.

1.3 Our different legal roles

Account Data. Kumify is the responsible organisation under the PDPA for Account Data collected, used or disclosed for its own account administration, billing, support, security and legal compliance purposes. Where the GDPR or a comparable law applies, Kumify generally acts as Controller for those purposes.

Business Service Data. Under the PDPA, the business Customer is generally the organisation responsible for the purposes for which it engages us to process mailbox data. Kumify acts as a data intermediary where the statutory conditions are met, processing email contents solely on the Customer's behalf and under its documented instructions, except where applicable law requires otherwise. The Customer remains responsible for obligations applying to its processing through an intermediary. Kumify retains its own applicable duties, including protection, retention limitation and notifying the Customer of data breaches without undue delay. Where the GDPR applies, the corresponding arrangement is generally Customer as Controller and Kumify as Processor. Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act ("CCPA"), we act as a service provider or contractor only where the legal and contractual requirements are satisfied.

If a managed service provider or other Customer processes mail for another organisation, that organisation may be the Controller, the Customer its Processor, and Kumify a Subprocessor. The relevant agreements must authorise this arrangement.

Personal and household Service Data. The PDPA excludes individuals acting in a personal or domestic capacity from specified data protection obligations. Such an individual is not automatically a regulated business Controller or responsible organisation merely by subscribing. We still process their mailbox contents to carry out their backup and recovery instructions and remain subject to the PDPA obligations applicable to our own activities. We do not assume that an individual's exemption also exempts Kumify or automatically makes every personal-customer relationship a statutory data-intermediary arrangement. Legal roles depend on actual processing and applicable law, rather than labels alone.

1.4 Customer instructions and agreements

Customer instructions include the applicable service agreement, any DPA, and authorised configuration choices, backup schedules, retention settings, support requests, restores, exports and deletion requests. Customers are responsible for having lawful authority over each connected mailbox, providing required notices and permissions, and ensuring their instructions are lawful.

This Policy is a transparency notice. It does not replace a legally required DPA, international transfer agreement or HIPAA business associate agreement ("BAA"). It does not give us broader rights to use Service Data than those agreements permit. Applicable mandatory law and an executed DPA, BAA or transfer agreement prevail within their respective subject matter. Reading this Policy or using the Service does not, by itself, constitute consent to processing for which specific consent is legally required.

2. Information We Collect

2.1 Account information

We collect information you provide when you request a trial, create or administer an account, subscribe, contact us or seek support. Depending on your interaction, this includes:

  • Name, email address, company or organisation name, and other contact details you choose to provide.
  • Account identifiers, user roles, invitations, preferences, subscription details and administrator contact information.
  • Billing identity and address, invoice and payment records, transaction references and payment status where needed for a paid subscription. Any payment provider separately collecting payment credentials must be identified in the relevant checkout notice.
  • Contact, trial and support submissions, including your message and any optional information about mailbox counts or email providers.
  • Authentication and account-recovery information. Account passwords are stored as Argon2id hashes rather than readable passwords.

If you include an email excerpt or attachment in a support request, we restrict its use to resolving that request and related authorised Service purposes. We do not treat it as permission to exploit mailbox content commercially. Please do not send passwords, unnecessary sensitive information or unlawful material through support forms.

2.2 Usage, technical and security information

We automatically collect information needed to operate and protect the website and dashboard, including:

  • IP address, browser or user-agent information, requested pages or endpoints, and access timestamps.
  • Sign-in events, session and device identifiers used for authentication, and records of security-relevant account changes.
  • Backup and restore status, storage usage, job volumes, error information and operational performance indicators.
  • Audit events recording sign-ins, restores, deletions and settings changes.
  • Failed mailbox-authentication results, including relevant mailbox addresses and IP addresses, to detect unauthorised password testing and account abuse.

Device information is used for access, authentication and security. We do not build advertising profiles from it. Service-related logs are kept to the information reasonably needed for their operational purpose; this does not authorise copying email contents into general analytics datasets.

2.3 Service Data from connected mailboxes

After an authorised connection is established, the Service automatically ingests and stores messages from the folders selected by the Customer. Depending on the selected features and mailbox settings, it also organises information and generates encrypted message summaries for recovery, browsing and search. Private mailboxes are handled differently as explained below.

Service Data includes:

  • Message bodies, subject lines, attachments and embedded message content.
  • Sender, recipient, copy-recipient and other header information, including routing metadata where present in the source message.
  • Folder names and hierarchy, message identifiers, dates, labels and message flags.
  • Recovery-point records, encrypted message summaries and any supported search information generated to locate and restore backed-up messages.
  • IMAP server details, usernames, passwords or app passwords, connection settings, backup schedules and retention settings supplied to connect and manage mailboxes.

The contents depend on what Customers and their correspondents put in email. They may include financial records, health information, confidential business information, children's information, or other sensitive Personal Data. We do not require Customers to place those categories in email or use them to infer personal characteristics. Special restrictions for HIPAA-regulated information appear in Section 5.5.

Private mailboxes remain backed up and restorable, but browsing, searching, opening and downloading their email are blocked for everyone, including staff. We do not store message summaries for private mailboxes. In place of those summaries, we retain an encrypted message identifier used to prevent duplicates during restoration. The encrypted messages and recovery information necessary for backup and restore are still processed.

2.4 Sources and cookies

We receive information directly from Customers and users, from account administrators and mailbox owners, automatically from devices and connected mail servers, and from providers supplying information necessary to complete authorised account transactions.

Our public website does not currently set cookies or use analytics, advertising or tracking scripts. Technical server logs are still collected. The authenticated dashboard uses a sign-in session cookie and, if selected, a persistent device cookie for "Keep me signed in". These support authentication and are not used for advertising. Contact, trial and support forms may use Cloudflare Turnstile for abuse prevention, as described in Section 5.4. Disabling necessary authentication cookies may prevent dashboard access.

Dashboard sessions expire after 30 minutes of inactivity or a maximum of 12 hours. Remembered-device authorisations last up to 30 days for Customers and seven days for staff, unless revoked sooner. A remembered-device authorisation is separate from the duration of an individual signed-in session.

If we introduce non-essential tracking, we will explain it and obtain consent or provide applicable opt-out controls before its use where required.

3. How We Use Information

3.1 Account Data purposes

We use Account Data to:

  • Review trial requests, establish accounts, verify email addresses, manage subscriptions and administer user permissions.
  • Process billing, maintain transaction records and address payment or account issues.
  • Respond to enquiries, provide support and communicate about requested services.
  • Send necessary sign-in links, backup alerts, security notices, service announcements and policy or contractual updates.
  • Operate, troubleshoot and improve the reliability and usability of the website and dashboard using operational information.
  • Detect fraud, unauthorised access and abuse, enforce lawful service restrictions, and meet legal, accounting and regulatory obligations.

Submitting a contact or trial form does not subscribe you to a marketing list. We do not use backed-up email or its metadata to select marketing recipients or personalise advertising. Any separate optional marketing programme would require appropriate notice and any legally required consent or opt-out.

3.2 Service Data purposes and restrictions

We process Service Data strictly to carry out documented Customer instructions and provide the agreed Service, including:

  • Connecting to authorised mailboxes and executing scheduled or requested backups.
  • Encrypting, compressing, storing and maintaining recovery points and agreed protection copies.
  • Providing authorised browsing, indexing, search, download, export and restoration features, subject to private-mailbox restrictions.
  • Applying Customer retention and deletion instructions and assisting with applicable rights requests.
  • Providing requested support and maintaining the security, integrity and availability of the backup service.

Security processing involving Service Data is limited to what is necessary and proportionate for the agreed Service, applicable instructions and legal requirements. It does not permit unrestricted inspection of correspondence or unrelated reuse. If law requires processing outside Customer instructions, we will inform the Customer before doing so unless the law prohibits notification.

We do not:

  • Sell Service Data, license it for another party's use, or share it for cross-context behavioural advertising.
  • Use email bodies, attachments or mailbox metadata for our own marketing, advertising profiles, data brokerage or unrelated monetisation.
  • Use Service Data to train general-purpose artificial intelligence or machine-learning models, or permit a provider to do so on our behalf.
  • Combine Service Data across Customers or with third-party datasets to create commercial profiles about individuals.

Charging a subscription fee to provide backup services does not give us a right to monetise the backed-up data itself.

3.3 Singapore PDPA purposes, consent and accuracy

For processing for which we are the responsible organisation, we collect, use and disclose Personal Data only for purposes a reasonable person would consider appropriate in the circumstances. We notify individuals of the relevant purposes on or before collection, or at another time permitted by the PDPA. We do not require consent to purposes beyond what is reasonable to provide the relevant product or service as a condition of supplying it.

We obtain consent where required, including valid deemed consent where the PDPA permits it, or rely on an applicable statutory exception. If relying on a specific exception, including a legitimate-interests or business-improvement exception, we must satisfy that exception's conditions and required safeguards. A GDPR legal basis is not, by itself, a substitute for satisfying the PDPA.

You may withdraw consent on reasonable notice using the contact route in Section 7.7. We will explain the likely consequences, which may include inability to continue a function that needs the affected data, and stop the relevant collection, use or disclosure unless the PDPA or another written law requires or permits it without consent. Withdrawal does not automatically require deletion of records lawfully retained for a separate legal purpose, or waive an active immutable lock; we must still assess and meet our applicable legal duties. We will not impose an arbitrary penalty for exercising a withdrawal right.

We make reasonable efforts to maintain the accuracy and completeness of Personal Data where it is likely to be used to make a decision affecting an individual or disclosed to another organisation. Customers should keep account information current. Backups preserve source records; correction requests affecting archived correspondence are handled with the responsible Customer where appropriate, rather than silently rewriting original messages without authority.

3.4 Additional legal bases where another law applies

Where the GDPR, UK GDPR or a comparable law also applies and requires a legal basis for processing Account Data, we rely, as applicable, on:

  • Contract: Processing necessary to enter into or perform a contract with an individual Customer.
  • Legitimate interests: Administering organisational customer relationships, responding to business enquiries, maintaining reliable services and protecting against fraud and security threats, after considering affected individuals' rights.
  • Legal obligations: Maintaining legally required records and complying with binding legal requirements.
  • Consent: Where required for an optional activity, subject to the right to withdraw it.

The Customer determines the lawful authority and any additional conditions required for its instructed processing of Service Data where it is the responsible organisation or Controller. We remain responsible for obligations applying directly to us under the PDPA and any other applicable law.

4. Data Retention & Deletion

4.1 Customer-controlled Service Data retention

During an active subscription, Service Data is retained according to the Customer's supported retention settings and service agreement, including any expressly locked recovery points or immutable-storage periods. The Service currently supports up to seven daily and 24 monthly recovery points, together with recovery points the Customer locks for longer retention while the account remains active.

Older recovery points are cleared according to the configured retention rules, except for locked points and other agreed retention protections. Where several recovery points refer to the same message, deleting one point does not delete a message still needed by another retained point. Removing a mailbox connection stops future backups but does not itself erase existing backups. Deleting a message from the source mailbox also does not automatically erase earlier backup copies.

4.2 Mailbox deletion and account termination

When a Customer deletes a mailbox or closes its account:

  1. Further backups of the affected mailbox or account stop immediately.
  2. A seven-day waiting period normally applies to allow correction of an accidental request. When deleting a mailbox, the Customer may select the supported option to skip that waiting period.
  3. We erase affected recovery points, archived messages and associated search information from ordinary backup servers and the separate non-immutable protection copy within 30 days of the deletion or closure request.
  4. When an account is terminated by us or under the service agreement, the same ordinary deletion timetable runs from the effective termination date, unless a shorter period is agreed or law requires otherwise.

The 30-day period includes the ordinary waiting period; it is not an additional 30 days afterwards. The exceptions in Section 4.3 apply. Subscription renewal cancellation may take effect at the end of the paid term and is distinct from an immediate account-closure request. Customers should arrange any lawful export before closure or termination takes effect, subject to their agreement and available features.

Ended trials: When a trial ends without conversion to an active subscription, the Customer has seven days of browse-and-restore access, subject to mailbox permissions and private-mailbox restrictions. After that recovery window, the account and its backups are deleted under the closure process described above. Trial recovery access does not extend the ordinary 30-day deletion period once account closure begins.

Deletion is designed to make the data permanently unavailable for recovery through the Service. We use deletion mechanisms appropriate to the storage architecture, including removal of stored objects and associated indexes and, where applicable, cryptographic erasure of keys. We do not describe logical deletion as immediate physical overwriting of every storage device.

4.3 Immutable storage and legal preservation exceptions

The optional Immutable Backup & Recovery add-on stores encrypted protection copies under retention locks that cannot be shortened or removed while active. Each copy is locked for at least 30 days and for the period specified for that copy.

  • A still-locked copy may remain after the ordinary 30-day deletion deadline. It is erased automatically when its applicable lock expires.
  • Account closure does not immediately unlock an immutable copy. The Customer must consider the actual lock-expiry dates before enabling the add-on or placing data subject to a shorter deletion requirement into it.
  • Pending expiry, residual copies are restricted to the protection purpose and are not reused for analytics, marketing or unrelated operations. We do not restore deleted data into normal use except on lawful, authorised instructions; applicable deletion restrictions must be reapplied if recovery is legally required.
  • A technical lock does not create an exemption from privacy law. We will assess legally required deletion or restriction requests with the Customer and take lawful, technically available measures consistent with the DPA and applicable law.

Where law requires preservation of particular information, we retain only what is necessary for the required period, restrict its use to that purpose and delete it when the obligation ends. An ordinary commercial preference is not a basis to retain Service Data indefinitely after termination. We will inform the Customer about a preservation requirement where legally permitted.

4.4 Account records, credentials and trial information

  • Customer profiles, user records, plan history and billing-country records: Kept while the account exists and deleted as part of account closure, subject to the ordinary deletion timetable and the limited legal-preservation exceptions in this Policy.
  • Separate invoices, transaction and accounting records: Kept to the extent and for the period required by applicable tax and accounting law, even if the operational customer profile is deleted. Singapore corporate tax records generally require retention for at least five years from the relevant Year of Assessment. Applicable accounting-record rules may use a different starting point; we apply the requirements relevant to the record and restrict any retained information to the necessary purpose.
  • Mailbox credentials: Encrypted credentials are kept only while needed for authorised connection and Service functions, and removed when those purposes end under the applicable deletion process.
  • Trial password hashes: Deleted if a trial request is not approved, or if the email address is not confirmed within 48 hours. Accounts for completed trials follow the seven-day recovery-access and account-deletion process in Section 4.2.
  • Enquiries and support records: Kept for handling the request, necessary follow-up and applicable legal obligations. We assess continued necessity and remove unnecessary sensitive supporting material earlier where appropriate.

4.5 Logs, notification records and sessions

The normal retention schedule for operational records is:

Record categoryNormal retention
Security and audit logs2 years
Backup and restore job history24 months
Email notification content180 days
Email delivery logs90 days
User sign-in history, including recorded IP addresses90 days
Backup server event logs60 days
Application and scheduled-task logs30 days

These periods apply to the relevant record category; a shorter sign-in-history period does not mean a distinct security or audit event is erased before its own retention period ends. Operational records may remain for their applicable period after an account is closed, with use restricted to the stated operational, security or legal purpose. They do not authorise retaining deleted email bodies or attachments as general logs. A record that erasure occurred may remain without retaining the erased correspondence.

Sessions expire after 30 minutes idle or 12 hours at most. Remembered-device authorisations last up to 30 days for Customers and seven days for staff, unless removed or revoked sooner.

Under the PDPA's Retention Limitation Obligation, we cease retaining Personal Data, or remove the means by which it can be associated with an individual, when its purpose is no longer served and retention is no longer necessary for legal or business purposes. The normal periods above are not authority to retain information after that test is no longer met. A narrowly applicable legal-preservation requirement may require longer retention of particular records; any extension is limited to the necessary information and purpose. Where no fixed period is specified, we determine necessity using the nature and sensitivity of the information, its purpose, applicable law and the circumstances of the request.

5. Data Security & Sub-processors

5.1 Technical and organisational safeguards

We maintain safeguards appropriate to the nature of the information and the risks of the Service. These include:

  • Mailbox encryption at rest: Every backed-up message, including attachments, is encrypted with XChaCha20-Poly1305 using libsodium and a separate key for each mailbox. Standard-mailbox message summaries used for browsing and search, including subject, sender, recipients and date, are also encrypted with that mailbox's key. Private mailboxes do not store those summaries.
  • Key protection: Mailbox keys are themselves encrypted using a separate key held on each backup server. This protects stored copies but does not make the Service end-to-end encrypted.
  • Encryption in transit: The website and dashboard use TLS 1.2 or TLS 1.3 with HTTP Strict Transport Security (HSTS). Connections to Customers' mail servers require TLS with certificate verification; unencrypted connections are refused.
  • Server-to-server authentication: Requests between our servers use HTTPS and Ed25519 signatures to authenticate requests and protect their integrity.
  • Credential protection: Saved mailbox passwords are encrypted at the application level with XChaCha20-Poly1305 and are not displayed again, emailed or placed in logs. Account passwords are hashed using Argon2id.
  • Access controls: Role-based account permissions, private-mailbox restrictions and re-authentication for sensitive administrative changes. Authenticator-app two-factor authentication is mandatory for staff and available to Customers.
  • Accountability: Audit records of sign-ins, restores, deletions and configuration changes, together with operational monitoring for abuse and suspicious access.
  • Content-display safeguards: Scripts and remote images are removed or blocked when messages are displayed through supported browsing functions.
  • Recovery protections: Separate backup storage and recovery-point controls. For Customers purchasing Immutable Backup & Recovery, copies are encrypted on our servers before upload to Backblaze B2 and stored under Object Lock in compliance mode. Backblaze stores those encrypted copies without the decryption keys needed to read them.
  • Personnel and operational controls: Access limited to authorised personnel for a defined need, confidentiality requirements, secure handling procedures and proportionate incident response and supplier review.

Our encryption description concerns the specified data and layers; it is not an assertion that every item of Account Data or every infrastructure component uses the same algorithm. KumoBunker is not end-to-end encrypted: it decrypts email when a Customer uses authorised browsing, search or restore functions. Encryption at rest protects storage media and copied files and prevents storage providers from reading the separately encrypted add-on copies; it does not protect against an attacker obtaining full control of a running server with access to decryption keys. Private-mailbox restrictions prevent anyone from reading those mailboxes through the Service while allowing automated backup and restoration.

5.2 Staff access, assurance and incidents

Staff access to mailbox contents is limited to authorised assistance requested by the Customer or fixing a problem the Customer reports, subject to private-mailbox protections. Necessary security investigations must respect applicable instructions, access restrictions and law. Any access compelled by law is handled under Section 7.4. This Policy does not grant unrestricted permission for staff to read email.

Private mailbox browsing, search, opening and download are blocked for all user roles, including staff. Whole-mailbox restoration is restricted to the same mailbox. Only support can change the private setting, and the mailbox owner is notified if that happens.

KumoBunker does not currently hold an independent ISO/IEC 27001 certification or a SOC 2 examination report. We completed an internal security assessment and remediation in November 2026; this was an internal review, not an independent certification or audit opinion.

Our providers maintain their own assurance programmes: OVHcloud publishes ISO/IEC 27001 certification information, Backblaze publishes SOC 2 Type II assurance information, and Zoho/ZeptoMail publishes ISO/IEC 27001 and SOC 2 assurance information. The applicable scope, entity, service and reporting period are those of the provider's current documentation. Those assurances do not certify KumoBunker or establish that a particular Customer workload meets every regulatory requirement. No service can guarantee absolute security.

Where we act as a data intermediary and have reason to believe a data breach has occurred involving Personal Data processed for a Customer, we notify that Customer without undue delay and provide the information and assistance required by the DPA and law. We do not wait for the Customer's assessment of whether the incident is notifiable before giving the required intermediary notice.

Where Kumify is responsible for assessment and notification as an organisation under the PDPA, we assess the incident reasonably and expeditiously. If notification to Singapore's Personal Data Protection Commission ("PDPC") is required, we notify it as soon as practicable and no later than three calendar days after the day we determine that the breach is notifiable. We notify affected individuals as soon as practicable where the PDPA requires it, subject to applicable exceptions and directions. This three-calendar-day period is not a general period for delaying notice to Customers and is not automatically measured from initial discovery of every incident.

Customers retain their own assessment and notification duties where applicable. We also meet any additional notification requirements imposed directly on us by another applicable law or executed agreement.

5.3 Supplier selection and contractual protections

We use vetted providers suitable for enterprise backup, hosting, storage and supporting operations. We assess relevant security, confidentiality, reliability, location and legal safeguards before entrusting Personal Data to them. Providers processing Service Data on our behalf must be bound by written terms imposing confidentiality, appropriate security, restricted purposes, assistance with rights and incidents, deletion or return obligations, and equivalent applicable data protection commitments.

Subprocessors may process Service Data only to provide their contracted services and must not use it for their own advertising, data brokerage or general-purpose model training. We remain responsible for our Subprocessors as required by the DPA and applicable law. Required Customer authorisation and notice or objection procedures for Subprocessor appointments and changes are addressed in the DPA.

An infrastructure provider's brand, certification or data-centre location does not by itself establish Kumify's compliance or a Customer's regulatory compliance. The providers used for the current architecture are described below.

5.4 Identified providers and recipients

Our current infrastructure and supporting recipients include:

Provider or componentFunction and information involvedLocation
OVHcloud VPSWebsite and control panel; account records, encrypted mailbox credentials and logsSingapore
OVHcloud dedicated serverPrimary storage and processing of Customers' encrypted email backupsMumbai, India
Independent protection server, for the optional add-onHolds and processes encrypted protection copies and writes locked copies to Backblaze B2United Kingdom
Backblaze B2, for the optional add-onStores pre-encrypted immutable protection copies under compliance-mode Object LockEU Central region, Amsterdam, Netherlands
OVHcloud VPS, Emergency Mail standby server, only during an Emergency Mail incidentWhile a Customer's own mail system is down and the Customer has asked for Emergency Mail: temporary mailboxes holding the recent months of mail restored from that Customer's backups, mail received and sent during the incident, temporary sign-in details and mail logsFrance (OVHcloud, Lille region)
SpamExperts outgoing filtering (N-able), only during an Emergency Mail incident and where set up for the Customer's domainFilters and relays the Customer's outgoing email sent from the Emergency Mail standby server, including message contents, sender and recipient detailsApplicable processing locations are identified in the provider register
Zoho/ZeptoMailDelivers transactional messages, including recipient details and the information needed for sign-in links and Service alertsApplicable sending and processing locations are identified in the provider register; the countries listed for backup storage are not a guarantee about notification processing
Cloudflare Turnstile, where enabledReceives IP addresses and browser-related technical information for form abuse prevention, rather than the contents typed into the formProcessing is subject to the applicable Cloudflare service and transfer arrangements; the backup-storage countries do not describe all form-security processing

The Emergency Mail standby server and outgoing filtering apply only to a Customer who asks for Emergency Mail during an incident, for the affected mailboxes and only for the duration of that incident. When the incident is closed or cancelled, the temporary mailboxes are deleted from the standby server and the backups taken of them are erased after a 7-day waiting period. The standby server never reads the backup servers; copies are restored into it.

The United Kingdom and Netherlands copy-processing route applies only to Customers who purchase the Immutable Backup & Recovery add-on. Purchasing the add-on does not move primary backups out of India or account records and credentials out of Singapore. Transactional-email recipients receive the information needed for notifications rather than general access to mailbox archives.

The provider register and applicable DPA supplement this description with the actual contracting legal entities, the operator or hosting provider of the independent UK protection server, relevant onward subprocessors, other processing and remote-access locations, and transfer safeguards. Those details must be established before any processing requiring Customer authorisation. Each provider's role depends on its data and function: an Account Data provider is not automatically a Subprocessor of backed-up email contents.

5.5 HIPAA and specially regulated information

Customers must not place HIPAA-regulated protected health information in the Service unless Kumify has expressly accepted that use in writing, a required BAA has been executed and the agreed safeguards are in place. If Kumify does not offer or execute the required BAA, that use is not permitted. Encryption and a private-mailbox setting do not remove a BAA requirement.

Other regulated data may be processed only where lawful and supported by the agreed Service scope. This restriction does not classify every personal email containing health information as HIPAA-regulated information; the applicable legal context determines whether HIPAA applies.

6. International Data Transfers

6.1 Processing locations and residency

Kumify is incorporated in Singapore. The current storage and protection architecture is:

  • Singapore: The website and control panel on an OVHcloud VPS, with account records, encrypted mailbox credentials and logs.
  • India: Customers' primary email backups on an OVHcloud dedicated server in Mumbai.
  • United Kingdom, optional add-on only: An independent protection server holds and processes encrypted copies and writes the locked protection copies to Backblaze B2.
  • Netherlands, optional add-on only: Backblaze B2 stores the encrypted, locked protection copies in its EU Central region in Amsterdam.
  • France, Emergency Mail incidents only: While a Customer's own mail system is down and the Customer has asked for Emergency Mail, temporary mailboxes on an OVHcloud VPS in France hold the recent months of the affected mailboxes' mail and the mail received and sent during the incident, until the incident is closed.

Primary backups are stored in India, including for EU/EEA Customers. The optional copy in the Netherlands passes through the UK protection-server workflow and does not make the Service an EU-only service. Account processing takes place in Singapore. The current Service does not provide a general guarantee that EU-origin data remains exclusively in the EU or EEA, and the listed locations are not a representation that every Customer can select a region.

This storage description does not cover the location of a Customer's own mail provider, Customer-directed exports or every supporting provider's operational processing. Notifications, form-security checks and authorised remote support may involve further cross-border processing. Access from another country may constitute a transfer even if a stored copy does not move.

Any stricter residency commitment must be expressly agreed in an applicable order form, DPA or written residency schedule and supported by the deployed configuration. That schedule must identify covered data, primary and protection-copy locations, permitted access locations, relevant providers and exceptions. Customers requiring EU-only storage or access must obtain a separately confirmed suitable arrangement before connecting mailboxes; the current architecture described here does not satisfy an EU-only requirement.

6.2 Transfer safeguards

Singapore PDPA. For overseas transfers for which Kumify is responsible, we meet the Transfer Limitation Obligation and applicable regulations, including taking appropriate steps to ensure transferred Personal Data receives protection at least comparable to that under the PDPA, unless an applicable legal exception or exemption permits another approach. We use legally enforceable recipient obligations, such as appropriate contractual protections, where required. This includes assessing the relevant overseas recipients and onward processing, rather than relying only on a data-centre country, encryption or provider certification. Where we act as a Customer's data intermediary, we also follow agreed transfer instructions and provide the cooperation needed for the Customer's applicable obligations.

The disclosed Singapore, India, United Kingdom and Netherlands processing chain remains subject to those requirements. Selecting the Service or accepting this Policy is not a blanket waiver of overseas-transfer protection.

Additional international requirements. Where another applicable law restricts a transfer, we will not carry it out unless that law and any contractual restrictions are satisfied. Depending on the relevant law and transfer, safeguards may include:

  • A valid adequacy decision covering the actual destination and recipient.
  • Applicable European Commission Standard Contractual Clauses, using the appropriate transfer module, together with any required transfer assessment and supplementary safeguards.
  • The applicable UK transfer addendum or International Data Transfer Agreement, or Swiss adaptations, where required for the relevant data.

We do not rely on the EU-US Data Privacy Framework merely because a supplier operates in the United States. Reliance is possible only where the relevant recipient has a valid, applicable certification covering the transfer and the framework remains legally available. No claim is made here that Kumify, a Singapore company, is itself certified under that framework.

The applicable DPA or transfer schedule identifies the mechanism actually used for the relevant Service Data transfer. A DPA without an appropriate transfer mechanism is not, by itself, sufficient for every restricted transfer. Customers and individuals may request information about the applicable safeguards and, where legally required, a copy with legitimate confidential information appropriately protected.

6.3 Customer-directed restores and exports

If a Customer directs restoration or export to another mailbox, device or provider, the destination may be in a different country. The Customer must have lawful authority for that destination and comply with applicable transfer and disclosure restrictions. We follow lawful instructions and our own applicable duties; Customer instructions do not waive a written residency restriction or authorise an unlawful transfer.

7. User Rights & Disclosures

7.1 Rights concerning Account Data

Singapore PDPA rights. Subject to applicable conditions and exceptions, you may:

  • Request access to Personal Data about you in our possession or control and information about its use or disclosure during the preceding year.
  • Request correction of errors or omissions in that Personal Data.
  • Withdraw consent on reasonable notice, as described in Section 3.3.
  • Ask about our Personal Data practices and raise a complaint with our DPO or the PDPC.

The PDPA does not provide an unconditional general right to erase every record immediately. You may request account or mailbox deletion under our Service controls and Section 4, and we must meet applicable retention and consent-withdrawal duties. We will not treat a technical storage lock or a contractual term as overriding a legal obligation.

Additional rights where other laws apply. Depending on the law and its conditions and exceptions, you may also have rights to:

  • Obtain information about processing and access or receive a copy of your Personal Data.
  • Correct inaccurate or incomplete information.
  • Request deletion or restriction of processing.
  • Object to processing based on legitimate interests, and to any direct marketing.
  • Receive qualifying information in a portable format.
  • Withdraw consent without affecting earlier processing that was lawful.
  • Complain to a competent data protection authority and pursue available remedies.

Contact Kumify using Section 7.7 to exercise rights concerning Account Data for which we are responsible. You can also update supported account details in the dashboard. Rights requests are not limited to paid Customers.

7.2 Rights concerning backed-up emails

If your Personal Data appears in Service Data for which your employer, another organisation or another Customer is the responsible organisation under the PDPA or the Controller under another applicable law, direct your request to that organisation, its privacy contact or the relevant system administrator. Kumify generally cannot independently decide whether to disclose, change or delete another Customer's email records.

If we receive such a request directly, we will, where appropriate and lawful, refer it to the responsible organisation or Controller or help identify the proper route. We assist that party under the DPA and applicable law and act on its lawful instructions. We will not disclose mailbox contents merely because a requester knows an email address or appears in a message. Nothing in this procedure limits a duty imposed directly on us by law.

If you are an individual Customer backing up your own personal mailbox, you may use available account controls or contact us directly. A household account does not give one family member automatic access to another person's mailbox. Rights requests must consider other individuals' privacy and applicable exemptions. Deletion from a live mailbox alone does not erase backup history; Section 4 describes how backup deletion works.

7.3 Verification, timing and California information

We may request proportionate information to verify identity, authority or an authorised agent's mandate. We do not require unnecessary sensitive documents or a new account solely to submit a request. We respond within applicable statutory deadlines and explain any lawful restriction, fee or refusal. For a PDPA access or correction request, we respond as soon as reasonably possible; if we cannot provide access or make the requested correction within 30 days after receiving it, we notify you in writing within those 30 days of when we will respond. We preserve relevant requested data where the law requires it rather than letting ordinary deletion defeat the request. Any permitted access fee is explained before it is incurred; we do not charge for correcting Personal Data under the PDPA.

Where the GDPR applies, its generally one-month response period and legally permitted extensions apply separately. We do not unlawfully discriminate against a person for exercising privacy rights.

Where the CCPA applies, the categories described in Section 2 include identifiers, customer and billing records, commercial subscription information, internet or electronic-network activity, professional information where supplied, and sensitive information such as account credentials and email contents. Sources are identified in Section 2.4, purposes in Section 3, retention periods or criteria in Section 4, and recipient categories in Sections 5 and 7.4. The categories actually collected depend on your relationship with us and the contents of connected mailboxes.

California residents may have rights to know, access, correct and delete information; to opt out of sale or sharing; and to limit certain uses or disclosures of sensitive information, subject to applicable conditions. We do not sell Personal Data or share it for cross-context behavioural advertising, and do not use sensitive information to infer characteristics or for unrelated purposes requiring a right-to-limit mechanism. We do not operate advertising uses that require an opt-out; where an applicable opt-out signal or Global Privacy Control is relevant, we will honour it as required by law. We do not offer financial incentives in exchange for Personal Data.

For Service Data handled as a CCPA service provider or contractor, we restrict use and disclosure to the specified contracted purposes and other legally permitted processing, do not sell or share that data, and provide required assistance to the Customer business. This does not prevent an individual from contacting us or a regulator about our own obligations.

7.4 When we disclose information

We disclose Personal Data only as necessary for the purposes described in this Policy and with appropriate legal authority, including:

  • Customer-authorised access: To authorised account users and the destinations selected for lawful restores or exports, subject to their roles and private-mailbox restrictions.
  • Service providers: To the providers described in Section 5, for their limited contracted functions. Billing, notification and form-security providers receive information necessary for those functions rather than general access to mailbox archives.
  • Professional advisers: Relevant Account Data to legal, accounting or other advisers subject to confidentiality. Service Data is not routinely disclosed to advisers; any access must have a specific lawful basis and comply with applicable Customer instructions and agreements.
  • Legal requirements: Information we are legally required to disclose under binding, applicable legal process, after assessing authority, scope and relevant cross-border restrictions. We seek to limit disclosure and notify the Customer where legally permitted. We do not voluntarily provide unrestricted government access to mailbox archives.
  • Business restructuring: Relevant information in a proposed or completed merger, acquisition, financing or asset transfer, subject to confidentiality, data minimisation and applicable law. Any transfer of Service Data must preserve its contractual restrictions and comply with required Customer authorisations and transfer safeguards; a transaction does not authorise unrelated reuse.
  • Your specific direction: Information you ask or lawfully authorise us to disclose for a clearly identified purpose.

We do not disclose Service Data to advertisers or data brokers. A general interest in protecting a business does not give us an unrestricted right to share email contents. We will assess necessity, lawful authority and contractual restrictions before any other security-related disclosure.

7.5 Customers' responsibilities and independent services

Customers must manage user permissions, provide required notices, establish lawful retention and processing instructions, and consider the effect of locked and immutable recovery points on privacy obligations. We remain responsible for our own applicable legal duties.

Your original email provider and any destination or independent service you select may handle information under its own privacy terms. This Policy governs Kumify's processing and does not replace those providers' notices or our obligations regarding providers we engage ourselves.

7.6 Changes to this Policy

We will publish updates with a revised version and effective date. For material changes, we will give advance notice to Customers by email or a prominent dashboard notice where practicable, and provide any notice or obtain any consent required by law. Urgent legal or security changes may require a shorter period, with notice as soon as practicable.

We will not use a policy update to expand our rights over existing Service Data contrary to Customer instructions, an executed DPA or applicable law. Continued use is not a substitute for specific consent where the law requires it. Existing statutory rights remain unaffected.

7.7 Contact and complaints

Kumify remains accountable for compliance with the PDPA obligations applicable to it. Our Data Protection Officer ("DPO") is the contact for Personal Data enquiries, consent withdrawal, rights requests and complaints. You can route a request to the DPO through:

  • Contact form: https://www.kumobunker.com/contact
  • Existing Customers: The support channel in your KumoBunker account.
  • Request label: "PDPA request - for the Data Protection Officer".

Please identify the account or relationship involved and the nature of the request. Do not include passwords, private keys, unnecessary health or financial information, or copies of unlawful content. We can arrange an appropriate method for sensitive information if needed.

We accept sufficiently clear written requests through the published privacy contact routes; a particular form or label is not compulsory. We will explain the complaint outcome or any next steps within a reasonable period. Delegating handling to staff or a provider does not remove Kumify's accountability.

You may also complain to Singapore's Personal Data Protection Commission or another competent supervisory authority, including an authority available to you under the GDPR, without first having to resolve the matter with us. Nothing in this Policy limits mandatory consumer or data protection rights.

Kumify Pte. Ltd. Incorporated in Singapore | UEN 202647131C KumoBunker | https://www.kumobunker.com

Every mailbox, kept safe somewhere else.

Start free trial

Product

  • How it works
  • Why us
  • Pricing
  • Storage calculator
  • Free trial

Use cases

  • Who it's for
  • cPanel, Plesk & DirectAdmin email
  • Gmail & Google Workspace
  • Moving to a new host
  • Ransomware & hacked mailboxes
  • Business continuity
  • All use cases

Company

  • About
  • Contact
  • Support
  • Sign in

Legal

  • Terms of Service
  • Privacy Policy
  • Acceptable use
  • Refunds
  • SLA
KumoBunker© 2026 Kumify Pte. Ltd. (incorporated in Singapore, UEN 202647131C).
All rights reserved.