Privacy Policy

1. Who we are and what this policy covers

Nootro Inc. operates Razam, an invite-only community for meeting people and making plans. Our mailing address is 379 West Broadway, Fl 2, New York, NY 10012, USA. Contact us about privacy, access to your information, or deletion at admin@nootro.studio.

This policy covers the Razam app, the Razam website and waitlist, community administration, and communications with us. It does not cover other products merely because they have the same operator. Nootro Inc. is responsible for the personal information it processes for Razam and is the controller where that term applies.

Razam is free to use. Available features and controls can differ by app version and rollout, and some features are released gradually or can be enabled or disabled by us. This policy describes information processed when you use the relevant feature; it does not mean every feature is available to every account.

2. Information you give us

Account and admission information: your account identifier, sign-in provider information, email address and name when supplied by that provider, invitation codes and their redemption, membership status, and waitlist information. Sign in with Apple may supply a private relay email rather than your personal email. We do not ask you to enter your email address again in the app. On the website waitlist we collect the email address you submit; an in-app admission request can also include your selected city.

Profile information: your display name, city, age, gender, neighborhood, biography, interests, visibility preferences, and up to five profile photos, including their order and main-photo selection. Your display name can be the name supplied by your sign-in provider or a neutral display name; you can edit it, and it does not have to be your legal name, but it must not impersonate another person. Age is required: Razam is for adults, and you must confirm that you are 18 or older to create a profile. Gender is required but you can choose Prefer not to say. Age and gender are saved once and cannot be edited in the app afterwards; if you entered them incorrectly, email admin@nootro.studio to request a correction as described in Section 9. Avoid including sensitive information or other people's personal information that you do not have permission to share. We do not ask for a government ID or claim to have independently verified every member's age or identity.

Community activity: profiles you like or pass, mutual matches, Event descriptions and categories, date or flexible-time choices, meeting places and route points, applications to join, invitations, responses, participants, attendance or completion actions, and enabled follow-up or Circle features. We also process the messages you send and the identifiers and timestamps needed to deliver conversations.

Safety and support: reports, block actions, the content or explanation submitted with a report, moderation outcomes, appeals, deletion requests, and correspondence with us. Do not send passwords, authentication codes, payment-card details, or unnecessary identity documents to support.

3. Device, location, and technical information

With your device permission, the app uses location to show relevant map content and nearby plans. You can change permission in iOS Settings. Profile discovery uses a city or neighborhood and your map-visibility setting; it is not intended to broadcast your live GPS position to other members. This is different from an Event location: meeting places and route points that you choose may include precise coordinates and street addresses.

Place searches and map requests are handled by Apple MapKit. A search query and the location or map context needed to answer it may be processed by Apple under its applicable terms and privacy policy. You can choose a public meeting place instead of your home or workplace.

Our infrastructure and service providers process technical information such as IP addresses, request and security logs, device or app information, authentication and app-attestation signals, and push-notification tokens. These help operate the service, prevent abuse, and deliver notifications. If you use a TestFlight build, Apple may also provide diagnostic information or feedback associated with TestFlight testing.

When the corresponding measurement feature is enabled, we collect limited first-party product measurements, such as an Event being published, a match being created, or an invitation being redeemed. These records can contain pseudonymous identifiers and timestamps. Pseudonymous does not mean anonymous: we may be able to associate those identifiers with service records.

4. Why we process information

We use information to register and admit members, display profiles and Events to their intended audience, find relevant people and plans, manage invitations and matches, deliver messages and notifications, support users, and maintain the service. We also use it to detect abuse, enforce community rules, assess reports and appeals, investigate security problems, meet legal obligations, and understand whether core features work.

Where a law requires a legal basis, the basis depends on the activity: performing our agreement with you for the service you request; our legitimate interests in operating and securing a community, balanced against your rights; compliance with legal obligations; or consent when required, including for relevant device permissions or optional processing. We do not treat reading this policy as blanket consent to every use of personal information.

We do not sell personal information, share it for cross-context behavioral advertising, or use profile photos or private messages as advertising testimonials without separate permission. Razam does not show advertising and does not operate an advertising-targeting feature. If we introduce materially different processing, we will provide appropriate notice and obtain consent where required before that processing begins.

Other eligible members can see profile information and photos made available through discovery and community features. Profile map visibility is controlled separately from other profile discovery: hiding your map presence does not necessarily hide your profile everywhere. Event audiences and membership or safety controls determine who can discover a plan.

An Event detail may reveal the precise meeting point and route you entered to eligible members before they join. Do not assume that only confirmed participants can see an Event's location. A host can see applications and applicant information needed to choose participants. Requests to join are not a public applicant list. Match and conversation information is available to the relevant participants; private likes are not displayed as a public list.

