Information should remain available for as long as it is legitimately required, and no longer.
Document details
- Document version
- 1.0
- Effective date
- October 2026
- Policy owner
- Voyj
- Review cycle
- At least annually, and following any material change to applicable law, infrastructure, data processing arrangements or Voyj services
- Classification
- Public
This policy is published by Nian Marketing Pty Ltd (ABN 80 149 763 093), the operator of Voyj. Voyj is an Australian-operated service. Where this policy refers to Voyj, it refers to us. This policy should be read together with our Privacy Policy, Terms of Service, Security policy and Data Deletion and Privacy Requests page.
1. Purpose
We provide technology used by career coaches, career practitioners and other organisations to manage client relationships, cases, communications, assessments, documents, meetings and related professional activities.
In providing these services, we store and process information on behalf of our customers. Some of this information may constitute personal information or sensitive information.
This policy establishes the principles and requirements governing:
- where and how data is stored;
- how long data is retained;
- the responsibilities of us and our customers;
- backup and recovery data;
- customer access and export;
- deletion of data;
- account termination;
- legal retention requirements;
- data held by service providers and subprocessors; and
- continuity and data access should we cease providing the service.
This policy is intended to ensure that information is retained only for legitimate purposes and for no longer than necessary, while maintaining appropriate availability, security and resilience.
2. Scope
This policy applies to information stored or processed by us in connection with the Voyj platform and associated services.
This includes, where applicable:
- organisations and user accounts;
- client records;
- case records;
- contact information;
- notes;
- goals and action plans;
- assessments and assessment results;
- documents and attachments;
- email and communication records;
- calendar and appointment information;
- meeting information;
- audio and video recordings;
- transcripts;
- system-generated records;
- audit and security logs;
- configuration information; and
- backups containing any of the above.
This policy applies to production systems and to supporting infrastructure operated by us or by third-party service providers acting on our behalf. It does not establish retention requirements for copies of information exported from Voyj and subsequently held by a customer outside the Voyj platform.
3. Policy Principles
We apply the following principles to the storage and retention of information.
3.1 Customer control
Customers control the business records and client information they place within Voyj, subject to applicable law and our contractual obligations.
We do not claim ownership of customer content.
Customers determine why information relating to their clients is collected, the information they choose to retain within Voyj, and the period for which their professional, regulatory or legal obligations require them to retain it.
3.2 Purpose limitation
We store customer information for the purpose of providing, securing, maintaining and supporting the Voyj service and for other purposes permitted by the applicable agreement, Privacy Policy or law.
Information must not be retained merely because storage is technically possible or inexpensive.
3.3 Data minimisation
We seek to avoid collecting or retaining information that is unnecessary for operation of the service.
Where information is no longer reasonably required for an authorised purpose, and there is no legal or contractual requirement to retain it, it should be deleted or appropriately de-identified.
3.4 Security throughout the lifecycle
Information must be appropriately protected throughout its lifecycle, including during:
- collection;
- transmission;
- active storage;
- backup;
- retrieval;
- export;
- archival where applicable; and
- deletion.
3.5 Portability
Customers must have reasonable mechanisms to retrieve their information from Voyj.
We do not deliberately use data lock-in as a mechanism for preventing a customer from leaving the service.
3.6 No indefinite retention by default
We do not adopt indefinite retention of customer data as our default position.
Retention must have a legitimate operational, contractual, legal or customer-directed purpose.
4. Roles and Responsibilities
4.1 Customer responsibility
Customers are responsible for determining the records they are required to maintain in connection with their professional activities.
This includes determining any retention requirements arising from:
- applicable legislation;
- professional standards;
- contractual obligations;
- insurance requirements;
- government programs;
- funding arrangements;
- dispute or litigation requirements; and
- their own organisational policies.
We do not determine the statutory or professional retention period applicable to an individual customer’s records unless explicitly agreed as part of a specific service. The availability of information within Voyj does not relieve a customer of its own recordkeeping obligations.
4.2 Our responsibility
We are responsible for operating the platform in accordance with this policy and for applying appropriate technical and organisational measures to information we hold.
We are responsible for:
- providing appropriate storage infrastructure;
- protecting stored information;
- maintaining appropriate backup and recovery capabilities;
- enforcing access controls;
- supporting deletion and retention processes;
- providing data export capabilities;
- managing relevant service providers and subprocessors; and
- maintaining procedures for account termination and service discontinuation.
Where we hold personal information for the purposes of Australian privacy law, we will comply with applicable obligations under the Privacy Act 1988 (Cth) and the Australian Privacy Principles.
5. Storage of Customer Data
5.1 Primary storage
Voyj customer data must be stored using infrastructure we approve for production use.
Production customer data must not be copied to:
- personal devices;
- unmanaged storage;
- personal cloud storage accounts;
- unapproved development environments; or
- other systems not authorised for production customer information, except where specifically authorised under a documented operational or incident-management procedure.
5.2 Data residency
We will identify the primary hosting region applicable to a customer’s service where a specific data residency commitment forms part of the service or customer agreement.
For Australian-hosted services, our intention is that primary persistent customer data is stored in Australian infrastructure unless otherwise disclosed or agreed.
A primary storage location does not necessarily mean that information will never be technically processed outside that location.
Certain authorised service providers may process limited information in other jurisdictions where required to provide a particular function. Such processing must be managed in accordance with our Privacy Policy, contractual obligations, security requirements and applicable law.
5.3 Third-party infrastructure
We may use cloud infrastructure providers and specialised service providers to store or process information.
Where a provider stores or otherwise holds customer information on our behalf, we must take reasonable steps appropriate to the nature of the service to ensure that:
- information is handled only for authorised purposes;
- appropriate security protections apply;
- access is restricted;
- subcontracting is appropriately controlled;
- data can be retrieved where required; and
- data can be deleted or rendered inaccessible when it is no longer required.
5.4 Encryption
We protect customer data using multiple layers of encryption, including encryption at rest, in transit, and at the application level for designated personally identifiable information (PII).
Customer data stored within our approved production infrastructure, including databases, documents, attachments, recordings and backups, must be encrypted at rest using industry-standard encryption.
In addition to infrastructure-level encryption, designated PII stored within our databases is encrypted at the application or data-record level. This provides an additional layer of protection for sensitive data independently of the encryption applied to the underlying database and storage infrastructure.
Customer data transmitted between users, our systems and authorised service providers must be encrypted in transit using current industry-standard secure transport protocols.
Encryption keys and credentials must be appropriately protected, access-controlled and managed separately from the data they protect where technically applicable.
We periodically review our encryption standards and may update the underlying technologies and cryptographic mechanisms as industry standards and security requirements evolve.
6. Customer Data Retention
6.1 Active customers
Unless a different retention rule applies, customer data may be retained for the duration of the customer’s active Voyj service.
We do not impose a universal seven-year retention period on all customer data.
Different customers and different classes of records may be subject to different legal, professional or business retention requirements.
Customers may therefore retain information within Voyj for as long as they reasonably require it while maintaining an active service, subject to:
- their service plan;
- applicable storage limits;
- applicable law;
- this policy; and
- any specific contractual arrangements.
6.2 Customer-managed deletion
Where we provide deletion functionality, customers may delete records that they determine are no longer required.
Deletion from the active application does not necessarily result in immediate physical erasure from every underlying system or backup.
Deleted information will progress through our deletion lifecycle as described in this policy.
6.3 Customer retention policies
We may provide functionality allowing customers to establish automated retention rules for particular classes of information.
Where such functionality is available, the customer remains responsible for determining an appropriate retention period.
We may provide recommended defaults or guidance, but these do not constitute legal advice and do not override a customer’s legal or professional obligations.
7. Our Business and Operational Records
Some information generated through operation of Voyj is retained independently of the customer’s underlying content.
This may include:
- subscription and billing records;
- invoices and transaction records;
- contractual records;
- authentication records;
- security events;
- audit records;
- service activity records;
- support correspondence; and
- records required to establish or defend legal rights.
These records may be retained after customer content has been deleted where reasonably required for:
- legal or regulatory compliance;
- taxation and accounting;
- fraud prevention;
- security;
- audit;
- dispute resolution; or
- establishment, exercise or defence of legal claims.
Retention of such records must be limited to information reasonably necessary for the relevant purpose. Where possible, operational records should avoid retaining the underlying customer content itself.
8. Backups and Recovery
8.1 Purpose of backups
Backups exist to support:
- disaster recovery;
- business continuity;
- protection against accidental deletion;
- recovery from system failure;
- recovery from malicious activity; and
- restoration following a security incident.
Backups are not archives and must not be used as a mechanism for circumventing customer deletion or retention requirements.
8.2 Backup retention
We will maintain backup retention periods based upon recovery requirements, infrastructure design, security requirements and the sensitivity of the information concerned.
Backup periods must be documented internally and periodically reviewed.
We will not retain backup copies indefinitely.
8.3 Information deleted from active systems
When information is deleted from our active systems, copies of that information may remain temporarily within protected backups.
Such information:
- must not be restored to active use except as part of a legitimate system recovery;
- must not be accessed for ordinary business purposes;
- must remain protected by appropriate access controls; and
- must expire through the normal backup lifecycle.
Where a system restoration reintroduces information that had previously been deleted, we must take reasonable steps to ensure that applicable deletion requirements are reapplied.
8.4 Backup security
Backups containing customer information must receive security protection appropriate to the information they contain.
Backup access must be restricted to authorised personnel and systems.
We must maintain appropriate recovery procedures and periodically verify that critical information can be restored.
9. Data Export
9.1 Export during active service
We will provide customers with reasonable mechanisms for exporting their information.
Customers should not need to terminate their Voyj service in order to obtain a copy of their information.
The available export mechanisms may differ according to the type and volume of information.
9.2 Large datasets
For customers with large quantities of information, including recordings, documents or other large binary objects, we may provide export through mechanisms other than a single downloadable archive.
These mechanisms may include:
- staged exports;
- machine-readable data exports;
- bulk object transfer;
- transfer to customer-controlled storage; or
- other secure transfer mechanisms.
The objective is to provide practical data portability without requiring us to construct impractically large single-file downloads.
9.3 Customer-controlled archives
Where supported by us, customers may transfer or archive information to customer-controlled storage.
Once information has been successfully transferred to customer-controlled storage and removed from Voyj, the customer assumes responsibility for the security, availability, backup, retention and deletion of that copy.
10. Account Termination
10.1 Customer-initiated termination
Customers are encouraged to export information they wish to retain before terminating their service.
Following termination, we will provide a defined post-termination period during which eligible customer data may remain available for retrieval or export.
Unless otherwise specified in the applicable agreement, our target post-termination retrieval period is 90 days.
During this period:
- access may be limited to administrative and export functions;
- the service may no longer support normal operational use; and
- applicable charges may continue where significant storage or specialised export services are required.
10.2 End of retrieval period
Following expiry of the post-termination retrieval period, we may delete customer data from active systems.
Once active deletion has commenced, recovery of the data is not guaranteed.
Residual copies may remain within backups until those backups expire in accordance with our backup lifecycle.
10.3 Immediate deletion
Where technically and legally permissible, a customer may request deletion before the end of the standard retrieval period.
We may require appropriate verification and confirmation before performing irreversible deletion.
We may retain limited information where required by law or reasonably required for security, fraud prevention, dispute resolution or establishment or defence of legal rights.
11. Legal Holds and Required Retention
Deletion or automated retention processes must be suspended where we are legally required to preserve particular information.
This may occur in response to:
- a court order;
- subpoena or other compulsory legal process;
- applicable statutory requirements;
- a regulatory requirement;
- an active legal dispute; or
- a reasonably anticipated legal proceeding requiring preservation of evidence.
A legal hold must apply only to information reasonably within the scope of the preservation requirement.
When the requirement ends, the information must return to its ordinary retention lifecycle unless another lawful basis for retention exists.
We will not retain customer information indefinitely merely because it might conceivably become relevant to a future dispute.
12. Destruction and De-identification
We will take reasonable steps to destroy or appropriately de-identify personal information when it is no longer required for an authorised purpose and is not required to be retained by law.
Deletion must address information under our control across relevant systems, including third-party systems where applicable.
Technical limitations may mean that deletion occurs progressively rather than instantaneously.
Where immediate physical destruction is impractical, information must be placed beyond ordinary use and remain protected until permanent deletion occurs through the applicable lifecycle.
De-identified information may be retained where there is a legitimate purpose for doing so, provided that we have taken reasonable steps appropriate to the circumstances to prevent individuals from being reasonably identifiable.
We must not describe information as anonymous or de-identified where there remains a material and reasonably practicable means of identifying the individual.
13. Service Providers and Subprocessors
We remain responsible for managing the lifecycle of information entrusted to service providers acting on our behalf to the extent required by applicable law and our contractual arrangements.
We must consider a provider’s ability to:
- appropriately protect information;
- restrict its use;
- meet relevant data location requirements;
- return or export information;
- delete information;
- manage backups appropriately; and
- apply equivalent obligations to relevant subcontractors.
We must not intentionally retain information indefinitely within a third-party service after the information has been deleted from Voyj merely because deletion from that provider is inconvenient.
14. Security Logs and Audit Information
Security and audit logs may require different retention periods from customer content.
Logs should contain only the information reasonably necessary for their operational and security purpose.
Where practicable, sensitive customer content should not be written to application, diagnostic or security logs.
Logs may be retained for purposes including:
- security monitoring;
- incident investigation;
- fraud detection;
- troubleshooting;
- auditing; and
- demonstrating compliance.
Log retention periods must balance these requirements against privacy, security and storage risks.
15. Development and Test Environments
Production customer information must not routinely be copied into development or test environments.
Where production information is exceptionally required for diagnosis or testing:
- its use must be authorised;
- only the minimum necessary information may be used;
- access must be restricted;
- de-identification or masking must be used where practicable; and
- the information must be removed when the authorised purpose has been completed.
Synthetic or appropriately de-identified test data should be used wherever reasonably possible.
16. Voyj Service Discontinuation
We recognise that customers may rely upon the platform to hold important business and client records.
We must therefore maintain reasonable business continuity arrangements addressing the possibility that we permanently discontinue the service.
Where we make a planned decision to discontinue the service, we will seek to provide customers with reasonable advance notice and an opportunity to export their information.
Our continuity objective is to provide customers with at least 90 days, where reasonably practicable, in which to retrieve or export their data following notice of permanent service discontinuation.
We will maintain data export capabilities as a core part of our continuity strategy.
Nothing in this policy constitutes a guarantee that we can continue operating our full application platform for a particular period following insolvency, external administration, catastrophic failure or circumstances outside our reasonable control.
Instead, our continuity planning will prioritise preservation of customer access to, and export of, customer data.
Where appropriate, we may maintain technical or operational arrangements designed to allow limited data retrieval or export independently of normal application operations.
17. Insolvency
If we become insolvent or enter external administration, customer information does not become our property merely because it is stored on Voyj infrastructure.
Subject to applicable law and the authority of any appointed administrator, liquidator or other controller, our continuity arrangements should prioritise:
- maintaining the security and integrity of customer information;
- notifying customers where reasonably possible;
- maintaining or establishing a mechanism for customer export;
- providing a reasonable period for retrieval where circumstances permit; and
- securely disposing of remaining customer information when continued retention is no longer required.
We will design our systems and operational procedures with the objective that customer data portability does not depend solely upon our continued operation as a going concern.
18. Security Incidents
A security incident does not automatically alter the applicable retention period.
Information relevant to investigation of an incident may, however, be preserved for longer than its normal retention period where reasonably required for:
- investigation;
- remediation;
- regulatory reporting;
- insurance;
- law enforcement;
- legal proceedings; or
- demonstrating the actions taken by us.
Any such extended retention must be proportionate to the purpose.
19. Exceptions
Exceptions to this policy must be:
- justified by a legitimate business, technical or legal requirement;
- appropriately risk assessed;
- approved by an authorised representative of ours; and
- documented where material.
An exception must not be used merely to avoid implementing a reasonable deletion or retention control.
20. Compliance and Review
We will periodically review our information storage and retention practices to ensure they remain appropriate to:
- the nature and scale of the Voyj service;
- the information being processed;
- customer requirements;
- contractual obligations;
- technological changes;
- security risks; and
- applicable laws and regulations.
Material changes to infrastructure or service providers must include consideration of their impact on storage, retention, deletion, recovery and data residency. This policy will be reviewed at least annually.
21. Relationship With Our Other Policies
This policy should be read together with our:
- Privacy Policy;
- Information Security Policy;
- Artificial Intelligence Policy;
- Business Continuity and Disaster Recovery arrangements;
- Terms of Service;
- Data Processing Agreement, where applicable; and
- applicable customer agreements.
Where another binding agreement establishes a specific retention requirement, that requirement takes precedence to the extent of any inconsistency with this general policy. Applicable law always takes precedence over this policy.
22. Definitions
- Active systems
- Production systems used in the normal operation of Voyj and from which information is ordinarily accessible.
- Backup
- A copy of information maintained primarily for system recovery, disaster recovery or business continuity.
- Customer
- An organisation or individual that has entered into an agreement to use Voyj.
- Customer data
- Information submitted to, generated through or stored within Voyj on behalf of a customer, excluding information generated and held solely for our own corporate purposes.
- De-identification
- A process intended to ensure that information is no longer about an identifiable or reasonably identifiable individual.
- Deletion
- Removal of information from ordinary operational use, followed by destruction, expiry or other measures appropriate to the system in which the information is held.
- Legal hold
- A temporary suspension of ordinary deletion processes where information must be preserved for a legal, regulatory or dispute-related purpose.
- Personal information
- Information or an opinion about an identified individual, or an individual who is reasonably identifiable, as defined by applicable Australian privacy law.
- Production data
- Information held within our live production environment.
- Retention period
- The period for which information is maintained before deletion or de-identification.
- Sensitive information
- Information falling within the definition of sensitive information under applicable Australian privacy law.
23. Policy Statement
Our approach to data retention is based on a simple principle:
Information should remain available for as long as it is legitimately required, and no longer.
We will provide customers with control over their records, reasonable data portability, appropriate resilience and backup, and a defined path for deletion. We will not use indefinite retention as a substitute for proper information lifecycle management.
24. Applicable Law and Jurisdiction
We are an Australian-operated service and this policy is established with reference to applicable Australian laws and regulatory requirements, including the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).
Where we provide services to customers or process personal information subject to the laws of another jurisdiction, additional legal or contractual requirements may apply.
Nothing in this policy is intended to limit any rights or obligations that cannot lawfully be excluded or modified under applicable law.
Where a customer agreement establishes specific data residency, retention, deletion or regulatory requirements, those requirements apply in addition to this policy and prevail to the extent of any inconsistency.
How to contact us
Nian Marketing Pty Ltd (ABN 80 149 763 093)
Email: privacy [at] voyj.app
Phone: 07 3732 4976
Postal: PO Box 3472, Norman Park QLD 4170, Australia
Have a question? Back to voyj.app