Data Retention & Deletion Policy

1. Purpose

This Data Retention & Deletion Policy (“Policy”) explains how TP-CAMP OneSuite (“OneSuite,” “TP-CAMP,” “we,” “us,” or “our”) retains, archives, deletes and otherwise manages information throughout its lifecycle.

The objectives of this Policy are to:

• avoid retaining information indefinitely without legitimate reason;
• give customers appropriate control over their information;
• preserve records necessary to operate OneSuite;
• maintain the integrity of music-rights and ownership records;
• meet legitimate financial, security and legal requirements;
• protect customers and TP-CAMP from fraud and disputes;
• maintain appropriate audit history; and
• establish a consistent framework for account closure and data deletion.

This Policy applies throughout the OneSuite ecosystem.

2. Scope

This Policy may apply to information processed through:

• OneSuite accounts;
• customer workspaces;
• Catalog;
• Splits;
• Operations;
• Invoice;
• Finance;
• AI-assisted functionality;
• contracts and documents;
• electronic-signature functionality where available;
• integrations;
• customer support;
• CRM and communications;
• payment records;
• security systems;
• audit records;
• backups; and
• other OneSuite services.

3. General Retention Principle

TP-CAMP seeks to retain information only for as long as reasonably necessary for legitimate purposes.

Those purposes may include:

• providing OneSuite;
• maintaining customer accounts;
• preserving customer records;
• completing transactions;
• maintaining music-rights information;
• supporting cross-application functionality;
• providing customer support;
• preventing fraud;
• maintaining security;
• resolving disputes;
• enforcing agreements;
• meeting accounting requirements;
• complying with legal obligations;
• establishing or defending legal claims; and
• maintaining reasonable business records.

Different categories of information may therefore have different retention periods.

4. Retention Is Not the Same for Every Record

OneSuite processes different types of information with different operational, legal and business purposes.

For example:

• a temporary authentication token may need to exist only briefly;
• an active customer profile may be required while an account remains active;
• an invoice may need to be preserved after a subscription expires;
• a rights-ownership revision may need to remain available as historical evidence;
• a security log may need to be retained to investigate suspected misuse; and
• backup copies may remain temporarily after information has been removed from active systems.

TP-CAMP therefore does not apply one universal deletion period to every category of information.

5. Active Accounts

While a OneSuite account or workspace remains active, TP-CAMP may retain information reasonably necessary to provide the Services.

This may include:

• account information;
• workspace information;
• team membership;
• permissions;
• catalogue information;
• ownership and split information;
• operational information;
• invoices;
• financial records;
• contracts;
• documents;
• communications;
• integration information; and
• other Customer Data.

Users may be able to edit or delete certain records during normal use, subject to application permissions and legitimate record-preservation requirements.

6. Expiry Is Not Immediate Deletion

Expiration of a subscription, access period, trial or complimentary entitlement does not necessarily cause immediate deletion of the customer's account or Customer Data.

Following expiry, OneSuite may:

• restrict access;
• make certain functionality read-only;
• disable editing;
• disable particular applications;
• preserve existing records;
• permit renewal or reactivation; or
• otherwise limit functionality according to the applicable plan or service.

This allows customers an opportunity to renew and helps prevent accidental loss of important business and rights information.

7. Cancellation Is Not Immediate Deletion

Choosing not to renew or requesting cancellation does not necessarily mean that all Customer Data will immediately be deleted.

Cancellation concerns continuation of access.

Deletion concerns what happens to stored information.

These are separate processes.

The consequences of cancellation are addressed further in the TP-CAMP OneSuite Cancellation Policy.

8. Account Closure

A customer may request closure of an account or workspace through the applicable OneSuite support or account-management process.

Before completing a closure request, TP-CAMP may take reasonable steps to:

• verify the identity of the requester;
• verify the requester's authority;
• confirm which workspace is affected;
• identify other workspace owners or administrators;
• determine whether unresolved obligations exist;
• determine whether records must be preserved; and
• prevent fraudulent or unauthorized deletion.

9. Workspace Authority

A team member's request to delete their own user account does not automatically authorize deletion of an organization's entire workspace.

Workspace-level deletion may require authorization from an appropriate:

• owner;
• administrator;
• authorized company representative; or
• other person with sufficient authority.

TP-CAMP may refuse or delay a workspace-deletion request where the requester cannot reasonably demonstrate appropriate authority.

10. Removing a Team Member