Messages are stored and delivered by our servers. They are not end-to-end encrypted. Authorized service processing, automated moderation, and appropriately authorized staff handling safety, support, or legal matters may access relevant content. Transport and infrastructure protections are not the same as end-to-end encryption.

Members may copy, photograph, or share information they can see. We cannot retrieve copies held by another person. If an enabled sharing feature creates an external link or recap, consider its audience before using it; the applicable access controls and choices are shown by that feature.

We use service providers to host and secure Razam, store information and media, authenticate accounts, deliver notifications, and moderate content. Relevant services include Google Firebase and Google Cloud, Apple sign-in, maps and notification services, and website security and font services described below. Providers receive information needed for their role; some, such as Apple for its own platform services, also process information under their own policies.

We may disclose relevant information when reasonably necessary to comply with a valid legal process, protect rights and safety, address fraud or security incidents, or complete a merger, financing, restructuring, or transfer of the service subject to appropriate safeguards and any required notice. We do not provide unrestricted database access to other members.

6. AI-assisted moderation and human review

Razam uses automated rules and, when enabled for the feature, Google Cloud Natural Language text moderation and Google Cloud Vision SafeSearch image moderation. For profile text requiring an additional language check, Razam may also use Gemini on Google Cloud after obtaining your updated explicit permission. These are third-party AI services used only for content safety analysis. Razam does not provide an AI chat, assistant, or companion feature.

Text submitted for analysis may include profile names, biographies and interests, and Event descriptions and location labels or route notes. Profile photos are processed into app image variants and submitted for image safety analysis. Do not include secrets or unnecessary sensitive information in this content. We use the resulting safety classifications to allow, reject, or hold content for review and to maintain relevant moderation records.

Private chat messages between members are not submitted to third-party AI moderation services. Chat text is checked on our servers by automatic word filtering, which may block or reject a message. Before this update, chat-message text was submitted to third-party AI text moderation under the then-current permission; that processing has stopped for new messages, and records created by it are handled under the retention rules below. Chat messages are still hosted and delivered by our servers as described in this policy, and reports, blocking, and authorized staff safety access continue to apply to them.

Automated systems can make mistakes and may handle languages differently. An Event may wait for human review; a profile update or message may instead be refused with an error and require editing or a support request. We do not promise that every rejected item automatically reaches a human reviewer. You can ask for a review or challenge a restriction by emailing admin@nootro.studio with the relevant context. Do not resend unrelated private information.

We do not use this moderation integration to train our own general-purpose AI model. Provider processing is governed by the applicable service terms and privacy commitments; this policy does not promise that all providers retain no technical data. Where separate permission for third-party AI processing is required, it must be requested before that processing; this policy is a disclosure, not a substitute for that permission. If you decline or withdraw that permission, content that must pass this safety analysis before it becomes visible to other members cannot be published until the permission is given; declining it does not by itself withdraw other permissions you have given, and neither this policy nor your acceptance of the Terms is blanket consent to that processing. Moderation is not a guarantee that people, content, or meetings are safe and is not an emergency-response service.

7. Website cookies, security, and outside services

The landing page uses Google reCAPTCHA Enterprise to protect the waitlist against bots and abuse. Google may process device, network, and interaction signals and use security cookies, including _GRECAPTCHA. The reCAPTCHA script can load when you visit the page, before you submit a form. The page also loads Google Fonts, which means your browser requests font resources from Google and exposes ordinary request information such as your IP address to that provider.

The public waitlist stores your email and submission status. Its abuse protection uses an opaque, time-limited identifier derived from an IP address rather than storing the raw IP address in the waitlist entry. This does not mean hosting providers or security systems never process IP addresses or logs.

Google's Privacy Policy and Terms apply to its relevant services: https://policies.google.com/privacy and https://policies.google.com/terms. Information about Firebase processing is available at https://firebase.google.com/support/privacy. Apple's Privacy Policy is available at https://www.apple.com/legal/privacy/.

We do not use the current landing page for behavioral advertising. We do not currently change its behavior in response to a browser Do Not Track signal. We do not sell or share personal information for targeted advertising regardless of whether a browser sends an opt-out preference signal. Browser and device settings can limit cookies or permissions, but some security or sign-in features may then not work. External websites that you choose to visit have their own policies.

8. Retention and deleting your account

We retain active account information while needed to provide the service and for the purposes described here. Waitlist information is retained while the admission request remains relevant or until you ask us to remove it, subject to necessary security or legal records. We consider the purpose, sensitivity, legal requirements, and operational need when deciding retention; not every record has the same lifetime.

