Terms of Service, Privacy & Legal
Last updated 5 November 2026 · Version 2026-11-05-release-disclosures-1
This version reflects an implementation audit of privacy, providers, optional media, account closure and personal-data rights. Pricing and the approved billing cycle remain unchanged. Qualified legal review and operational checks remain outstanding, including privacy coverage, provider processing locations and the specific disposal gaps explained in R4. It is not a claim of verified legal compliance. The free single-project service is available in early access; paid plans are planned for later and live paid collection is not enabled.
Terms of Service
T1. Supplier, service and scope
NOM is supplied by Jonathan Edelstein, a sole trader operating NOM (NotesOfMeeting), ABN 63 322 083 928, Sydney, New South Wales, Australia (“NOM”, “we”, “us”). Contact: info@notesofmeeting.com. Legal notices may be sent to the contact email.
NOM supports preparation of agendas, meeting notes, issued records and project responsibilities. Features depend on the service’s stated availability and your project permissions. The public demonstration uses fictional information and does not save or send your project records. NOM’s free single-project service is available in early access. Paid plans are planned for later; paid collection is not enabled for this release. NOM is an online service.
T2. Agreement and authority
The person or organisation identified as the customer when an account is created is the customer under these terms. If you create or administer an account for an organisation, you must have authority to bind it. Invited users use their own verified accounts and must comply with the terms applicable to their use; accepting an invitation does not make them responsible for the host’s bill.
You must be given an opportunity to read these terms before accepting them. We record the accepted version and acceptance date. The Privacy Policy explains personal-information handling; acknowledging it is not consent to unrelated processing or a waiver of privacy rights. Any legally required specific consent is sought separately.
NOM is available only to individuals aged 18 or older, regardless of country or region. This is NOM’s eligibility policy; it is not a statement that the law universally prohibits minors from using online services. You must provide your date of birth during signup so NOM can calculate whether you have reached your 18th birthday. Parental authorisation and previous guardian or regional approvals do not provide an exception.
NOM validates calendar dates and calculates age on the server using UTC calendar dates. Registration may proceed from your 18th birthday; for a 29 February birth in a non-leap year, the threshold is reached on 1 March. Completing authentication, saving a payment method or returning from a sign-in provider does not by itself establish age eligibility. Existing users without a current age check must complete it before accessing the application. Account-security, account-closure and support routes remain available for appropriate requests.
If the supplied date establishes that you are under 18, you cannot complete NOM registration or use the application. NOM displays: “NOM is available only to individuals aged 18 or older. You do not meet the minimum age requirement and cannot create an account or use the service.” Age eligibility is based on the date you declare; it is not independent identity verification. No country or region can override this minimum age.
T3. Your records and account
You are responsible for the accuracy of the records you enter, the recipients you choose and the authority needed to use and share the information. You must have a lawful basis for providing another person’s information and give required notices or obtain consent where the law requires it. NOM retains its own legal responsibilities for handling that information.
Protect your sign-in details, authenticator and recovery codes. Do not share credentials. Report suspected misuse to info@notesofmeeting.com. Account recovery requires appropriate identity and authority checks; possession of a receipt alone may not establish ownership.
T4. Content and intellectual property
You and the relevant rights holders retain the rights you already have in content supplied to NOM. These terms do not transfer another contributor’s intellectual property to you or to NOM.
You grant NOM a non-exclusive licence to host, copy, process, transmit and display that content only as reasonably needed to supply, secure, maintain and support the service, carry out authorised sharing and instructions, and satisfy applicable legal obligations. Necessary service providers may process it for those purposes under appropriate restrictions. The licence continues after access ends only to the extent needed for lawful retention, required records and disposal under the retention policy. It does not permit advertising use or model training.
NOM and its licensors retain rights in the software, service design and materials they own or license. We permit you to access and use the enabled service for its intended purposes under these terms and your permissions. This does not transfer ownership of the service or restrict rights that cannot lawfully be restricted.
T5. Confidential information
NOM restricts access to customer content to authorised recipients, necessary service providers and personnel who reasonably need access for service delivery, support, security, recovery or legal obligations. We use reasonable safeguards and confidentiality arrangements appropriate to that access. We do not use private customer content for our advertising or model training. The Privacy Policy explains personal-information handling and lawful disclosures.
T6. Payments and records
The Payments and Monthly Billing schedule forms part of these terms. The account identifies the applicable billing period, charge rules, earned amounts and payment status. You are not enrolled in paid billing merely by receiving a project invitation. A free workspace does not require a payment method. Any paid billing requires the account holder’s express authorisation.
T7. Restrictions and ending the service
We may restrict access to the extent reasonably necessary to address a material breach, unauthorised access, security incident, unlawful activity or serious risk to people or the service. Where reasonably possible, we give reasons, an opportunity to address the issue and a way to request review. Urgent action may precede notice where needed for protection or where notice is legally restricted. Restrictions should be proportionate and reviewed when their basis ends.
Cancellation, account closure and data deletion have the different effects explained below. They do not remove mandatory remedies.
T8. Consumer rights
Nothing in these terms excludes, restricts or modifies a guarantee, right or remedy that cannot lawfully be excluded, restricted or modified, including under the Australian Consumer Law. Where its service guarantees apply, NOM must supply services with due care and skill and meet applicable fitness-for-purpose and reasonable-time guarantees.
If a covered service has a major failure, you may cancel the service contract and obtain a refund for the unused portion, or seek compensation for its reduction in value, as the law provides. You may also have rights to compensation for reasonably foreseeable loss or damage. For a remediable failure that is not major, NOM must remedy it within a reasonable time; further remedies may arise if it does not. The available remedy depends on the facts and applicable law. Contact NOM directly; you are not required to resolve a NOM service complaint solely with a payment or hosting provider.
T9. Availability and responsibility
We do not promise uninterrupted availability or recovery of permanently removed information. These statements do not excuse a failure to meet applicable consumer guarantees, reasonable security obligations or express contractual commitments. Issuing a NOM document preserves an application record; it does not certify the truth, legal validity or regulatory sufficiency of its contents. You should check records and keep appropriate copies for your own obligations.
T10. Changes and notices
We identify updated terms by version and effective date and explain material changes. We give advance notice through your account or contact email of materially adverse contractual or price changes, with a meaningful opportunity to cancel before they affect future charges. No change retrospectively creates charges for earlier use or removes accrued rights. Urgent changes required by law or security may need shorter notice, with an explanation where lawful.
A new privacy notice does not itself supply consent where separate consent is required. If you decline new contractual terms, we provide an appropriate route to cancel, request your information and exercise legal rights rather than requiring acceptance as a condition of making those requests.
T11. Complaints, law and disputes
Send support, billing, privacy and legal complaints to info@notesofmeeting.com, identifying the account and issue without sending passwords, security codes or full card details. We may reasonably verify identity and authority. We review the complaint and explain the outcome and available next steps.
These terms are governed by the laws of New South Wales, Australia. The parties submit to the non-exclusive jurisdiction of its courts and courts entitled to hear appeals from them, subject to any mandatory right to bring proceedings elsewhere. This clause does not remove applicable mandatory consumer or privacy protections. You may use available courts, tribunals and regulators without first completing a compulsory paid arbitration process. The ACCC does not resolve individual consumer disputes; NSW Fair Trading and relevant tribunals may offer appropriate avenues. Privacy complaints may be escalated to the OAIC where it has jurisdiction. Its guidance is available at https://www.oaic.gov.au/privacy/privacy-complaints.
Payments and Monthly Billing
B1. Start free. Scale simply.
Your first active project is free forever. Add more active projects for A$11.00 each per month plus applicable GST, with unlimited people. Free accounts can join shared projects as Viewers or Participants. Shared administration requires active paid accounts for both the project owner and administrator. Archived projects and view-only links are free. There is no trial deadline.
The monthly project fee is max(active projects − 1, 0) × A$11.00. One active project is free; two cost A$11.00, three A$22.00 and five A$44.00 per month. Invitations to another host’s workspace do not make you liable for that host’s charges. Project roles and permissions continue to apply.
B2. Activation and monthly renewal
Review the resulting monthly charge before confirming an additional active project or reactivating an archived project. Initial billing uses a secure hosted checkout page provided by our payment processor. Only backend verification of a successful first payment unlocks a second active project. A saved card, checkout redirect, failed, cancelled or pending payment does not unlock paid capacity.
The first payment covers the first month. Monthly renewal is anchored to that payment date. Later additions change the next renewal, without immediate charges or prorations. The account billing page shows the resulting project fee; final invoices record the tax actually assessed. The A$11.00 rate excludes applicable GST. Where 10% Australian GST applies, each additional project costs A$12.10 including GST. The subscription examples above exclude applicable GST. GST registration status is not changed by this pricing model.
B3. Archiving and reductions
Archived and completed projects do not count as active projects and are excluded from the next renewal. Their records and history are retained. Existing paid access continues through the current paid period. Archiving does not automatically refund the current month or create an account credit. Archiving an individual meeting does not deactivate its project.
Reactivation is subject to the displayed monthly project charge and payment-confirmed access. Removing or adding named people never changes the subscription fee. Named people remain subject to the host’s permissions and sharing controls.
B4. Cancellation, failed payments and deletion
Use Account → Your workspace billing → Cancel at period end to stop renewal. Already-paid access continues until the displayed period end. After expiry or a failed renewal, excess projects remain viewable but cannot be edited until paid access is confirmed; the first active project remains free. NOM grants no additional payment grace period. Records are not deleted as a consequence of a billing reduction.
Account deletion is separate from ordinary cancellation. Identity and authority must be verified and the associated provider subscription must be confirmed cancelled before identity deletion completes. Existing billing history is preserved subject to the retention policy. Closing the account does not prevent a billing dispute or statutory remedy.
B5. Existing subscriptions and payment records
Earlier subscriptions require account-specific reconciliation before migration. NOM must not create duplicate subscriptions or charge the same service twice. Historical invoices retain their original prices and descriptions. A payment-provider credit is not a cash refund. Existing valid credits remain provider records; this pricing change does not erase them or issue refunds.
B6. Refunds and credits
Deleting or archiving a project, removing a person, cancelling or deleting an account does not automatically refund valid charges already incurred or create an account credit. This is a change-of-mind position, not an exclusion of consumer rights or correction of billing errors. A refund returns money already paid; a credit reduces a future amount due. We do not substitute a credit for a refund where the law requires a refund.
The change-of-mind position does not remove an applicable statutory cooling-off or withdrawal right. Contact info@notesofmeeting.com to exercise a legally available right or report a billing error. Worldwide consumer-sales disclosures and any early-service-start request require qualified review before paid launch; these terms do not assert that a cancellation right has been waived.
Contact info@notesofmeeting.com with the account email and payment/invoice reference. Do not send full card or security details. Account closure does not prevent a legally available claim.
User access and sharing
U1. Project roles and invitations
An invitation applies only to its specified project. Receiving or accepting it does not create a payment obligation for the recipient. Anyone holding a valid invitation link can view the latest issued agenda and Notes of Meeting for non-archived meetings without signing in; the link does not expose drafts or the contact directory and does not itself grant project membership. Keep invitation links confidential. Accepting the assigned project role requires an explicit action by an account with the matching verified email and required authentication setup. Invitations expire after seven days, can be revoked and can be replaced by a new pending invitation. Adding a contact to All Contacts alone grants no project access. Adding an existing account to a project creates a pending invitation in Shared Projects. The matching verified account must accept before the selected role or project access is granted; recipients can decline and authorised project managers can revoke pending invitations.
Viewers read permitted records; Participants edit assigned content in unissued documents within their permissions; project Administrators manage the assigned project. The Meeting Coordinator manages their own project. These roles do not grant access to unrelated projects or the internal customer-administration portal. Issued locks and completed-project/archived-meeting restrictions apply.
U2. Viewer and calendar links
A private viewer link allows anyone who holds it to read its permitted content without an account. It does not create a project membership or grant access to unrelated projects. Viewer links expire after seven days or can be revoked. Treat them as confidential and check their scope before sharing.
A live calendar subscription shares the selected responsibilities, names, project/meeting information and dates with the calendar application and anyone who obtains the subscription URL or copied events. Protect that URL. Revoking access prevents future retrieval as implemented; it cannot erase information already downloaded, cached, exported or forwarded.
U3. Contributions and historical records
Your profile and contributions are visible to people whose project permissions allow access. Hosts can change or remove project access, but that does not automatically erase contributions from their records. Issued records preserve their historical identity information. Corrections and requests about personal information are handled under the Privacy Policy; preserving history does not override applicable correction or deletion duties.
Acceptable use and safety review
A1. Lawful use
Do not use NOM to commit or facilitate unlawful activity, abuse, exploitation, credible threats of serious harm, impersonation, unauthorised access or interference with the service. Lawfully recording, reporting or discussing a sensitive subject is not, by itself, prohibited conduct.
A2. Limited screening
When an online project is saved, NOM checks specified text for a limited set of explicit harm-intent phrases. A match can create a short excerpt for authorised human review. It can be a false positive or a quotation; it does not establish intent or illegality and does not itself automatically suspend an account or notify authorities. NOM is not an emergency-monitoring service.
A3. Preservation and disclosure
We may preserve or disclose relevant information where required or authorised by applicable law, including where a legally recognised serious-threat exception applies. We assess the circumstances and lawful basis and seek to limit disclosure to what is necessary. Recipients may include appropriate authorities or emergency services. We give notice where lawful and appropriate. A phrase match alone is not a sufficient finding of a serious threat. Review and disclosure decisions should be documented and restricted to authorised personnel.
Privacy Policy
Age eligibility
We request your date of birth to calculate whether you meet NOM’s minimum age of 18. It is processed transiently on the server and is not saved to NOM’s database, browser storage, application logs or a URL. We do not retain unsuccessful anonymous applicants’ birth dates. For an authenticated account, we retain only the eligibility outcome, policy version and check time, so NOM can enforce access consistently without retaining the birth date. Before signup completes, an expiring one-use receipt may record a successful age-check result; it does not contain the birth date.
The age requirement is the same in every region, so this check does not request your country, state or province. Do not submit identity documents or parental details for this purpose. A declared birth date is not independently verified proof of age. Contact info@notesofmeeting.com to request correction or exercise applicable information rights. Other account, project and billing records remain governed by their separate purposes and retention rules.
P1. Who handles information
The proprietor identified in T1 is responsible for NOM’s handling of personal information. Contact info@notesofmeeting.com. This policy covers visitors, customers, invited users and people whose information is supplied in project records. NOM operates as a sole-trader service; the proprietor monitors this inbox. Replies may not be immediate. This does not extend applicable statutory response deadlines.
For account administration, billing, security and its own operations, NOM determines why information is handled. For project information entered on an organisation’s instructions, that organisation may have separate controller responsibilities and NOM may act as its processor. The appropriate roles, data-processing terms and international-transfer arrangements require review for the customer and relevant jurisdiction; this policy alone is not a signed data-processing agreement.
P2. What is collected and how
NOM handles account identity and contact information; profile name, initials and company; project people, assignments and contributions; meeting content and uploaded images; project status and issue history; invitations, access permissions and sharing/calendar records; billing customer/invoice references and payment status; policy acceptance; service/security activity and the latest edge-supplied IP address; support communications and safety-review excerpts where generated.
Information comes from you, project hosts and other authorised users, authentication/payment providers and service operation. A host may provide information about a person before that person has an account. Authentication providers handle passwords and MFA secrets, and the payment provider handles full card details.
P3. Purposes and device storage
We handle information to deliver project features and authorised sharing, authenticate accounts, manage permissions, bill and reconcile payments, provide support, protect the service, assess limited safety flags, maintain necessary records and meet legal obligations. We do not sell or rent online customer content or use it for advertising, profiling, external commercial purposes or model training.
Where EU or UK data-protection law applies, relevant purposes may rely on performing a contract with you, legal obligations, or legitimate interests in secure operation, requested collaboration, support and proportionate record keeping, subject to the applicable balancing and objection requirements. A contract with a project host is not automatically a contractual lawful basis for information about every participant. Optional third-party video media uses a separate choice. Sensitive information or safety excerpts may need an additional legal condition; hosts and NOM must assess it rather than treating acceptance of these terms as consent.
Device-local project records, display preferences and saved feedback drafts use browser storage for the requested features. Signing out or closing your sign-in account does not erase those device copies. Saving or importing device records to an online account transmits the selected records to the service. Local records are not automatically included in service backups. Authentication/session cookies and a short-lived sign-up terms receipt support requested sign-in and security.
NOM has no application analytics, advertising pixel or session-replay integration in this release. The optional video introduction is blocked until you choose to allow the video provider identified in the consent notice. The player uses that provider’s privacy-enhanced embedding mode; this does not mean that the provider receives no data. Once loaded, the video provider receives connection and device information and viewing interactions, and may use device storage. Rejecting optional media leaves the rest of NOM available. Privacy choices in the website footer lets you allow or withdraw this choice; withdrawal removes the player and stops further player activity but cannot recall information already sent. NOM stores the media choice, version and date in this browser. The saved choice is treated as valid for up to 180 days; expiry of its validity does not itself remove the stored record. If browser storage is unavailable, the choice applies only on this page.
P4. Sharing, providers and locations
Project content and identity information are shared with recipients according to your permissions and sharing choices, including external calendar services when you subscribe or export. Personnel and necessary providers may access information for the purposes described here, subject to appropriate restrictions. Legal disclosures are addressed in A3.
Our authentication and account-security provider handles sign-in identity and contact details, authentication credentials, sessions and device or connection information, and delivers authentication-related email. The optional telemetry settings configured in NOM’s browser and backend integration are disabled; this does not disable authentication security processing or establish that all provider-side logging is disabled. NOM does not send meeting content to this provider as part of authentication. International processing, subprocessors, relevant contractual terms and deletion arrangements must be described accurately in the applicable provider disclosures; the actual locations and arrangements for NOM must be verified.
NOM’s managed hosting and publication platform uses infrastructure providers for server execution, database and file storage. Requests, IP addresses, request metadata, account and project content, and uploads pass through the relevant hosting services as needed to serve NOM. A hosting-infrastructure provider also operates the separate billing-recovery service; its job-state database is separate from project content. NOM does not send meeting records to an AI model in this application. Exact contracting arrangements, storage and support countries, provider-log retention, backups and transfer safeguards have not all been verified; do not assume Australian-only storage.
Our payment provider receives customer contact details, billing address and payment information entered in its hosted checkout, together with account, subscription and invoice references needed for payment processing, fraud prevention and reconciliation. NOM receives references, status and invoice amounts; it does not receive full card details. NOM does not send meeting notes or project people lists to the payment provider for billing. The provider’s published privacy information describes international processing and continued financial, tax, regulatory and fraud-prevention retention. NOM’s actual recipient countries and applicable arrangements must be stated accurately in the relevant disclosures. NOM does not promise immediate erasure of the provider’s legally retained records.
Through NOM’s optional-video integration, the video provider receives connection, device and viewing information when you allow that media to load. Your chosen calendar application and recipients receive the feed contents or files you choose to share. Email sent to info@notesofmeeting.com is handled through our email-delivery and mailbox-storage provider and read by NOM’s proprietor. The provider handles sender and recipient details, message contents, attachments and associated email metadata to deliver, store and protect that correspondence. NOM’s mailbox storage locations, retention settings, deleted-item recovery, legal holds and applicable transfer arrangements remain to be verified; using a hosted email service alone does not establish Australian-only processing. Project invitations are prepared for the host to send. NOM also sends administrative account notices through its dedicated Microsoft email service. That service processes the recipient address, account-action notice, administrator-supplied reason and delivery metadata. Submission to the email service is not confirmation of receipt or inbox placement. Issued-document notifications appear inside NOM. NOM has no marketing-email integration. Authentication-related email is handled through our authentication provider. Provider subprocessors may be involved under their own applicable arrangements.
Not all processing is necessarily in Australia. Provider statements about standard contractual clauses or other transfer mechanisms do not by themselves verify NOM’s own compliance. Where cross-border requirements apply, NOM must assess and implement the required arrangements. Your acknowledgement of this policy is not blanket consent to waive them. Contact NOM for available provider/location information; unresolved details remain launch-review items.
P5. Retention and disposal
Account closure, removal from a screen, expiry of access and storage deletion are different events. R4 explains category-specific purposes, legal requirements, disposal criteria and verified implementation gaps. The administration screen stops showing the last recorded IP after 30 days; that display rule does not erase the stored IP. A separate disposal process can clear the stored IP and observation date once the last observation is at least 30 days old, subject to preservation holds and successful processing. At the 28 October 2026 review, that production process was not enabled. NOM therefore does not claim a verified 30-day storage-deletion deadline. Personal information must not be retained indefinitely merely because expiry has not been implemented.
P6. Security and incidents
We use reasonable technical and organisational safeguards appropriate to the information and service. Authorised application support access is restricted and recorded. No internet service can guarantee perfect security. That does not remove our legal responsibilities. Report suspected security incidents to info@notesofmeeting.com without sending credentials. We assess incidents and notify affected people and regulators where required by applicable law.
P7. External copies and services
You control downloaded files and information you share outside NOM. External recipients and calendar/media/payment services may also handle information under their own terms and privacy notices. NOM cannot recall external copies through link revocation or account deletion. This does not remove responsibility for disclosures NOM itself makes or for its service providers where the law assigns it responsibility.
P8. Access, correction and deletion requests
Contact info@notesofmeeting.com to request access, correction or erasure of personal information, including information supplied by a project host. Requests are assessed separately from cancellation and do not require acceptance of updated terms. We may reasonably verify identity and authority without asking for unnecessary identity documents. Where applicable, rights also include restriction, objection, portability and withdrawal of consent. Withdrawing optional-media consent does not affect the lawfulness of earlier processing.
Where EU or UK data-protection law applies, NOM must respond without undue delay and normally within one month, subject to lawful identity-verification rules and any permitted extension notified with reasons within the required time. A solo-operator support queue or a paid billing period does not extend a statutory deadline. Valid erasure requests are assessed without waiting for period end; only information justified by a specific applicable exception or necessary legal obligation may be retained.
Closing the sign-in account is not full personal-data erasure. Project records, contributions, billing history and necessary audit records require a separate assessment, including other people’s rights and any lawful retention. If a request is limited or refused, NOM explains the basis and applicable complaint route. You may complain to the OAIC, ICO, relevant EEA supervisory authority or other regulator where it has jurisdiction. There is no unconditional promise to erase every historical record, but preserving history is not itself a legal exemption.
Optional information need not be provided. Without required account/authentication or billing information, the relevant features may be unavailable. Hosts must assess lawful collection and any consent requirements before supplying sensitive information.
P9. Privacy complaints and changes
Contact NOM first so we can investigate and respond. Where applicable, you can also complain to the OAIC or another regulator with jurisdiction. We publish material policy changes with an updated date and explanation; legally required consent is obtained separately.
Data Access, Retention and Deletion
R1. Active, completed and deleted projects
Active records remain available while the relevant service, account and permissions remain available. Completed projects are read-only until restored or deleted, subject to entitlement and permissions. NOM uses Mark project complete to make a project inactive for billing; there is no separate project archive control. Individual meeting archival is distinct.
Deleting a project removes normal access and revokes the relevant participation/sharing access. Recovery controls, where available, depend on owner authority, retained project content, the current eligibility deadline and account limits. No recovery period or successful recovery is guaranteed. Recovery does not reactivate old invitations automatically. A free account with an occupied active-project place must manage that place or obtain authorised paid capacity before restoration. The billing consequences are in B3.
R2. Recovery and exports
Users are responsible for keeping their own local copies of project information. NOM should not be relied upon as a backup service or as a means of recovering deleted information. A displayed deleted-project recovery deadline is a current eligibility limit, not a promise of recovery until that date. After that limit, customer recovery is unavailable and the content is eligible for purge. Purge code can remove project content, the uploaded project image and related records when an eligible owner-access, administrator or authorised job path runs; those paths do not remove every residual record. A fixed physical-disposal deadline and unattended cleanup for closed owners have not been verified. Closing a sign-in account does not itself mark its projects deleted or start a deleted-project recovery eligibility period. The absence or expiry of customer recovery does not mean operational backups do not exist or that legally required retention has ended.
Permitted PDF/CSV exports are readable copies, not restorable project backups. Online JSON project copies can be downloaded by that project’s Administrator or Meeting Coordinator where access permits; device-local copies use the local backup controls. Downloaded files do not update automatically and must be stored securely. Importing a compatible JSON copy creates a project subject to account limits and applicable billing. Operational backups are separate from these customer downloads and do not guarantee customer recovery or historical rollback. Their retention and any legally required preservation remain subject to R4.
R3. Account closure and other people’s records
Account → Account Settings provides sign-in account closure; /account/delete is also available without accepting updated terms. NOM verifies identity, confirms immediate cancellation of the associated supported subscription and expires an unfinished hosted checkout session before deleting the sign-in identity through the authentication provider. This differs from ordinary Cancel at period end, which preserves already-paid access until the displayed period end. If provider cancellation, access revocation or identity deletion cannot be confirmed, closure remains incomplete and retryable; contact info@notesofmeeting.com. No guaranteed technical completion time is asserted.
Confirmed closure revokes NOM sessions, the closing identity’s memberships and viewer/calendar links, and unaccepted invitations to projects it owns. It does not erase project content, contributions, profile/customer records or billing/tax/audit history, and does not revoke other collaborators’ independent access. Device-local records and external copies also remain. For a separate personal-data erasure assessment, contact info@notesofmeeting.com before or after closure. NOM must assess what can be erased, restricted or retained, the lawful reason and relevant timing; the billing cycle does not postpone a valid legal erasure request.
Account closure does not issue an automatic refund or credit or prevent a billing dispute, statutory withdrawal right or other mandatory remedy. Contributions to another host’s records are assessed individually; neither host ownership nor issued-record history overrides applicable privacy rights. Link revocation cannot erase downloaded, cached or forwarded copies.
R4. Residual records and retention review
Reviewed 28 October 2026 for NOM’s NSW, Australian sole-trader operation. Closure does not create a general right to retain everything. NOM must retain records required by applicable law or a court/tribunal order, and may otherwise retain only information necessary for a lawful, identified purpose. Where the Australian Privacy Principles apply, APP 11.2 requires reasonable steps to destroy or de-identify information no longer needed for a permitted purpose, unless an exception applies. NOM’s Privacy Act coverage requires qualified review; sole-trader status alone does not determine it. The following describes requirements and current limits, not a guarantee that automated disposal is operating.
Billing and tax records — Keep invoices, payments, refunds/adjustments and the limited supporting calculation and customer references needed to explain the transactions. Income-tax records generally must be retained for five years after preparation or obtaining the record, or completion of the related transaction or act, whichever is later, with statutory exceptions/extensions. GST transaction records must be retained for the longest applicable period: five years after completion, the relevant assessment review period, or a refreshed review period following amendment. These periods do not automatically start at account closure. Necessary dispute evidence or a specific legal order may justify longer retention. Meeting content and an entire People list are not automatically tax records. NOM has no verified automatic expiry for its billing/usage history; once the applicable duty and any separate justified need end, unnecessary information must be securely destroyed or effectively de-identified. The proprietor and tax adviser must determine the record-specific end date.
Security and audit records — Limited records may be necessary to detect misuse, investigate incidents, verify authorised support access and address a specific complaint or claim. No general fixed statutory retention period has been identified for NOM’s ordinary security events, session records or support audit. Their period must be justified by the actual risk or case, reviewed and ended when no longer necessary; possible future usefulness is not indefinite authority. Protected audit history currently has no routine expiry/disposal workflow. Account closure revokes relevant sessions but does not delete their rows. Keyed identifiers used in logs remain potentially linkable personal information, not guaranteed anonymous data. Controlled disposal must preserve records subject to a valid hold and avoid weakening audit protections.
Policy acceptance — The account identifier, accepted version and timestamps help establish the agreed terms and deal with a relevant complaint or claim. No special law requires every acceptance record to be kept forever or for a universal number of years. NSW simple-contract claims commonly have a six-year limitation period running from accrual of the claim, subject to exceptions; that is a litigation consideration, not a six-year retention duty for every record and not a clock automatically starting at closure. Retain only necessary evidence for a documented claim-related period, then destroy or de-identify it. Account-linked acceptances currently have no automated expiry. Pending sign-up receipts expire for use after one hour; a subsequent successful sign-up-receipt request removes expired rows, but no independent timed cleanup has been verified.
Deletion identifiers and access-revocation metadata — Limited project/account identifiers and deletion or closure dates may be needed to prevent old device copies, retries or restores from reactivating removed records, and to demonstrate the disposal action. There is no identified general statutory minimum for these markers. Keep only what remains necessary for those purposes or a specific claim/hold, with a documented review/end criterion. Current project purge paths can leave identifiers, dates and some membership/link metadata, and no finite disposal rule has been verified for all such residuals. Identifiers and hashes are not automatically anonymous. A future disposal process must prevent unintended resurrection without preserving unnecessary names, contact details or content.
Resolved safety excerpts — A short excerpt may be needed while a genuine safety concern, lawful disclosure, investigation or related claim is assessed. No general fixed retention duty for all flagged meeting text has been identified. Review or dismissal does not currently erase the excerpt; it can remain until an applicable project purge runs. Once a concern is resolved or found to be a false positive, continued retention requires a specific remaining lawful need; otherwise the unnecessary excerpt must be destroyed or effectively de-identified. The current system has no separate resolved-excerpt expiry. Any proposed period, sensitive-information condition or preservation hold needs qualified legal and operational review rather than keeping the excerpt simply because a flag once existed.
Account and project records — Billing reconciliation, an unresolved rights/support request, authorised collaboration or a specific claim may justify a limited subset after closure. There is no established rule requiring NOM to retain the complete profile, contact record or every project after the sign-in identity is deleted. Necessary financial evidence follows the tax rule above; other information requires its own purpose and end criterion. NOM does not yet have a complete closed-account erasure workflow or verified maximum storage period. Disposal must identify and remove unnecessary profile/contact and project data, protect other people’s rights and lawful records, and separately address provider copies. Contributions to another host’s records are assessed individually. Browser storage, downloads and external recipients’ copies are not erased by closing the online account.
Provider-held copies and backups — NOM must address copies it controls through its hosting, authentication, payment and support providers, including backups, when their lawful purpose ends; a provider’s independent legal obligations may require a different outcome. Deleting an individual sign-in identity and terminating NOM’s agreement with its authentication provider are different processes. A provider-agreement termination provision does not by itself establish a deletion deadline for every copy associated with an individual account. Our payment provider may retain payment-related information for its own financial, regulatory and fraud-prevention duties; closure of a NOM account does not itself erase those provider records. Hosting snapshots, encrypted owner and service backups, and email-provider correspondence and recoverable items need separate inventory, necessity review and verified deletion or expiry. Service-backup code contains an expiry process, but actual production operation, provider snapshot settings and owner-backup/mailbox disposal periods have not been verified. No single provider-wide erasure deadline is promised. Provider deletion instructions and results must be checked; link revocation, encryption and an expired restore window are not proof that every copy was destroyed.
Disposal and holds — Once a required period and any separately documented lawful need have ended, take reasonable steps to securely destroy the information or effectively de-identify it across controlled stores and copies. If immediate destruction is genuinely technically impossible, restrictive isolation pending disposal must meet applicable legal requirements; an accessible backup is not automatically beyond use. A legal hold must identify its authority or lawful purpose, the relevant records, responsible person, review date and release criterion. Required holds must not be silently removed by a timer; they must also not become unreviewed blanket retention. Restores must reapply valid deletion decisions and lawful holds before ordinary access. Automated expiry, closed-owner disposal, resolved-excerpt disposal and verified provider/restore handling remain implementation gaps. Contact info@notesofmeeting.com for an individual assessment; these gaps do not authorise indefinite retention.
Retention references, checked 28 October 2026: Income Tax Assessment Act 1936, s 262A; Taxation Administration Act 1953, Schedule 1 s 382-5; OAIC retention and disposal guidance; NSW Judicial Commission limitations guidance. Application depends on the records and circumstances; qualified advice is required for the unresolved matters identified above.
Contact and complaints
For support, privacy enquiries, access, correction or deletion requests, billing disputes, complaints and legal notices, email info@notesofmeeting.com. Describe the account and issue without sending passwords, MFA codes or full card details. We may verify identity and authority before disclosing or changing information.
NOM is operated by one person as the sole-trader service identified in T1. The proprietor monitors info@notesofmeeting.com for legal, privacy, billing and support requests. Replies may not be immediate. This does not extend statutory time limits or limit mandatory rights. No business postal/service address has yet been approved for publication; required geographical/contact disclosures must be resolved before relevant worldwide sales launch.