Removing a team member from a workspace does not ordinarily delete business records that the person created while acting within that workspace.

For example, removal of a user should not automatically delete:

• works they entered;
• recordings they entered;
• split records;
• invoices;
• contracts;
• project records;
• financial records;
• audit records; or
• other organizational information.

Such records may belong to or form part of the customer's workspace rather than the individual user's personal account.

11. Personal Profile Information

Where appropriate, personal profile information associated solely with a removed user may be deleted, anonymized or restricted when no longer necessary.

However, limited identifying information may remain where reasonably necessary to preserve:

• authorship of business records;
• audit trails;
• contract history;
• transaction history;
• security records;
• rights history; or
• legal evidence.

12. Music Catalogue Data

Catalog information may represent long-term business and rights-management records.

Such information may include:

• works;
• recordings;
• releases;
• titles;
• contributors;
• writers;
• publishers;
• performers;
• producers;
• labels;
• identifiers;
• registrations;
• ownership information; and
• related metadata.

TP-CAMP may retain catalogue information while an account remains active and for an appropriate period after access ends, subject to customer requests and legitimate retention requirements.

13. Ownership and Split Records

Ownership and split information may have legal, financial and evidentiary significance.

Deletion of a current ownership record does not necessarily require destruction of all historical information showing:

• previous ownership;
• previous percentages;
• changes;
• approvals;
• validations;
• revisions;
• synchronization events; or
• related audit information.

Historical information may be retained where reasonably necessary to maintain record integrity or address future disputes.

14. Rights History

OneSuite may preserve historical rights information where reasonably necessary to establish what information existed at a particular time.

This can be important where:

• contributors dispute ownership;
• publishing interests change;
• master ownership changes;
• a registration was previously submitted;
• an agreement changes;
• royalties are disputed; or
• TP-CAMP needs to investigate alleged unauthorized modification.

Preservation of historical information does not mean TP-CAMP claims ownership of the underlying rights.

15. Split Sheets

Split sheets may be retained while necessary for the customer's account and may also be retained after account closure where reasonably necessary for:

• evidentiary purposes;
• dispute resolution;
• audit history;
• contractual records;
• legal compliance; or
• defense of claims.

A customer deletion request will be considered in light of the rights and interests of all persons represented by the relevant record.

16. Rights Registrations and Submissions

Records associated with CWR files, registrations or submissions to music-industry organizations may be retained where reasonably necessary to document:

• what was submitted;
• when it was submitted;
• by whom;
• which data was included;
• the response received; and
• subsequent corrections or disputes.

Deleting the active OneSuite record may not cause an external organization to delete information already submitted to it.

Users may need to contact the relevant external organization separately.

17. Cross-Application Records

OneSuite applications may exchange or synchronize authorized information.

Deletion of information in one application may therefore affect related information elsewhere in the ecosystem.

TP-CAMP may implement deletion processes that:

• delete synchronized copies;
• remove active projections;
• preserve historical references;
• retain audit events; or
• otherwise maintain cross-application integrity.

OneSuite is not required to corrupt historical or financial records merely to make every prior reference disappear.

18. Operations Data

Operations-related information may include:

• projects;
• tasks;
• campaigns;
• milestones;
• workflows;
• KPIs;
• notes; and
• related records.

Such information may generally be retained while required by the customer and deleted or archived according to applicable account and retention rules.

19. Invoice Records

Invoices, quotations, credits, discounts, customer records, payment status and related transaction information may need to be retained after a subscription or account ends.

Retention may be necessary for:

• accounting;
• tax;
• financial reconciliation;
• customer disputes;
• payment disputes;
• audits;
• fraud prevention; and
• legal obligations.

A request to delete an account does not necessarily require TP-CAMP to destroy records it must or reasonably should retain for legitimate financial purposes.

20. Finance Records

Finance-related records may have longer retention requirements than ordinary application data.

TP-CAMP may retain appropriate financial records for periods reasonably necessary to satisfy:

• accounting requirements;
• tax requirements;
• financial reporting;
• reconciliation;
• fraud prevention;
• dispute resolution;
• contractual obligations; and
• applicable law.

21. Payment Records

TP-CAMP may retain transaction information concerning purchases made through OneSuite.

This may include:

• transaction identifiers;
• payment status;
• amounts;
• currency;
• purchase details;
• timestamps;
• refunds;
• reversals;
• disputes;
• payment-provider references; and
• related records.

