Privacy Policy
||NAM — getnam.app Last updated: 3 September 2026
Who we are
||NAM is operated by Ottmic Productions CC, a close corporation registered in Namibia ("we", "us", "our"). ||NAM is a platonic hug-matching and human connection app available on iOS and Android.
Privacy contact: privacy@getnam.app
Who this policy applies to
This policy applies to users of the ||NAM mobile application and website. ||NAM's launch scope is Namibia, South Africa and the United States. The app supports United States sign-up, and one-time passcodes sent to +1 mobile numbers are delivered by Telnyx. Any expansion to other markets — including the EU/EEA — is future work that has not happened yet. We are not currently intentionally offering or marketing ||NAM in the EU/EEA. If our market availability changes, we will update this policy and reassess any additional legal obligations that apply.
Where you are located affects which additional rights apply to you. See the GDPR supplement, POPIA supplement, and California privacy section below.
The data we collect and why
1. Account registration data
| Data | Why we collect it |
|---|---|
| Email address | Account creation; transactional and service emails; and the one-time passcode for the controlled Android sign-up variant described below |
| Phone number | SMS one-time passcode (OTP) — the standard route for creating an account, and the route for signing back in to an existing account |
| Date of birth | To enforce our 18+ minimum age requirement |
| Display name | To show on your profile |
How signing in works
||NAM is passwordless. There is no ||NAM account password: we never ask you to create one, and we do not collect, store or hash account passwords.
You sign up and sign in with a one-time passcode (OTP) sent by SMS to your mobile number. This is the standard route for creating an account, and it is the route for signing back in to an existing account.
A one-time passcode may also be sent to your email address in one controlled case: a server-controlled Android sign-up variant that we may enable. That variant applies to creating an account. Email is not a route for signing in to an existing account.
Separately from signing in, we use your email address to send you transactional and service emails — for example account notices and safety alerts.
One-time passcodes are short-lived, single-use codes issued and checked by our authentication provider. A passcode is not kept on your account as an ordinary reusable credential, and a passcode that has been used or has expired cannot be used to sign in again.
2. Profile data
| Data | Why we collect it |
|---|---|
| Profile photos | To display on your public profile |
| Bio / about text | To display on your public profile |
| Location (city or coordinates) | To show you people nearby who are open to a hug; approximate distance is shown to other users — your precise coordinates are never shared publicly |
| Hug preferences | To match you with compatible people |
| Gender (optional) | To personalise your experience and discovery |
3. Identity verification data
Identity verification is available to eligible ||NAM Plus and ||NAM Premium members, and is included in those plans at no additional verification charge. Verification is carried out by our third-party provider Didit.
Successful identity verification within your current membership cycle unlocks Verified Hugger status and the verified meetup capabilities — sending and accepting meetup requests. Buying a plan does not by itself verify your identity; you must complete verification successfully. Verified Hugger is a status and badge, not a separate subscription plan.
Free users and users on the 30-Day Launch Pass do not receive Verified Hugger status and cannot send or accept meetup requests. Free users may use core matching and messaging functionality subject to Free-plan limits. Where verification is offered to you, the process involves:
- A government-issued ID document scan
- A facial selfie and passive liveness check
Biometrics disclosure: Your ID document, selfie, and liveness data are captured through Didit and transmitted to Didit for verification. Ottmic Productions CC does not store your ID-document images or liveness video in its own database. ||NAM does, however, receive and store limited verification-derived identity data in restricted private records, including your verified first name, last name/full name, date of birth, verification status, verification date/timestamp, and Didit session reference ID. We do not store your biometric images or your ID-document images in our own database.
Biometric and verification data processed by Didit is used for identity-verification, fraud-prevention, authentication, and related verification purposes described in Didit's Verification Privacy Notice and Privacy Policy. ||NAM's live Didit workflow is configured with a 5-year retention period for verification data held by Didit.
Where applicable law (including GDPR for EU/EEA users, and certain US state laws) requires explicit consent for biometric processing, you will be asked to give that consent at the point of verification, separately from your acceptance of this Privacy Policy.
4. Trusted Buddy data
If you choose to configure a Trusted Buddy safety contact, we store the buddy's phone/WhatsApp number so the app can prepare a WhatsApp message for you to send from your own device. ||NAM does not automatically send that message on your behalf. We do not require or store a Trusted Buddy name in the current live design. Trusted Buddy contact data is not included in the 7-year restricted safety archive when your account is deleted.
5. Usage and activity data
| Data | Why we collect it |
|---|---|
| Messages sent and received | To deliver in-app messaging |
| Hug requests sent and received | To operate the matching feature |
| Meetup coordination details | To support in-person meetup planning |
| Reports and blocks | To enforce safety and community standards |
| Push notification tokens | To send you notifications you have opted in to |
6. Technical and device data
| Data | Why we collect it |
|---|---|
| Device type and OS | To ensure the app works correctly on your device |
| App version | To support you and deliver updates |
| Crash reports and stack traces | To identify and fix technical errors (may incidentally include limited PII — see Sentry below) |
| IP address | Security, fraud prevention, and approximate location |
7. Subscription and payment data
We do not process or store your payment card details. Subscription purchases are handled entirely by Apple (App Store) or Google (Google Play). We receive from our subscription management provider RevenueCat a record of your subscription status, entitlements, and purchase history (but not raw card data).
8. Analytics data
With your consent, we collect pseudonymised analytics data — including which features you use, screens you visit, and actions you take — to improve the app. Analytics is disabled by default until you opt in, and withdrawing consent stops further Mixpanel analytics collection. We do not send raw location coordinates or message bodies to Mixpanel. We do not use this analytics data for advertising, cross-app or cross-site tracking, or data-broker purposes. See Mixpanel below.
9. Device calendar
If you choose "Calendar" on a public event, the app asks your device to add that one event to your calendar, and your device may ask for calendar permission at that moment. ||NAM only writes the event you chose. ||NAM does not read, browse, or upload your calendar through this feature, and no calendar content is sent to us or to any third party. You can refuse the permission and continue using the rest of the app.
10. Website visitors and website forms
When you visit getnam.app or submit one of our website forms, our hosting and anti-abuse providers process ordinary request information such as your IP address, browser and device characteristics, and which pages or endpoints you requested. See Vercel and Cloudflare Turnstile under third-party recipients below.
How we use your data
We use your data to:
- Create and maintain your account
- Show your profile to other eligible users within your area
- Deliver in-app messaging, hug requests, and meetup features
- Verify your identity when you are an eligible ||NAM Plus or ||NAM Premium member and choose to complete verification
- Send you transactional emails (account notices, safety alerts)
- Send you push notifications you have opted in to
- Send you one-time passcodes by SMS so you can create an account and sign back in, and by email where the controlled Android sign-up variant is enabled
- Process and manage your subscription entitlements
- Detect and prevent fraud, abuse, and safety violations
- Enforce our Terms of Service and Community Guidelines
- Improve, analyse, and develop the app
- Comply with legal obligations
Automated safety screening of messages
To protect people from scams, harassment, and pressure to move off the platform, message content is automatically checked before it is delivered for prohibited sharing of personal contact information — for example phone numbers, email addresses, physical addresses, or handles and links for other messaging or social platforms. The underlying rule is set out in our Terms of Service and Community Guidelines. This applies per conversation. Once a meetup request has been accepted in a conversation, contact sharing becomes available in that conversation and remains available there, and messages in that conversation are no longer checked for contact information. Other conversations are unaffected.
If a message is blocked, we record the violation, including the text you attempted to send, so that we can apply the rule consistently and investigate abuse. You are told that your message was blocked, and the other person is told that a message was blocked — but not what it said. Repeated blocked attempts within a short period can trigger a temporary restriction on sending messages, which lifts by itself when it expires. We do not publish the details of how this check works, because that would help people evade it.
These checks are automated and are applied to message content only; they are not used to profile you or to make decisions about your identity verification or your subscription. If you believe a message was blocked or your messaging was restricted in error, contact support@getnam.app and a person will review it.
Legal bases for processing (GDPR)
For users in the EU/EEA, we rely on the following legal bases:
| Processing activity | Legal basis |
|---|---|
| Account creation and core app functions | Performance of contract (Art. 6(1)(b)) |
| Location-based discovery | Performance of contract and, where required, your permission/consent to access device location |
| Safety reports and blocks | Legitimate interests (safety and fraud prevention) (Art. 6(1)(f)) |
| Automated safety screening of messages for prohibited contact details | Performance of contract and legitimate interests (user safety and abuse prevention) (Art. 6(1)(b) and 6(1)(f)) |
| Bot and abuse prevention on website forms | Legitimate interests (security and abuse prevention) (Art. 6(1)(f)) |
| Push notifications | Consent (Art. 6(1)(a)) |
| Analytics | Consent (Art. 6(1)(a)) |
| Biometric identity verification | Explicit consent (Art. 9(2)(a)) |
| Legal compliance | Legal obligation (Art. 6(1)(c)) |
Our third-party data recipients
We share your data with the following third-party service providers only to the extent necessary for the services they provide. We do not sell your personal data to any third party.
Mobile information and SMS consent: Mobile information, SMS opt-in data, and SMS consent are not sold, rented, or shared with third parties or affiliates for their marketing or promotional purposes. This does not restrict disclosure to service providers that process authentication messages on our behalf, or disclosures required by law. Those service providers are named below: Supabase issues and checks the one-time passcode, and Africa's Talking and Telnyx deliver it by SMS; those messaging providers in turn hand the message to the telecommunications carriers and mobile networks that deliver it to your handset. We share only the minimum necessary to send and deliver that code — your mobile number, the message itself, and related delivery records — and none of these messaging providers, carriers or other SMS-delivery vendors may use it for their own promotional or marketing purposes, or for any purpose unrelated to delivering the code you asked for. The only SMS ||NAM sends you are these one-time passcodes and related account-security messages; there is no marketing SMS programme, and your mobile number is not used to send you marketing SMS.
Supabase
What they receive: Core user data needed to operate the service, including account details, profile data, messages, location, photos, meetup records, reports, blocks, and activity. Why: Supabase is our backend database and file-storage provider. Where: The production Supabase project is hosted in eu-west-2 (London, United Kingdom).
Sentry
What they receive: Crash reports and application error logs, which may incidentally include device information and app state. ||NAM does not attach a normal user identity through Sentry's setUser mechanism. Data scrubbing is enforced, default scrubbers are required, storage of IP addresses is disabled, and minidumps are not stored as attachments.
Why: To identify and fix technical errors in the app.
Where: European Union (EU). Ordinary Sentry error/crash data is retained for 30 days under the current Developer plan. Ottmic Productions CC has accepted Sentry's Data Processing Amendment v5.1.0 (signed 15 August 2026).
Mixpanel
What they receive: Consent-gated analytics events associated with a pseudonymous/UUID-based app identifier and the limited profile properties allowed by our hardened analytics implementation. We do not send raw location coordinates or message bodies to Mixpanel.
Why: To understand how people use ||NAM and improve the product.
Where: Mixpanel's EU data-residency endpoint (api-eu.mixpanel.com) is configured for the live project.
RevenueCat
What they receive: Your subscription status, entitlements, and purchase history. RevenueCat also receives a device identifier. Why: To manage your subscription and unlock premium features. Where: United States.
Expo / EAS
What they receive: Push notification tokens; over-the-air (OTA) app update delivery. Why: To deliver push notifications you have opted in to, and to push app updates without requiring a full App Store or Play Store release. Where: United States.
Didit
What they receive: Your government ID document, selfie/liveness capture, device and verification telemetry required to perform identity verification. What Didit returns to ||NAM: Verification status/result, session reference and timestamp, plus limited verified identity fields used in our restricted private verification records, including verified first name, last name/full name and date of birth. ||NAM does not store the underlying ID-document images or liveness video in its own database. Why: To confirm your identity so that eligible ||NAM Plus and ||NAM Premium members who complete verification can obtain Verified Hugger status and the verified meetup capabilities. Where: Didit's current documentation establishes EU-default processing/storage infrastructure for verification data. Its contractual framework includes a DPA and international-transfer safeguards, including SCC-based safeguards where applicable. Retention: The live ||NAM Didit workflow is configured to retain Didit-held verification data for 5 years.
Note: Didit also describes separate roles for certain aggregated or pseudonymised data it may use for its own service/algorithm improvement; we do not describe Didit as acting exclusively as our processor in every context.
Resend
What they receive: Information needed to send transactional and operational emails. Depending on the email, this can include names and email addresses, waitlist information, community-event information and written feedback, influencer-program information, and safety-report details such as reporter/reported-user names, email where available, plan, verification status, internal user IDs, report reason/details, timestamp and report ID. Waitlist-threshold administrative alerts may include a rounded aggregate cluster centre rather than an individual user coordinate. Why: To deliver transactional/operational email and notify the ||NAM team of relevant operational or safety events. Where: Resend stores relevant customer/account data in the United States. Its contractual framework includes data-processing and international-transfer safeguards, including SCC-based safeguards where applicable.
Africa's Talking
What they receive: Your phone number and the SMS information needed to route and deliver one-time passcodes, together with related delivery records/logs. Why: SMS OTP authentication for routes handled by Africa's Talking.
Telnyx
What they receive: Phone numbers, SMS content needed to deliver OTP messages, and related delivery records for routes handled by Telnyx. Why: SMS OTP authentication and message delivery. Where: No explicit Telnyx Data Storage Location has been selected for the ||NAM account. We therefore do not claim a specific Telnyx residency region. Telnyx's contractual framework includes data-processing and international-transfer safeguards.
Cloudflare (Turnstile)
What they receive: Ordinary browser, device, and network signals from your visit — including your IP address — when a Cloudflare Turnstile challenge runs on one of our website forms. Why: Bot and abuse prevention on the relevant website forms, including the influencer application form and the illegal-content report form. Turnstile is used on our website only; it is not part of the mobile app. Where: Cloudflare's global infrastructure. See Cloudflare's privacy policy.
Vercel
What they receive: Ordinary request and log information needed to serve and secure the site — including your IP address, the URL you requested, the time of the request, and browser/device characteristics. Vercel also hosts the endpoint that receives illegal-content reports submitted through our website form, and therefore processes the contents of a report you submit there in transit. Why: To host and deliver the getnam.app website and the website report endpoint, and to keep them available and secure. Where: Vercel's hosting infrastructure. See Vercel's privacy policy.
||NAM Influencer Programme applicants
This section applies if you apply to the ||NAM Influencer Programme through our website. It is in addition to the rest of this policy.
What we collect from you:
- Your legal name, display name, email address, country, and the referral code you request
- Your mobile phone number, together with a derived, irreversible fingerprint of that number used for anti-abuse and duplicate-application checks
- Your social-media information — platform, handle and/or profile URL, and follower count for each profile you add
- Your preferred payout currency
- Your notification preferences, and the programme terms version you accepted with the date and time
- Your application, email-verification, and review status, including the review decision and internal review notes
How access works: we confirm your email address by sending you a verification link, and we sign you in to the influencer portal using short-lived links rather than a password. The influencer portal and our internal admin tools use time-limited sessions. We store only what is needed to check those links and sessions, and we do not describe how they work internally.
Communications: we email you about your application, its verification and review outcome, and the ongoing administration of the programme.
Banking details: we do not collect bank-account or payout-account details when you apply. Payout details are requested separately, later, and only if your application is approved.
Anti-abuse: the application form is protected by Cloudflare Turnstile and by rate limits. See Cloudflare (Turnstile) above.
Retention: your plain phone number is cleared from the application record when the application is approved, declined, or expires; the derived anti-abuse fingerprint is kept. We otherwise keep application and review records for as long as we need them to run the programme, prevent fraud and abuse, and meet our legal, financial, and accounting obligations, and we delete or de-identify them once they are no longer needed for those purposes.
Influencer-programme privacy enquiries and requests: privacy@getnam.app.
International data transfers
Ottmic Productions CC is based in Namibia. Our service providers may process personal information in Namibia, South Africa, the European Union, the United States, and other countries in which they or their subprocessors operate.
Where personal information is transferred across borders, we use the safeguards available and appropriate to the particular transfer, which may include provider data-processing agreements, contractual transfer safeguards (including Standard Contractual Clauses where applicable), adequate-protection arrangements, consent where appropriate, or another lawful transfer mechanism.
South Africa: Where section 72 of POPIA applies to a transfer, we will make that transfer only where a lawful condition under section 72 is available for it. Which condition is relevant depends on the particular transfer and the recipient. For further information about a specific transfer, contact privacy@getnam.app.
How long we keep your data
| Data category | Retention |
|---|---|
| Account and profile data | Until you delete your account, subject to exceptions below |
| Messages (while your account is active) | Retained to provide in-app messaging. Ordinary access ends when you delete your account — see "Restricted safety evidence retained after account deletion" below for what may be preserved |
| Connection and meetup records (while your account is active) | Retained to operate hug requests/matches and support in-person meetup planning. Ordinary access ends when you delete your account — see "Restricted safety evidence retained after account deletion" below for what may be preserved |
| Photos | Until you delete your account or remove them |
| Location data | Used for foreground location-based features. ||NAM does not maintain a general user location-history table, does not use a background-location architecture, and does not expose precise coordinates peer-to-peer. Exact coordinates are stripped from onboarding-progress storage, converted waitlist rows clear exact coordinates, and waitlist-threshold administration uses a rounded aggregate cluster centre rather than one user's exact coordinate. |
| Reports and PII/safety-violation records (while your account is active) | Retained to enforce safety and our Community Guidelines. Ordinary access ends when you delete your account — see "Restricted safety evidence retained after account deletion" below for what may be preserved |
| Restricted safety evidence retained after account deletion | If you delete your account, certain records connected to it — messages from conversations you were part of, connection and meetup records, reports, PII/safety-violation evidence, and a limited safety identity record — may be preserved in a restricted, access-limited archive for up to 7 years from the date of deletion. The safety identity record can include limited identifiers needed to associate this evidence with your deleted account, such as your registered email address or phone number and your verification/account-status information — it does not include your full deleted profile (for example, your bio, date of birth, precise location, or profile photos are not part of it). This supports user safety, abuse and fraud prevention, investigation of incidents or complaints, enforcement of our Terms of Service and Community Guidelines, and the establishment, exercise, or defence of legal claims. A documented legal or safety hold may extend retention where necessary and lawful. Expired, non-held evidence is automatically purged. This archive is not accessible through ordinary use of the app. |
| Subscription and purchase records | Limited transaction/subscription records may be retained after account deletion where reasonably necessary for financial, tax, accounting, fraud-prevention, disputes/chargebacks, subscription-entitlement administration, or legal-compliance purposes. Apple, Google, RevenueCat and other payment processors may independently retain transaction records under their own obligations and policies. Retained transaction records are not used to recreate a deleted social profile. |
| Crash and diagnostic data | Ordinary Sentry error/crash data is retained for 30 days under the current Developer plan. |
| Analytics data | Mixpanel event data is retained for up to 2 years under the retention policy applicable to the current GetNam project. |
| Identity verification data stored by ||NAM | Restricted verification-derived identity data — including verified first name, last name/full name, date of birth, verification status, verification date/timestamp and Didit session reference ID — is retained while your account is active. After deletion, only limited verification/account-status information needed for the restricted safety identity record may be preserved for the safety-retention period described above; your date of birth is not part of that safety identity record. |
| Identity verification data held by Didit | 5 years under the current live ||NAM Didit workflow configuration. |
| Supabase database backups | For this Privacy Policy, ||NAM applies a maximum provider-controlled database-backup retention period of 7 days as its launch retention baseline. Depending on the Supabase plan actually active at a given time, the provider may retain backups for a shorter period or may not provide the same managed-backup feature. If you delete your account, residual copies of data may remain in these provider-controlled backups until they are removed through the provider's normal retention and rotation process. Backup copies are not used to recreate a deleted account for ordinary product use. |
When you delete your account, the following happens immediately: your live profile is taken down, your authentication identity and login credentials are permanently deleted, your avatar/profile photos are permanently deleted from storage, and your ordinary access to messages, connections, meetups, and other account activity through the app ends.
Certain safety-related records connected to your account — such as messages from conversations you were part of, connection and meetup records, reports, and evidence of Terms or Community Guidelines violations — may be preserved afterwards in a restricted, access-limited safety archive that is separate from the live product. This archive exists to support user safety, abuse and fraud prevention, investigation of incidents or complaints, enforcement of our Terms of Service and Community Guidelines, and the establishment, exercise, or defence of legal claims. It is retained for up to 7 years from the date of deletion, unless a documented legal or safety hold requires it to be kept longer where necessary and lawful. Evidence that is no longer subject to a hold and has passed its retention period is automatically purged. This archive is not accessible through ordinary use of the app or by other users, and access to it is restricted to what is necessary for the purposes above.
Some data may also persist temporarily in encrypted provider backups before being removed through the provider's normal retention/rotation cycle. For this Privacy Policy, ||NAM applies a maximum provider-controlled database-backup retention period of 7 days as its launch retention baseline; depending on the Supabase plan actually active at a given time, the provider may retain backups for a shorter period or may not provide the same managed-backup feature. Limited transaction/subscription records may also be retained for the purposes described in the retention table above. Records held independently by Apple, Google, Didit, RevenueCat, or other processors are subject to those processors' own legal obligations and retention policies.
Your rights
Regardless of where you are located, you may contact us at privacy@getnam.app to:
- Access the personal data we hold about you
- Correct inaccurate personal data
- Delete your account and personal data (you can also do this in-app)
- Export a copy of your data in a portable format
- Object to or restrict our processing of your data
We will respond within the period required by applicable law and aim to respond to ordinary requests within 30 days where practicable. We may need to verify your identity before processing a request.
See the GDPR, POPIA, and CCPA sections below for additional rights specific to your location.
GDPR — EU/EEA users
If you are located in the EU or EEA, the General Data Protection Regulation (GDPR) applies to our processing of your personal data.
In addition to the rights listed above, you have the right to:
- Withdraw consent at any time where we process your data on the basis of consent, without affecting the lawfulness of processing before withdrawal
- Restrict processing in certain circumstances
- Lodge a complaint with the data-protection supervisory authority competent for your location
Special categories of data: Biometric data used to uniquely identify a person is a special category under GDPR Article 9. We process biometric data only with your explicit consent and only through Didit for the purpose of identity verification.
EU representative: ||NAM's current intentional launch scope does not include the EU/EEA. We are not currently intentionally offering or marketing the service in the EU/EEA, and no EU representative has been appointed. Before any intentional launch or marketing in the EU/EEA, we will assess which obligations apply and appoint any representative required at that point.
Data Protection Officer: ||NAM's current intentional launch scope does not include the EU/EEA. Whether a formal GDPR Data Protection Officer is required, together with the other EU-specific governance obligations that may apply, will be assessed before any intentional launch or marketing in the EU/EEA. Privacy enquiries can be sent to privacy@getnam.app.
POPIA — South African users
If you are located in South Africa, the Protection of Personal Information Act 4 of 2013 (POPIA) applies.
Your rights under POPIA include the right to:
- Know whether we hold personal information about you
- Request access to and correction of your personal information
- Request deletion or destruction of your personal information
- Object to the processing of your personal information
- Submit a complaint to the Information Regulator of South Africa
Information Regulator: inforegulator.org.za | complaints.IR@justice.gov.za
Information Officer: Michael Ott, Ottmic Productions CC. Formal registration with the Information Regulator is in process. Privacy enquiries: privacy@getnam.app.
California privacy
The United States is within ||NAM's launch scope: the app supports United States sign-up, and one-time passcodes sent to +1 mobile numbers are delivered by Telnyx. We will assess which United States federal and state privacy requirements apply to ||NAM and what they require of us, and we will update this policy as that assessment concludes.
Regardless of launch territory, California users may use the general privacy-request process above to ask to access, correct, or delete personal information we hold about them, subject to applicable exceptions.
We do not sell personal information, and we do not use personal information for cross-context behavioural advertising. We do not currently provide a "Do Not Sell or Share My Personal Information" mechanism. We will reassess this if we introduce cross-context behavioural advertising or otherwise become subject to an applicable opt-out requirement.
Sensitive information: Precise geolocation is used only for core location-based functionality and safety/meetup-related features described in this policy; it is not sold or used for cross-context behavioural advertising.
California privacy requests: Email privacy@getnam.app with the subject line "California Privacy Request" and your registered email address or phone number. We may verify your identity before processing a request.
Children
||NAM is strictly for users aged 18 and over. We do not knowingly collect personal data from anyone under 18. If we become aware that a user is under 18, we will immediately suspend and delete their account. If you believe a user may be under 18, please report them in-app or contact our dedicated child-safety address, childsafety@getnam.app. General safety concerns that do not involve a minor can be sent to safety@getnam.app. See our Child Safety Standards.
Security
We use industry-standard technical and organisational measures to protect your personal data, including encrypted data transmission (TLS), passwordless one-time-passcode authentication (||NAM does not use or store account passwords), access controls, and row-level security on our database. No system is completely secure, and we cannot guarantee absolute security.
Changes to this policy
We will notify you of material changes to this policy by email or by an in-app notice before the change takes effect. The "Last updated" date at the top of this document will always reflect the current version.
Contact us
Ottmic Productions CC
3 Kerby Street
Windhoek, Namibia
Privacy enquiries: privacy@getnam.app
General legal: legal@getnam.app