MurrCloud Accounting

Policy version na-2026-11-02-v3

Exports, workspace closure and retention

Policy bundle: `na-2026-11-02-v3`

Effective date: 2026-11-02

This Accounting SaaS notice takes priority over the generic website's 90-day reactivation description. Owner-confirmed deletion receives no added 90-day period. The scheduled archive transition below applies from 3 November 2026 at 00:00 UTC. Earlier accepted policy records remain available at their original versioned URLs. Registration remains gated on verified policy, backup, workflow and capacity checks; publication of this notice alone does not open registration.

Export your required records

ExportScopeLimit
Native CSV/XLSX and report downloadsSelected records/periods within the user's accounting permissionsA selected list is not a complete backup; list exports exclude attachments.
Portable accounting CSV ZIPFixed company/accounts/journals/partners/taxes/entries/entry-line projections with counts and hashesExcludes attachments and some business/configuration models.
Full workspace ZIPNative database image, manifest and attachmentsContains password hashes, invitation tokens and configuration; protect and encrypt your downloaded copy.

The authorized owner must re-enter the current password and exact company name for full export requests and downloads. The asynchronous export default is 64 MiB compressed and ten minutes in the initial production release. Consistent capture briefly stops workspace access and writes. Larger exports require an arranged, measured alternative. Download authorization expires after 24 hours. The production lifecycle cycle removes expired generated server artifacts; it cannot delete a user-held download. An export request or download is not an instruction to close the workspace.

Scheduled tenant archives and retention transition

For admitted workspaces, the service schedules a consistent native database-and-attachment archive daily, encrypts it before transfer from the Boston tenant host to the separate Hostinger Server A in Singapore, then checks remote readback. A capture briefly interrupts the workspace. New archives captured from 3 November 2026 at 00:00 UTC have 15 days of recoverable history, subject to owner-authorized earlier closure and the stated retained-copy boundary. This is not a guarantee that a backup succeeds every day; failed or stale captures raise alerts and close new admission. Restoration is an operator-assisted procedure, not a customer self-service or fixed recovery-time commitment. Quarantined native restore validation targets a weekly cycle; failed, stale or incomplete checks raise alerts and close new admission. A whole-server disaster requires the separately held recovery key and current closure records.

Archives created before that cutoff keep their original 30-day window; an interrupted capture started before the cutoff and uploaded later also keeps 30 days. The window is measured from archive creation/upload receipt, so delayed uploads do not shorten it. An existing recovery point is not deleted early to implement this change. Owner-authorized workspace closure still takes priority. This change affects recovery copies, not the accounting records in a live workspace.

The current service admits no more than five workspaces. Each compressed native backup must fit within 128 MiB; the encrypted envelope must fit within 129 MiB. The shared archive allowance is 25,000,000,000 bytes, with a separate free-space floor. During transition the store reserves up to 32 points per workspace to preserve old copies; steady 15-day operation normally needs 16 daily boundary points plus one recovery slot. These are operational limits, not a promise of unlimited storage or eight-workspace server capacity. Oversize, quota, disk or backup-health failures raise alerts and stop new admission. Retention is never shortened silently to admit another company. Contact contact@murrcloud.com for recovery assistance or a capacity review before your workspace outgrows its limit.

Backup history is not your statutory accounting-record retention. Preserve the independent records and exports required by your tax/accounting obligations. A 15-day archive history does not mean you can discard older required records.

Owner-confirmed workspace deletion

Deletion closes the whole company workspace and all users, rather than removing a colleague. The owner chooses processing as soon as eligible, after seven days or after 30 days; confirms the exact company name and current password; and acknowledges that needed exports were obtained or explicitly chooses to proceed without another export. Scheduling deletion does not create an export. Normal access continues until the chosen deadline/execution begins, subject to a separate incident or service restriction. Cancellation is possible before execution starts. Once execution starts, it cannot be cancelled through the owner interface.

At the selected deadline, processing fences writers and runtime restarts, removes the exact live database/runtime files and the service-managed tenant archive store, and scrubs linked registration contacts and known service-mail generations. An immediate choice requests processing as soon as eligible; it does not establish instantaneous erasure. Unknown supported-scope copies, identity/permission failures or unfinished removal checks block completion.

A **completed workspace-deletion status** means those live-workspace and tenant archive-store checks passed. It does **not** say that every provider copy has been physically erased. In this version, the full-purge and full-backup-erasure flags remain false while restricted provider copies may remain.

Restricted provider whole-VPS copies

Hostinger's automatic whole-VPS backups are separate from the per-tenant archive store. The observed Server A copies are in India (daily schedule); Server B's are in the United States (weekly schedule). They can include tenant information, keys, configuration and operational records. Hostinger does not offer selective removal of one tenant from such a copy. The operator's accepted boundary is to restrict these retained copies to disaster recovery until observed provider rotation removes the listed generations. Backup counts and daily/weekly labels do not establish a guaranteed erasure date. Unlisted or in-progress provider copies are outside what a listed inventory proves; physical provider erasure is not independently verified.

Any provider restore must start in quarantine. Current closure records must be reconciled and closed tenants removed before service or mail is enabled. An old provider copy must not recreate a closed workspace merely because it contains an old database or runtime configuration. Provider inventory freshness/drift is monitored; a stale or inconsistent inventory closes production readiness rather than inventing an erasure receipt. Further legally required retention, if any, must be identified and explained rather than marked erased.

Restricted evidence and copies outside service control

Consent/allocation/deletion evidence remains restricted after workspace removal to prevent stale work from recreating a closed tenant and document the action. It includes UUIDs, reserved database/hostname/port, policy version/manifest and document hashes, consent timestamps, request hashes and deletion receipts. Database and hostname values can identify the company; they are not anonymous. There is no automatic expiry for these tombstones. Access and continued need require operator review; no unimplemented purge date is promised.

Delivered recipient emails, customer-held exports and independently controlled third-party records remain outside the service's removal control. Account- specific mail-provider logs/copies, support/incident logs and operational rollback artifacts are not covered by a claim of immediate full erasure. Their complete inventory and automatic pruning are not asserted in this notice. Contact contact@murrcloud.com about a specific record or retention request.

Other operational records

Verification links expire after 30 minutes; expiry alone does not erase an abandoned registration. No automatic abandoned-registration deletion period is promised. Registration abuse counters have a bounded cleanup method for buckets older than two days. No automatic counter-cleanup schedule is promised by this notice. User invitations are single-use with no time expiry and may be revoked. Known app mail generations are linked for lifecycle scrubbing; a message already delivered to a recipient is separate.

Read with Privacy and Processing and cookies.