TP-CAMP seeks to avoid unnecessarily retaining complete payment-card credentials where payment processing is handled by an external payment provider.

22. Refund and Chargeback Records

Records concerning refunds, reversals, disputes and chargebacks may be retained where reasonably necessary to:

• document the transaction;
• investigate fraud;
• respond to payment providers;
• resolve disputes;
• prevent repeated abuse; and
• satisfy accounting or legal requirements.

23. Contracts and Legal Documents

Contracts and other documents may be retained according to their business and legal significance.

TP-CAMP may preserve documents where reasonably necessary to:

• demonstrate an agreement;
• preserve execution history;
• address a dispute;
• establish rights or obligations;
• respond to legal proceedings; or
• maintain an appropriate business record.

24. Electronic Signature Records

Where electronic-signature functionality is available, information associated with an executed document may have evidentiary significance.

TP-CAMP may therefore preserve appropriate records concerning:

• document identity;
• signing events;
• signer information;
• timestamps;
• execution status; and
• related technical evidence.

Such records may be retained after ordinary account closure where reasonably necessary.

25. AI Interaction Data

OneSuite may retain certain information associated with AI-assisted functionality.

Depending on the feature, this may include:

• prompts;
• generated responses;
• contextual information;
• usage information;
• error information; and
• technical records.

Retention may occur for purposes such as:

• providing the feature;
• maintaining conversation context where applicable;
• troubleshooting;
• security;
• abuse prevention;
• service improvement; and
• resolving support issues.

AI-related information should not be retained longer than reasonably necessary for the applicable purpose, subject to legitimate exceptions.

26. AI Provider Retention

Where OneSuite uses an external AI provider, information transmitted to that provider may also be subject to the provider's applicable retention and processing practices.

TP-CAMP will not represent that an external provider immediately deletes information unless that behavior is supported by the applicable technical and contractual arrangement.

Further information is provided in the AI Usage & Transparency Policy and Privacy Policy.

27. CRM Records

TP-CAMP may maintain customer relationship information for purposes such as:

• onboarding;
• support;
• account administration;
• trials;
• customer communications;
• subscriptions;
• renewals; and
• service history.

CRM information may be retained while a customer relationship remains active and for an appropriate period afterward where reasonably necessary for legitimate business or legal purposes.

28. Marketing Information

Where a person has subscribed to optional marketing communications, TP-CAMP may retain appropriate contact and preference information until the person unsubscribes or the information is otherwise no longer needed.

TP-CAMP may retain limited suppression information after an unsubscribe where reasonably necessary to ensure that the person's preference continues to be respected.

29. Customer Support Records

Support requests and related communications may be retained for an appropriate period to:

• resolve ongoing issues;
• understand account history;
• investigate recurring technical problems;
• document customer instructions;
• train support processes where appropriate; and
• address disputes.

Highly sensitive information should not be included in support requests unless reasonably necessary.

30. Security Logs

Security information may be retained where reasonably necessary for:

• detecting unauthorized access;
• investigating incidents;
• identifying fraud;
• protecting customers;
• maintaining system integrity;
• enforcing OneSuite policies; and
• defending legal claims.

Security logs may be retained after account closure where legitimate security or legal reasons remain.

31. Authentication Records

Certain authentication records may be retained temporarily or for an appropriate security period.

These may include information relating to:

• login events;
• session activity;
• failed authentication;
• authorization;
• account changes; and
• suspicious access.

Short-lived authentication credentials may expire automatically according to their technical purpose.

32. Integration and Event Records

OneSuite may maintain records concerning application-to-application or third-party integrations.

These records may include:

• event identifiers;
• timestamps;
• processing status;
• revision information;
• delivery attempts;
• errors;
• duplicate detection information; and
• related technical metadata.

Such information may be retained where reasonably necessary for reliability, troubleshooting, audit and security.

33. Audit Records

Audit records may be retained longer than the active data to which they relate.

This may be necessary to establish:

• who performed an action;
• when an action occurred;
• what record was affected;
• whether a transaction was authorized;
• whether an ownership record changed; or
• whether suspicious activity occurred.

Deletion requests do not automatically require destruction of legitimate audit history.

34. Fraud Prevention Records

TP-CAMP may retain limited information concerning confirmed or reasonably suspected fraud, abuse or serious policy violations where necessary to protect:

• TP-CAMP;
• customers;
• payment systems;
• rights holders;
• service providers; or
• third parties.

Such information should be limited to what is reasonably necessary for the relevant purpose.

