Privacy Policy

NextNoon privacy contact

NextNoon is operated by Automata, Incorporated. Contact support@nextnoon.app to request access, correction, deletion, restriction of processing or account deletion. Do not send passwords or verification codes.

Contact privacy support

Account deletion

1. Data we process

We process sign-in email, OAuth identifiers, name, birth date, country and timezone, organization email and affiliation, role, interests, activity preferences, location and distance settings, profile photos, and matching, chat, meeting, and report records.

2. Purposes

We use data for account and affiliation verification, recommendations and matching, scheduling and chat, notifications, safety reports, fraud prevention, and service operations.

3. Service providers

We may use Supabase for databases, Railway for APIs, Vercel for web delivery, Resend for email, and configured S3-compatible storage for media. Your selected OAuth provider processes social sign-in data.

4. Retention and deletion

Account data is retained while you use the service and related data and uploads are deleted when you delete your account. Limited records may be retained where required for law, security investigations, or disputes.

5. Your rights

You can edit your profile, reverify affiliation, block users, disable notifications, and delete your account. Use Delete account permanently in Settings or contact support@nextnoon.app. We may need to verify account ownership before processing a request.

6. Security

We use session cookies, access controls, password hashing, one-time codes, upload ownership checks, secret-safe logging, and moderator authorization checks.

7. Purchases and usage records

Recommendation Reset purchases involve store transaction identifiers, receipts or purchase tokens, products, purchase and refund status, credit usage and account linkage. We contact Apple or Google servers to verify purchases. We do not directly collect card numbers or bank account details. Transaction records may remain without the account link after account deletion for refunds and prevention of receipt reuse.

8. Face photos and screening data

We process profile photos you select and their thumbnails, removing EXIF metadata before screening. From Google Cloud Vision face-detection responses, we use face presence/count, detection confidence and face-box size to check that a face is sufficiently visible and that the main photo contains one person. We also screen for sexual or violent content. We do not identify people, compare identities across photos, create facial recognition templates or embeddings, or perform biometric authentication. We do not use facial landmarks, emotions or demographic attributes in profiles or recommendations. Raw screening responses, face coordinates and confidence values are used only in request-processing memory and are not saved in our database, files or logs.

8.1. Face-photo transfer, sharing and storage

Photos pass through the NextNoon API hosted on Railway to Google Cloud Vision’s synchronous online images:annotate API. Screening requests contain image bytes and requested features, not your sign-in email, nickname or affiliation. Google processes these photos to provide screening. According to Google’s Cloud Vision Data Usage FAQ, online image content is processed in memory without being persisted to disk, used for model training/improvement or shared with third parties. Google may temporarily log request metadata such as time and size. NextNoon stores accepted photos and thumbnails in Supabase Storage in Singapore, and photo references and the limited screening records described below in Supabase PostgreSQL in the same region. Display photos are shared as described in section 9. We do not sell face-screening data or disclose screening results to other users or advertisers.

Cloud Vision Data Usage FAQ

8.2. Face-photo retention and deletion

Photos and thumbnails remain while used in your profile, until replacement, removal or account deletion. Face count, screening-policy version and screening time are retained as photo metadata. Unused photos removed from a profile become eligible for periodic deletion after they are 24 hours old; the original, thumbnail and photo metadata are removed. Permanent account deletion immediately revokes photo access and removes photo metadata, and queues originals and thumbnails for erasure. Storage failures are retried, so physical erasure can be delayed. A retry cache contains only a non-reversible key, face count or rejection code; it is valid for 10 minutes and expired entries are periodically deleted. Newly rejected photos are not published to profile storage. Raw facial-analysis responses are not retained. Database backups may retain photo metadata for the backup retention cycle; Supabase database backups do not contain the photo files themselves. Request account deletion through My page → Delete account permanently or support@nextnoon.app.

8.3. Diagnostics

Push tokens, sign-in and usage records, request performance and errors support functionality, safety and troubleshooting. Sign-in SDKs may process device identifiers, usage and diagnostic data. We do not use data for advertising tracking.

9. Sharing with other users

Profile names, photos, affiliation, occupation, interests and meeting preferences are shown to recommended or connected users. Messages and meeting details are shared with the participants in that conversation or meeting. Your sign-in email and precise meeting-verification coordinates are not shown to other users.

10. Google place search

Workplace searches send query text, the selected place ID, a search session identifier, country and language to Google Maps Platform, not your sign-in or affiliation email. Your selected place ID and personal coordinates support recommendations and distance calculations. Google place names, addresses and predictions are not permanently stored. Coordinate caches are deleted after 28 days and fetched again when needed. Google’s Privacy Policy also applies.

Google Privacy Policy