1. Who is responsible and what this Policy covers
NOTA SOCIAL NETWORK PTY LTD, trading as NO'TA (“NO'TA”, “we”, “us”, “our”), is responsible for the personal information described here. We are an Australian company based in Sydney, New South Wales, ABN 24 693 312 926, ACN 693 312 926. We act as the controller where that term applies. Contact our privacy contact at privacy@no-ta.app; legal contact: legal@no-ta.app.
This Policy covers our apps, websites, public pages, waitlists, invitations, support, age checks, moderation, app extensions and widgets. “Personal information” includes information about an identified or reasonably identifiable person, including personal data under applicable law. Features and processing vary with availability, settings and region. A description of an optional or future feature does not mean it runs for every account.
This Policy explains processing; it is not a request for blanket consent. Optional permissions and consent requests are presented separately. A feature notice may add specific information but cannot silently remove your rights or authorise an incompatible new purpose. Independent external services have their own notices; our responsibility for providers processing on our behalf remains.
2. Information, sources and reasons for collection
We collect information from you and your device, from your use of the Services, and from other users, authorised reviewers and providers. We use the following categories only as relevant to the features you use and the purposes described below.
- Accounts and authentication: email, username, internal identifiers, required date-of-birth information, invitation and waitlist records, authentication/session information, passkey and two-factor metadata, and Apple or Google sign-in data. Supabase Auth processes login credentials. A phone number is not required for standard registration. Required details enable an account, access checks and recovery; refusing them can prevent the relevant service.
- Profile and preferences: names you provide, avatar or preset selection, banner, biography, website, language, optional residence/nationality, education, occupation, language proficiency, privacy and real-name settings, and business or platform roles. Fields are optional unless marked as required; choosing a username does not require publishing your legal name.
- Content and communications: posts, replies, polls and votes, answers, quotations, messages and context, photos and videos, drafts, recipes and ingredients, place submissions and reviews, offers, reflections, journals, journeys, Path Notes, Library notes and saved links, support conversations and attachments. Visibility follows the relevant feature and your choices.
- Relationships and participation: follows, blocks, mutes, saves, memberships, reactions, views, searches, sharing, notification preferences and history, and engagement signals used for product metrics and Resonance. Other users’ interactions can create information about you.
- Safety and review: reports, reported content and evidence snapshots, warnings, restrictions, appeals, case outcomes, reviewer consent and assignments where available, operator notes and audit records. Reports and authorised review activity are sources of this information.
- Location and device information: IP address, user-agent, device/app identifiers, platform and version, approximate location from requests, login events, push tokens, delivery records, crash diagnostics, upload metadata, security and abuse signals. Precise location is collected when you permit and use a location feature; place searches, coordinates and optional location/weather attached to content are processed to fulfil those requests.
- Local storage: language/theme choices, cached content, local search history, offline drafts and queues, share-extension session/context data, and limited widget context such as username, topic labels or pending actions. Some stays on the device until a requested action or synchronisation sends it to us.
- Optional AI and commercial records: Monthly Insight consent, eligible source excerpts, counts, generated summaries and operational records when you opt in; business/offer interactions and relevant sponsor disclosures where those features exist. Third-party mobile ads are disabled for the first store release; later advertising processing requires the notices and controls described in section 6.
Information you or another user submits can reveal sensitive matters such as health, religion, political views, ethnicity or sexuality. Do not post unnecessary sensitive information or another person’s confidential data. Publishing something is not unlimited consent to reuse it, and we apply any additional legal conditions required for sensitive information. Age-check data is addressed separately below.
Age assurance and Didit
We may require a proportionate age check because of applicable law, a country policy, an age band or a suspected-minor review. The server determines whether a check is required; editable nationality or residence profile fields do not determine the outcome alone.
The standard flow uses Didit. We send an account reference, workflow, language and necessary technical information. Depending on the method, Didit may collect an ID image and extracted details including birth information, a selfie or liveness capture, biometric-derived information, network/device data, fraud indicators and human-review information. Read the notice presented before collection and Didit’s verification privacy notice.
We use the outcome to establish minimum-age eligibility, administer a review or correction, prevent circumvention and meet applicable duties. Age-assurance information is not used for advertising, feed recommendations, Resonance or unrelated profiling. The result is not displayed publicly. Acknowledging a compulsory check is not, by itself, freely given consent to biometric processing; any required consent or other additional legal condition must be addressed for the selected method.
Our integration retains limited status, threshold outcome, review information and timestamps. It scrubs detailed decision payloads and does not intentionally retain document images, extracted document details or biometric scores in NO'TA’s verification records. On a terminal outcome it requests deletion of the Didit session, records failures for retry and replaces the raw session reference with a one-way hash after confirmed deletion. A deletion request is not a guarantee that every vendor copy has already been erased. A hash linked to your account remains personal information.
Didit’s processing and deletion can depend on the configured method and its contractual and legal duties. Any separately retained biometric template requires its own disclosed purpose, lawful basis and retention limit; this Policy does not authorise such retention. Age-assurance records, including incomplete sessions and minimal results, remain subject to the purpose and destruction limits in section 10. General audit or business interests do not override stricter age-assurance law.
You may request a non-government-ID review in the app or through support, correct inaccurate information and challenge an outcome. Access can remain limited while eligibility is assessed. Where Australian social-media minimum-age rules apply, a reasonable alternative to government ID or an accredited government digital ID must be available. We may request a proportionate alternative age signal. Didit acts for us for the configured check; any processing it conducts independently must be explained in its own notice and have a valid basis.
3. Purposes and automated processing
We use the relevant information to authenticate and administer accounts; deliver the content and features you request; manage visibility and interactions; operate search, feeds, maps and notifications; respond to support and rights requests; measure use and diagnose faults; prevent abuse; assess eligibility; moderate content; and meet legal obligations or handle legal claims.
Automated systems can affect you. Content text and images, reports and prior outcomes may trigger keyword or AI-assisted moderation. Device, IP, age and activity signals may trigger rate limits or access restrictions. Participation, feedback, blocks, reports and moderation signals contribute to Resonance and may affect ranking or feature eligibility. These are estimates and rule-based assessments, not findings of truth, expertise or personal worth. A result can be wrong.
You can challenge a material outcome through an available in-app review route or support@no-ta.app, and request privacy-related information or human intervention where applicable law provides that right. Human review may occur; we do not claim that every automated action is reviewed before it takes effect. The Community Guidelines explain enforcement.
Optional Monthly Insight
When you opt in, Monthly Insight may use excerpts from your own posts, replies and public-context messages for a completed calendar month, compare the previous month, and use aggregate counts and limited context such as a parent title or topic. Other participants’ reply and message bodies, including body excerpts used as reply context, are excluded from this feature’s provider payload. Your own writing can still contain information about other people.
Selected material is sent to OpenAI for summary generation and safety checks. Responses application-state storage is disabled for these requests. Separate provider abuse-monitoring retention may apply, ordinarily up to 30 days unless an approved alternative control or legal requirement applies. Our summary tables do not intentionally store raw prompts or source excerpts; they hold generated summaries, counts, status, model/prompt versions, consent and deletion/audit records.
The summary is private, does not change Resonance, and is not used by itself for moderation, access or enforcement decisions. Authorised administrators may run a reason-recorded preview for an opted-in account and receive the generated summary and counts. Opt out to stop future generation; deleting a visible summary does not necessarily immediately erase every lawful audit or backup record. Optional AI consent is separate from safety moderation, which can run without Monthly Insight being enabled.
4. Who can see what you share
Public posts, replies, reviews and other public activity can be visible to users, visitors and search engines through relevant surfaces. Content may be copied, quoted, translated or shared elsewhere. Private-profile settings do not make every contribution private. If you enable real-name display, your name may appear on relevant public surfaces; a private profile uses the username on relevant public surfaces and limits certain following and messaging functions.
A public profile can expose derived age in whole years and an adult-status field. This is distinct from the exact date-of-birth record and the private Didit verification outcome. Making a profile private does not automatically remove every public profile field.
Conversations are attached to public content. They are not confidential, end-to-end encrypted private DMs. Their visibility depends on the feature, participants and access rules; authorised support and safety personnel may access relevant records. Avoid confidential disclosures.
Reflections and journeys are private by default unless you choose a public setting. Private journals, Library notes and private content are not intended for public display, but authorised personnel may access relevant data where necessary for support, security, law or operation of the feature. Private does not mean inaccessible to the service operator.
Notifications and operating-system extensions or widgets can expose limited content or account context on your device. Manage previews and permissions. Blocking or changing settings cannot recall screenshots, quotations or external caches already created. Deleting an account is subject to section 10, including the possibility that retained content itself identifies you.
6. Advertising, diagnostics and communications
The first store release does not display third-party mobile advertising. Google Mobile Ads/AdMob and its advertising-consent and tracking-permission integrations have been removed from the intended new release. Firebase Analytics and Crashlytics remain for usage measurement and crash diagnostics. The iOS app uses the Core-only Analytics variant, without Firebase’s IDFA collection capability. The Android app retains Firebase’s standard Analytics integration. These services can collect app-instance or other device-related identifiers, usage events and diagnostic data; removing advertising integrations does not turn them off. Any future advertising rollout requires updated information about the actual data, recipients and purposes, and the consent or opt-out controls required by law. We do not sell personal information to data brokers for money. We do not treat that statement as an exemption from laws defining non-monetary “sale”, “sharing” or targeted advertising.
Crash diagnostics and internal usage metrics help us investigate failures and understand product use. Some telemetry can identify an account or device; it is not all anonymous. Current mobile startup enables Firebase Crashlytics in supported builds. Device-level advertising choices do not automatically turn off all operational diagnostics or internal metrics. Where consent is legally required for non-essential processing, it must be obtained before that processing.
Our public website uses Cloudflare Web Analytics, where enabled, to understand visits and page performance. The service sends technical measurements, such as the page visited, referring page and loading or interaction timings, to Cloudflare. It does not use cookies or browser storage for analytics, fingerprint visitors or track individuals across websites. Cloudflare receives the source IP address when handling the request and states that its analytics service discards it at the nearest data centre without storing it in its core databases or logs. These website measurements are separate from mobile diagnostics and information you submit through forms.
Push notifications require the relevant device permission and use available in-app preferences. Necessary security, recovery and legal messages are distinct from marketing. You may unsubscribe from promotional or waitlist communications using an available link or by contacting support. An opt-out does not stop messages necessary for an active account or a request you made.
7. Cookies and device storage
Authentication, settings, security, caching and offline features use cookies, browser storage, app preferences and secure storage as appropriate. Marketing pages store language preferences locally; Cloudflare Web Analytics does not use that storage. Web sign-in stores session information. Mobile apps retain caches, local search history and pending content; iOS share extensions use an app group for session hand-off, while widgets use limited context and pending actions.
Our policy pages request an Arabic font from Google Fonts, which exposes network request information such as IP address and browser details to Google. A stored language preference is distinct from advertising tracking. Essential security services can also receive request information without an advertising cookie.
You can clear storage or revoke permissions through device/browser settings and available in-app controls. This can sign you out, remove unsynchronised drafts or disable features. Uninstalling does not delete server-side information, and operating-system backups may follow separate settings.
We do not uniformly respond to the legacy “Do Not Track” signal. A legally applicable opt-out preference signal, including Global Privacy Control, must be honoured for covered processing; technical limitations are not a waiver of that obligation. Contact privacy if you cannot use an applicable control. Any future covered advertising processing must support the required controls before activation.
8. Legal grounds and sensitive information
Where law requires a legal basis, we assess each purpose separately:
- Providing a contractually requested service: necessary account administration, authentication and delivery of the content or feature you request. A feature being described in the Terms does not make all processing contractually necessary.
- Legitimate interests, where permitted: proportionate security, abuse prevention, moderation, product reliability, participation metrics and legal claims, balanced against your rights and reasonable expectations. You may object where applicable law permits.
- Legal obligations: applicable age and online-safety duties, valid legal process, required records and regulatory responses.
- Consent: optional Monthly Insight and processing for which law requires consent, such as particular sensitive-data uses or non-essential tracking. Device permissions are technical controls and do not automatically establish every legal basis. Withdrawal stops future consent-based processing without making earlier lawful processing unlawful.
- Protection of vital interests or other public-interest grounds: only in circumstances and to the extent the applicable law permits, for example a serious threat to life.
Sensitive or special-category information, including biometric information where protected as such, may require an additional condition such as explicit consent or a specific statutory ground. A general legitimate-interest claim or public post is not a universal substitute. Declining an optional use does not by itself remove access to unrelated core features; declining information necessary for a specific lawful service may prevent that service.
9. International processing
Our operator is in Australia, and our primary hosted database is configured in Singapore. Global infrastructure and specialist providers may process information in other countries, including the United States and European countries, depending on the service, processing location and authorised subprocessors. Public content can be accessed worldwide. Support access and backups may involve locations different from the primary database.
Where required, we use an applicable transfer mechanism, such as an adequacy decision or appropriate contractual safeguards, and assess required supplementary protections. Australian overseas-disclosure responsibilities and applicable local restrictions remain relevant; accepting this Policy does not waive them. Contact privacy@no-ta.app for the applicable recipient-country information or safeguards, subject to justified protection of confidential terms. A provider’s general global footprint does not mean your data is processed in every country it lists.
10. Retention and deletion
We retain personal information only for as long as needed for its stated purpose and lawful obligations. Relevant criteria include whether an account or request remains active, the nature and sensitivity of the information, recovery needs, a specific dispute or safety issue, and statutory requirements. Removal from an active screen, deletion from active storage and expiry of backups are different events.
- Account deletion: the standard flow provides 30 days for recovery. The profile is hidden and retained shared contributions show “User not available” during this period. Recovery restores current public identity information. Permanent purge removes the original authentication account, profile identity and private/account-only state, subject to specifically justified lawful retention. A shorter legal deadline or immediate removal obligation takes precedence.
- Shared contributions: otherwise-visible posts, replies, directory contributions, Path Notes and recipient-visible conversation history may remain after account deletion to preserve shared discussions and records. The username/name, avatar and profile link are detached, but the text or media may still identify you. This is not a claim of full anonymisation. You may remove available content before deletion or request specific removal under applicable law. Third-party copies may remain outside our control.
- Private content: private reflections, journals, journeys and account-only records are retained for their feature or until deletion, subject to limited backup and lawful retention needs. Individual-content deletion does not necessarily remove material already quoted by someone else.
- Support, invitations and waitlists: retained for the relevant request or relationship and justified follow-up or legal needs, then deleted or de-identified when no longer needed. You may ask to leave the waitlist or stop promotional contact.
- Security, moderation and audit records: retained to investigate a specific issue, prevent relevant abuse, handle appeals or claims, or meet an identified obligation. Evidence snapshots may survive removal of the original content. General usefulness is not a reason for indefinite retention.
- Age assurance: the integration requests deletion of terminal Didit sessions and retries recorded failures. Minimal status, result, review and hashed-reference records also require a purpose and retention limit. Incomplete or abandoned sessions are not exempt. Where Australian minimum-age destruction rules apply, information collected for that purpose must be destroyed when its permitted purposes are complete; a general safety or audit clause cannot extend that period. Vendor-specific copies or separate records remain subject to their applicable deletion obligations.
- Monthly Insight: summaries and related consent, status, version and audit records are held for the configured feature-retention period and justified legal needs. Opting out stops future generation. Deleting a visible summary hides it from your Growth view; lawful backend, backup or audit records may remain. Provider retention is described in section 3. We do not represent a configurable duration as a universal fixed period.
- Media, logs and backups: deletion can take additional time to propagate through delivery caches and backup cycles. Restricted copies may remain where necessary for recovery, a legal hold or another lawful purpose and must not be reused for unrelated purposes. Contact privacy for information about a particular record or deletion request.
To delete an account, use Settings > Account > Delete Account, or contact support or privacy if access is unavailable. See the account-deletion notice. Uninstalling alone is not a deletion request. If we cannot fully honour a request, we will explain the lawful reason and applicable review options rather than treating the standard recovery period or retained contributions as a blanket exception.
11. Choices, rights and requests
Available controls include profile and real-name visibility, reflection/journey privacy, notification preferences, device permissions, Monthly Insight opt-in/opt-out and visible-summary deletion. The in-app Export My Data feature provides available account records; it is not necessarily a complete response to every statutory access request. You may request additional information from us.
Depending on applicable law, you may have rights to access, correction, erasure, restriction, portability, objection, withdrawal of consent, an authorised agent, or review of certain automated decisions. Applicable advertising, sale/sharing and sensitive-information opt-outs remain available where the relevant processing and law apply. We will not unlawfully discriminate or retaliate because you exercise a privacy right.
Email privacy@no-ta.app with your request, account email or username if relevant, and country/region. We may seek proportionate verification and an agent’s authority, but do not send passwords, one-time codes or unsolicited ID images. If needed, we will explain a suitable way to verify your request. You may raise a concern without identifying yourself where lawful and practicable, although account-specific action can require verification.
We will acknowledge the request, assess it and respond within the applicable legal deadline. If a lawful extension, fee or refusal applies, we will explain the reason and available review routes. Rights are subject to applicable exceptions, including protection of others’ information; they do not require use of a particular subject line or access to the app.
12. Regional rights and privacy complaints
Contact privacy@no-ta.app with the issue, relevant dates and requested outcome. We will investigate, request necessary clarification and provide a reasoned response. If you disagree, you may ask for reconsideration at the same address. This process does not remove rights to contact a regulator or seek a court remedy within the applicable time limit.
- Australia: you may seek access or correction and complain about our handling of personal information. If unresolved, the Office of the Australian Information Commissioner explains its complaint process and when to escalate.
- New Zealand: applicable access, correction and complaint rights include escalation to the Office of the Privacy Commissioner.
- EEA, UK and Switzerland: applicable rights include access, correction, erasure, restriction, objection, portability, withdrawal of consent and safeguards for qualifying automated decisions. You may complain to your competent supervisory authority, including the UK Information Commissioner where relevant. Transfer safeguards may be requested as described above.
- United States: where state privacy law applies, you may have rights to know, access, correct, delete, obtain a portable copy, use an authorised agent, opt out of covered sale/sharing, targeted advertising or profiling, and restrict certain sensitive-data uses. The categories, sources, purposes and recipients are described in sections 2–6. To appeal a denied request, reply to the decision or contact privacy; we will explain any further route required by your state’s law. This Policy does not assert that every listed category was collected about every resident in the preceding 12 months.
- Brazil and Canada: applicable local law may provide access, correction, deletion or anonymisation, portability, information about sharing, consent withdrawal and complaint rights. Additional provincial rules, including Quebec requirements, may apply. Contact privacy to exercise them.
- Other countries, including Arabic-speaking jurisdictions: applicable local privacy, language, transfer and complaint rights remain available. Identify your country so we can assess the correct rules; this general notice does not replace any legally required local notice or representative.
13. Children and young people
NO'TA accounts are for adults aged 18 or above worldwide, or any higher applicable minimum age. Parental permission does not waive that threshold. Children and young people retain applicable privacy protections even when they are not eligible for an account.
We may process limited information to determine age before we know whether someone meets the threshold. If we identify an underage account, we restrict access and address removal of information as required by law. Underage status is not a justification for keeping all associated data indefinitely. Age-assurance purpose limits and destruction requirements apply. Report suspected underage access or child-safety concerns to support, privacy or abuse@no-ta.app; do not email or redistribute child sexual abuse material.
14. Security and incidents
We use access controls, protected authentication, database permissions, transport protections and operational safeguards designed to protect information. Relevant account features include passkeys and two-factor authentication where available. No system is completely secure, and the Services do not promise end-to-end confidentiality for public-context conversations.
If an incident occurs, we assess and contain it, investigate affected information, and notify affected people and regulators where legally required. Report a suspected vulnerability to security@no-ta.app. Protect your devices and credentials and avoid exposing sensitive information in public content or reports.
15. External links and independent services
Following an external link, connecting a sign-in provider, sharing externally or using a third-party service may disclose information to that service under its own rules. Review the relevant notice. We distinguish independent providers from processors acting on our behalf; merely calling a provider a third party does not remove our responsibilities.
External services and public recipients may retain copies outside NO'TA’s control. Where we are required to notify a recipient of correction or deletion, or assist with an applicable rights request, those duties remain.
16. Changes and language
We update this Policy when relevant practices or legal requirements change, publish the revision date and provide additional notice of material changes. Where a new purpose requires consent, we seek it before proceeding. Continuing to use NO'TA does not itself authorise new optional or incompatible processing.
Full English and Arabic versions are intended to carry the same meaning. If there is an unresolved discrepancy, English prevails only where applicable law allows; mandatory local language and privacy protections remain. Contact privacy if you need clarification or an accessible copy.
17. Contact
Privacy contact for NOTA SOCIAL NETWORK PTY LTD: privacy@no-ta.app. Legal contact: legal@no-ta.app. Account assistance: support@no-ta.app.
Sydney, New South Wales, Australia. ABN 24 693 312 926; ACN 693 312 926. Include only what is necessary for your enquiry. These mailboxes are not emergency services.