35. Legal Holds

TP-CAMP may temporarily suspend ordinary deletion where information is reasonably necessary for:

• pending litigation;
• anticipated legal proceedings;
• regulatory inquiries;
• law-enforcement requests;
• contractual disputes;
• copyright disputes;
• rights-ownership disputes;
• payment disputes; or
• another legally significant matter.

Information subject to a legitimate legal hold may be retained until the hold is no longer reasonably necessary.

36. Backups

OneSuite or its service providers may maintain backups for disaster recovery, resilience and system restoration.

When information is deleted from active systems, copies may remain temporarily within backups.

Backup information may be removed according to normal backup rotation rather than through immediate individual deletion.

Where technically practical, information restored from backup should remain subject to applicable deletion or restriction requirements.

37. Cached and Temporary Data

Temporary technical copies may exist in:

• caches;
• queues;
• session storage;
• temporary processing systems;
• logs; or
• integration infrastructure.

Such copies may expire or be removed automatically according to their technical lifecycle.

38. External Service Providers

Information processed through third-party services may be subject to the provider's own technical retention mechanisms.

TP-CAMP may request or configure deletion where appropriate and technically supported.

However, TP-CAMP cannot guarantee immediate deletion from a third-party system where the provider independently retains information under its lawful obligations or technical processes.

39. Data Submitted to External Organizations

OneSuite may help customers transmit information to external organizations such as:

• rights organizations;
• payment providers;
• CRM providers;
• email providers;
• AI providers; or
• other connected services.

Once information has been lawfully transmitted to an independent third party, deleting the corresponding information from OneSuite does not necessarily delete it from that third party.

The customer may need to contact that organization separately.

40. User-Initiated Record Deletion

Where OneSuite provides a delete function, users may delete records within the scope of their permissions.

Deletion may result in:

• immediate removal;
• soft deletion;
• archival;
• deactivation;
• anonymization; or
• scheduled permanent deletion,

depending on the record type and legitimate retention requirements.

41. Soft Deletion and Archiving

OneSuite may use soft deletion or archival where immediate permanent destruction would create unacceptable risks to:

• data integrity;
• audit history;
• cross-application synchronization;
• recovery;
• fraud prevention;
• financial records; or
• rights records.

Archived information may be removed from ordinary user interfaces while remaining restricted within underlying systems.

42. Anonymization

Where appropriate, TP-CAMP may anonymize information rather than delete an entire record.

Properly anonymized information that can no longer reasonably identify an individual may be retained for purposes such as:

• analytics;
• service improvement;
• reliability;
• security research; and
• statistical analysis.

43. Deletion Requests

Customers or individuals may submit appropriate deletion requests through official OneSuite support or privacy channels.

A request should provide enough information to identify:

• the requester;
• the relevant account;
• the relevant workspace where applicable; and
• the information or account the requester wants deleted.

TP-CAMP may request additional information where reasonably necessary.

44. Identity Verification

Before processing a sensitive deletion request, TP-CAMP may take reasonable steps to verify:

• identity;
• account ownership;
• workspace authority; and
• the scope of the request.

TP-CAMP may decline to act on a request where it cannot reasonably verify that the requester is authorized.

45. Deletion of Another Person's Data

A user may not ordinarily demand deletion of another person's independent account or legal records merely because both individuals appear in the same work, recording, contract or business record.

TP-CAMP may need to balance:

• the requester's privacy rights;
• another person's rights;
• contractual records;
• intellectual property records;
• financial obligations;
• legitimate business interests; and
• applicable law.

46. Contributor Information

Music records frequently identify multiple people.

For example, one musical work may identify several:

• writers;
• composers;
• publishers;
• performers;
• producers; or
• rights holders.

A request by one contributor to delete their account does not necessarily require TP-CAMP to erase their name from a legitimate rights record belonging to another authorized customer.

Where appropriate, TP-CAMP may instead restrict, correct or otherwise process the personal information in a manner consistent with applicable law.

47. Correction Instead of Deletion

Where information is inaccurate but legitimately required as part of a business, rights or legal record, correction may be more appropriate than deletion.

TP-CAMP may therefore offer or require correction where deleting the information would make the underlying record inaccurate or misleading.

48. Data Portability and Export

Where functionality permits, customers should consider exporting important records before requesting workspace deletion or closure.

Available exports may vary by application and record type.

Customers remain responsible for maintaining independent copies of information they are legally or operationally required to preserve.