You can delete your account in the app from Profile, Settings, Delete account. The app asks you to confirm with Apple again, revokes your Apple sign-in token, and submits the deletion request while that session is valid; you are signed out only after our server confirms the request. If you cannot sign in, email admin@nootro.studio instead, and we may verify that the request belongs to the account before acting on it. Deleting the app from a device does not delete your account.

When a deletion request is accepted, your account is deactivated immediately: your membership is marked for deletion, your profile is no longer shown to other members or on the map, your sign-in session and member credentials are revoked so you can no longer use community features, and removal of any Event share links you issued begins right away. Deletion of the rest of your data is queued as a background job that is scheduled to begin 30 days after the accepted request. From that point the job removes, in stages, your owned Events, authored messages and replies, Event participation records, connections and other relationship records, account metadata, and profile photos, and pseudonymizes the safety evidence described below; the sign-in account with our authentication provider is deleted in the final stage, after the earlier stages have completed. The job runs in bounded steps on a recurring schedule, is paused while a legal hold applies, and if a step fails it retries automatically with increasing delays of about one minute to about six hours between attempts. Because processing is staged, removal is not instantaneous on day 30 and we do not promise a specific completion date; where a law that applies to you requires deletion within a shorter period, that legal deadline applies, and you can contact us to ask about the status of your request. Minimal pseudonymized safety, report, moderation, and audit evidence is kept as a limited exception, and a separate purge of that evidence is scheduled to begin 90 days after the accepted request. Documented legal obligations or holds may require particular records to be retained longer. We restrict use of retained information to the relevant safety, security, or legal purpose.

Removing or replacing a profile photo makes it unavailable through the normal profile media service and schedules its stored variants for cleanup after 24 hours. Failed or abandoned uploads have a separate cleanup process. Short-lived caches or a copy already downloaded by another member may not disappear at the same moment.

These schedules concern records we control in the active service. Provider-managed logs, backups, and disaster-recovery copies have their own retention and deletion cycles. For example, Google's Firebase privacy information states that other Firebase Authentication information is removed from live and backup systems within 180 days after the customer initiates deletion; that provider cycle begins when we initiate deletion with Firebase, not when you uninstall Razam. We do not promise immediate erasure from every provider backup.

When created by an enabled measurement feature, limited pseudonymous product-event and notification-measurement records use a 90-day retention period. Expiry and deletion jobs are not an instantaneous wipe. If a request is delayed by a technical problem or a lawful retention requirement, contact us for its status; applicable legal deadlines still apply.

9. Your choices, privacy rights, and international processing

You can edit available profile fields and photos, change map visibility, manage notification and location permissions, block or report another member, and request deletion. Age and gender cannot be edited in the app after they are saved; to correct an error in either, email admin@nootro.studio and we will handle it as a correction request. Some information is needed to provide an account or a requested feature; if you do not provide it, that feature may be unavailable.

Depending on where you live and which laws apply, you may have rights to know about or access your information, obtain a portable copy, correct it, delete it, restrict or object to certain processing, withdraw consent, or appeal a decision about a privacy request. Withdrawal does not undo lawful processing already completed. To make a request or appeal, email admin@nootro.studio with enough information to identify the account and request. An authorized agent may contact us where allowed; we may need to verify identity and authority. We will not penalize you for exercising applicable privacy rights.

If applicable, you can also complain to the privacy regulator where you live or work. These statements do not claim that every privacy statute applies to every user or that additional rights replace mandatory local protections.

Nootro Inc. is based in the United States. Our service providers may process information in the United States and other countries, where laws may differ from those where you live. Where a restricted international transfer requires safeguards, we must use the applicable contractual or other lawful transfer mechanism. A provider's certification or safeguards do not mean Nootro Inc. itself holds that certification. Contact us for information about safeguards relevant to your data.

10. Age, security, and policy changes

Razam is intended only for people aged 18 or older. We do not knowingly allow children to use the service. If you believe a child has an account or has provided information, contact admin@nootro.studio so we can investigate and take appropriate action, including removal. An invitation is not proof of age, identity, or safety.

We use access controls and technical and organizational measures intended to protect information. No service can guarantee perfect security. Keep your account and device secure, do not share login codes, and report suspected unauthorized access promptly.

We may update this policy as the service or legal requirements change. The effective date and version identify this text. We will publish updates here and use an appropriate in-app notice, email, or other direct notice for material changes when required; we will seek fresh consent where required. For questions or requests, write to admin@nootro.studio or Nootro Inc., 379 West Broadway, Fl 2, New York, NY 10012, USA.