49. Export Before Cancellation

Where a customer does not intend to renew OneSuite, the customer should review and export any information it reasonably requires before access expires.

TP-CAMP may provide a post-expiry period or limited access where available, but does not guarantee indefinite access after expiry.

50. Permanent Deletion

Where TP-CAMP determines that information:

• is no longer necessary;
• is not subject to a legitimate retention requirement;
• is not subject to a legal hold;
• is not required for security, accounting or fraud prevention; and
• can reasonably be deleted,

TP-CAMP may permanently delete or anonymize that information according to applicable technical processes.

Permanent deletion may not be reversible.

51. Deletion Cannot Always Be Reversed

Customers should carefully review deletion requests.

Once information has been permanently deleted and removed from applicable recovery systems, TP-CAMP may be unable to restore it.

TP-CAMP is not responsible for recreating information that a properly authorized user intentionally instructed OneSuite to permanently delete, except where required by law.

52. Scheduled Deletion

TP-CAMP may use scheduled deletion rather than immediate deletion.

This may provide time for:

• verification;
• fraud review;
• accidental-deletion recovery;
• processing across connected applications;
• legal review; or
• normal technical deletion workflows.

The length of such a period may depend on the record and circumstances.

53. Suspended Accounts

Suspension does not ordinarily cause immediate deletion.

Information associated with a suspended account may be preserved while TP-CAMP:

• investigates the reason for suspension;
• permits an appeal or corrective action;
• addresses security risks;
• resolves payment matters; or
• satisfies legal requirements.

54. Terminated Accounts

Where TP-CAMP terminates an account for serious misuse, TP-CAMP may retain appropriate information where necessary to:

• document the violation;
• prevent repeated abuse;
• respond to disputes;
• protect customers;
• preserve security evidence;
• comply with law; or
• enforce its agreements.

Termination does not create a right to require destruction of legitimate evidence of misconduct.

55. Fraudulent Deletion Requests

TP-CAMP may refuse, delay or investigate a deletion request where it reasonably suspects that the request is intended to:

• conceal fraud;
• destroy evidence;
• evade payment obligations;
• erase ownership history;
• interfere with a rights dispute;
• conceal unauthorized access;
• evade contractual obligations; or
• harm another person.

Any restriction will remain subject to applicable law.

56. Rights Disputes and Deletion

Where catalogue, ownership or split information is actively disputed, TP-CAMP may preserve relevant information until the dispute is reasonably resolved.

This may include:

• current records;
• historical versions;
• supporting documents;
• integration records;
• validation information; and
• audit history.

TP-CAMP's preservation of information does not mean TP-CAMP has decided which party legally owns the disputed rights.

57. Financial and Tax Requirements

Nothing in this Policy requires TP-CAMP to delete information that must be retained to comply with applicable:

• accounting;
• tax;
• financial;
• regulatory; or
• legal obligations.

Where only part of a record needs to be retained, TP-CAMP may restrict or minimize the information retained where reasonably practical.

58. Legal Claims

TP-CAMP may retain information reasonably necessary to establish, exercise or defend legal claims.

This may include records relevant to:

• contracts;
• payments;
• refunds;
• chargebacks;
• intellectual property;
• data protection;
• account access;
• security incidents; or
• other disputes.

59. Retention Periods

TP-CAMP may maintain an internal retention schedule establishing more specific periods for particular categories of information.

Such periods may change as:

• legal requirements change;
• service functionality evolves;
• infrastructure changes;
• security risks develop; or
• legitimate business requirements change.

This public Policy establishes the principles governing those decisions without requiring TP-CAMP to publish security-sensitive internal retention configurations.

60. No Indefinite Retention Without Purpose

TP-CAMP does not intend to retain identifiable Customer Data indefinitely merely because storage is technically possible.

Information should be:

• actively used;
• legitimately archived;
• subject to a valid retention requirement;
• anonymized; or
• deleted

according to its purpose and lifecycle.

61. Data Protection Rights

Individuals may have rights relating to their personal information under applicable law.

Depending on the circumstances, these may include rights to request:

• access;
• correction;
• deletion;
• restriction; or
• other legally available actions.

Such rights may be subject to lawful exceptions.

Further information is provided in the TP-CAMP OneSuite Privacy Policy.

62. Mandatory Retention Overrides

Where applicable law requires TP-CAMP to retain particular information, that requirement takes precedence over an ordinary deletion request for the applicable retention period.

TP-CAMP may also preserve information where another lawful exception to deletion applies.

63. Security During Retention

Information retained under this Policy remains subject to appropriate security controls according to its nature and the systems involved.

Archived or retained information should not become freely accessible merely because the associated account is inactive.

64. Access to Archived Information

Archived information may have more restricted access than active Customer Data.

TP-CAMP may limit access to archived information to appropriately authorized personnel or systems where reasonably necessary for:

• support;
• security;
• compliance;
• disputes;
• restoration; or
• legal requirements.

65. Customer Responsibility

Customers remain responsible for determining which business records they are independently required to preserve.

OneSuite should not be treated as the customer's sole legal archive unless TP-CAMP expressly agrees to provide such a service.

Customers should maintain appropriate independent copies of critical:

• contracts;
• rights records;
• accounting records;
• registrations;
• split sheets;
• financial records; and
• other important business information.

66. TP-CAMP's Business Records

Certain records may form part of TP-CAMP's own legitimate business records even after Customer Data is deleted.

Examples may include limited records establishing:

• that a transaction occurred;
• that an account existed;
• that a refund was processed;
• that a legal request was received;
• that consent or an instruction was provided;
• that an account was closed; or
• that a security incident occurred.

Such records should be limited to information reasonably necessary for the applicable purpose.

67. No Ownership Through Retention

TP-CAMP's retention of Customer Data or historical records does not transfer ownership of the customer's underlying:

• music;
• copyrights;
• masters;
• compositions;
• contracts;
• catalogues; or
• other intellectual property

to TP-CAMP.

68. Changes to Infrastructure

TP-CAMP may change infrastructure providers, databases, storage systems, backup systems or other technical services.

When information is migrated between systems, TP-CAMP may temporarily maintain multiple copies where reasonably necessary to complete and verify the migration.

Obsolete copies should be removed according to appropriate technical procedures after they are no longer reasonably required.

69. Business Transfer or Reorganization

If TP-CAMP or OneSuite undergoes a legitimate merger, acquisition, restructuring, financing, sale or transfer of relevant business assets, information may be transferred as part of that transaction subject to applicable law and appropriate confidentiality or data-protection requirements.

Such a transaction does not eliminate applicable privacy or retention obligations.

70. Service Discontinuation

If TP-CAMP permanently discontinues a material OneSuite service, TP-CAMP may provide affected customers with reasonable information concerning:

• service closure;
• available export options;
• relevant deadlines;
• account access; and
• intended treatment of Customer Data,

where appropriate and reasonably practicable.

Information that must lawfully or legitimately remain after service closure may continue to be retained according to this Policy.

71. Deletion Following Service Discontinuation

After an applicable service-closure period, TP-CAMP may delete or anonymize Customer Data that no longer needs to be retained.

Backups, financial records, security information, legal records and other information subject to legitimate retention requirements may remain for their applicable lifecycle.

72. Relationship to Other OneSuite Policies

This Data Retention & Deletion Policy forms part of TP-CAMP OneSuite's broader legal and operational framework.

It should be read together with the:

• Terms of Service;
• Privacy Policy;
• Refund Policy;
• Cancellation Policy;
• Cookie Policy;
• Acceptable Use Policy;
• Copyright & Intellectual Property Policy;
• AI Usage & Transparency Policy; and
• Security & Data Protection Policy.

73. Conflicts With Specific Agreements

A separate written agreement, statement of work, institutional agreement or other specific contract may establish additional retention requirements for a particular customer or service.

Where a specific agreement validly establishes different requirements for that service, the specific agreement will govern to the extent of the conflict, subject to mandatory law.

74. Changes to This Policy

TP-CAMP may update this Data Retention & Deletion Policy as:

• OneSuite functionality evolves;
• new applications are introduced;
• retention requirements change;
• service providers change;
• security practices evolve; or
• applicable legal requirements change.

The current version will display its effective or last-updated date.

Material changes may be communicated through the OneSuite website, application interface, email or another reasonable method.

75. Contact and Deletion Requests

Questions concerning retention or requests relating to deletion of OneSuite information should be submitted through the official TP-CAMP OneSuite privacy, support or account-management channel.

Requests should identify the relevant account or workspace and provide enough information for TP-CAMP to understand the request.

TP-CAMP may require reasonable identity or authority verification before processing a deletion request.

The current Data Retention & Deletion Policy will be available through the TP-CAMP OneSuite website.