Privacy Policy

1. Who we are and what this policy covers

CoMinded LLC, registered and operating in Arizona and branded CoMinded, Co.Minded, or Company Minded (“CoMinded,” “we,” “us,” or “our”), provides a membership community that introduces entrepreneurs to nearby peers through monthly groups, meetups, member-hosted events, a community feed, and messaging. Our membership service is offered in supported locations within the United States. This Privacy Policy explains how we handle personal information when you visit companyminded.com, apply for membership, use our mobile app or related web experiences, participate in the community, or contact us (together, the “Services”).

This policy covers applicants, including people who are waitlisted or not approved, members, website visitors, and people whose information is included in a support request or report. Our authorized administrative tools support these same Services. Third-party websites, payment wallets, calendar services, social networks, and independently organized activities may have their own privacy practices, as described below.

A privacy policy explains data practices; it is not a request for blanket consent. Where separate permission or consent is required for a feature, that permission must be obtained separately. Membership pricing, renewals, cancellation, conduct, and other contractual conditions are addressed in the applicable membership disclosures and terms, rather than being authorized by this policy.

2. Information we collect

The information involved depends on which Services you use. Some fields are required to review an application, maintain an account, or provide a particular feature; other information is optional.

Application and identity information

First and last name, email address, phone number, date of birth or age, gender, state, ZIP code, company name, company website, business stage, selected business or industry tags, interests, networking goals, monthly income range, optional personal social-media link, and your explanation of why you would be a good fit. We also keep submission dates, review status, review notes, approval or rejection decisions, and invitation records.

Account and profile information

Your member identifier, profile name, photo or initials, biography, businesses, role, age, general city, interests, industry tags, networking preferences, social links, profile edits, and account or membership status. We maintain password verification records rather than storing your readable password, along with login sessions and invitation or password-setup tokens.

Content and communications

Posts, titles, descriptions, photos you upload, comments, replies, reactions, direct messages, group-chat messages, sender and participant identifiers, timestamps, and related message or content metadata. Information you type or upload may include information about other people. Please share only information you are entitled to share.

Meetups, events, and relationships

Group assignments, matching results and explanations, joining history, group availability, proposed and agreed plans, event details, venue names and addresses, dates, times, timezones, RSVP and confirmation choices, follow relationships, connection records and counts, vacation-mode settings, attendance check-ins, and block relationships.

Billing and transaction information

Selected income-based membership tier, recurring rate, billing customer and subscription identifiers, checkout status, trial eligibility and extensions, payment and invoice status, renewal dates, cancellation instructions, and records of the price and terms you accepted. Our billing interfaces may display limited payment-method information, such as brand, last four digits, and expiry information, supplied by Stripe. Full payment credentials are entered into payment-provider fields, not a CoMinded profile field.

Support and safety information

Ticket or report category, your explanation, the account or content involved, contact details associated with your account, correspondence, investigation notes, and actions taken. Reports may contain information about both the reporter and the person reported.

Device, notification, and technical information

IP address and request information received by our servers and infrastructure providers; browser, operating-system or app information supplied with requests; session identifiers; app-installation identifiers; device platform; push-delivery tokens; notification preferences; delivery receipts; and operational error or security records. A push token identifies an app installation for delivery, not your phone number.

Information derived from these inputs

Approximate ZIP-based coordinates, a timezone, age derived from a birth date, profile similarities and match rankings, local content recommendations, membership tier and trial eligibility, and participation or connection inferences. These are service-generated estimates or records, not independently verified facts about you.

Marketing preferences and measurement

Email subscription choices, consent and withdrawal records, and suppression records used to honor those choices. When the marketing tools described in section 10 are enabled, they may also process browsing or campaign interactions, device/browser information, online identifiers, and email addresses or phone numbers used for audience matching. Actual collection depends on the tools enabled, their configuration, and applicable permissions and opt-outs.

3. Where information comes from

We collect information directly from you through forms, profile changes, uploads, messages, participation choices, and support requests. We also receive information through your use of the Services, from other members who communicate with or report you, from administrators reviewing applications or safety concerns, and from service providers that supply payment status, message delivery results, or ZIP-location information.

Providing a website or social-media URL does not connect your social-media account to CoMinded or authorize importing your contacts. Our team may review the link you submitted when considering your application. Following a link can disclose information to the destination website under its own practices.

4. How we use information

We use personal information for the following service and operational purposes:

Applications, accounts, and access

Review applications, manage waitlists and approvals, send invitations, authenticate members, maintain profiles, and determine access to membership features.

Local introductions and discovery

Recommend or assign groups, rank eligible late-join groups, personalize nearby posts and events, apply age and distance requirements, and help members find people with relevant interests and business context.

Community participation

Publish the content you choose to share, deliver conversations, coordinate meetup plans, manage event participation and group availability, and show follow and connection information.

Membership administration

Determine the rate associated with your income range, obtain price-change authorization, process subscriptions through Stripe, apply trials and qualifying extensions, reconcile payment status, manage cancellations, and address disputes or billing questions.

Communications and member controls

Send application, account, payment, group, message, plan, and safety communications; deliver notifications according to the available controls; and maintain vacation mode, block settings, and attendance check-ins.

Optional marketing and campaign measurement

Send promotional emails to people who opt in, maintain unsubscribe preferences, and, when the disclosed advertising integrations are enabled, understand campaign performance and reach relevant audiences, subject to applicable consent and opt-out requirements. An email subscription is not blanket permission for every advertising disclosure.

Safety, reliability, and compliance

Investigate reports, provide support, enforce community rules, prevent abuse or unauthorized access, troubleshoot failures, maintain records, measure service operation through administrative reporting, satisfy legal obligations, and establish or defend legal claims.

5. Location and device permissions

Local discovery uses the ZIP code and state you provide. We resolve a representative point for that ZIP code and derive a timezone from that geography. This is approximate area-level location, not a verified home address, live device location, or a driving-distance measurement. Members may see your general city or an event or meetup venue that you share. Your account ZIP and internal coordinates are not intended as member-facing profile fields.

The current local-matching features do not require GPS or background-location access. Choosing a venue or typing a street address into a plan can nevertheless disclose a specific place to its audience. Calendar exports and map links can also disclose that venue and schedule to the destination service you select.

When you upload a photo, the app uses the device photo picker and any platform permission needed to access your selection. We receive the selected file and associated upload information, not an intentional import of your entire library. Images and their metadata may reveal people, places, or other personal information; remove sensitive details before uploading.

Adding a meetup or event to a calendar is optional. Where required, the app requests calendar permission, lists available calendars on your device, and writes the event you select. It does not use your unrelated calendar entries for matching or upload your calendar history to CoMinded. An exported event can remain in your calendar after the CoMinded plan changes or your account is removed.

Phone push notifications are optional and use your operating system’s permission controls. You can change app notification preferences and lock-screen preview settings, or disable notifications in your device settings. The current app does not import your address book or require microphone access for its text-chat features. Denying an optional permission may prevent that feature without deleting your account.

6. Matching, income, and participation inferences

Our matching and ranking systems compare information such as approximate proximity, income range, age, interests, and industry tags. They also consider eligibility, available group capacity, blocking, vacation mode, and the context of a particular feature. These systems support networking recommendations; they do not verify a person’s income, background, character, or suitability for a business transaction.

Income range is used both as a compatibility signal and to select the applicable membership rate. Other members are not shown your private income-range field or individual billing records as part of a compatibility explanation. Information you voluntarily publish or discuss can still reveal your income. Match scores are presentation indicators, may use an adjusted display scale, and are not a probability of friendship, business success, or a guaranteed outcome.

Connection history can be derived from recorded meetup confirmations and event participation after a scheduled activity. Attendance-related automation can infer that you missed a meetup when no confirmation was recorded, then enable vacation mode and request a check-in. These records do not prove physical attendance, and we do not track your physical arrival. Use the check-in choices or contact support if the inference is wrong. Vacation mode pauses eligibility for new groups; it does not by itself cancel a paid membership.

You can correct available profile fields in Account, manage the available participation controls, or ask us to review an inaccurate account record or an automated result that concerns you. Recommendations may change with profile updates and eligibility. Existing group assignments are not necessarily changed by a later profile correction.

7. AI-assisted group planning

Where AI-assisted planning is enabled, we use OpenAI to help identify an agreed meetup location, date, and time from a group conversation. The planning request can include a limited recent portion of the group’s message text, message timestamps, sender names and member identifiers, participant names, the conversation title, match period, and the group timezone. The result can update the planning section and generate a plan notification.

Related group-description features can use selected profile context, including age, general city, business name, role or stage, industries, interests, and networking goals, to generate a group name, focus, agenda, or welcome message. Structured income, password, payment-credential, and ZIP-coordinate fields are not inputs to these AI prompts. However, an income figure, phone number, address, or other personal detail typed into a group message can be included as message text. Do not post confidential business information or another person’s sensitive information in a group chat.

Our current planning helper is for group conversations, not a feature that intentionally analyzes direct-message conversations for meetup planning. Message storage and necessary safety or support access are separate from AI processing. AI output may be inaccurate: review the plan and use the available manual correction controls or contact support. An AI-generated plan does not prove attendance or independently establish everyone’s consent to attend.

AI processing involves a third-party service rather than processing solely on your phone. OpenAI receives the inputs needed for the applicable request and processes them under the terms and data controls applicable to our use of its service. This policy does not promise zero provider retention or that all processing occurs in a particular country. Any legally or platform-required feature-specific disclosure and permission must be provided separately; merely viewing this policy is not that permission.

8. What other members can see

This is a social networking service. Other eligible members can see the profile and content fields exposed by the features you use, including your name, profile image, age, general city, business information, biography, interests, industry tags, social links, posts, comments, reactions, and hosted events. A “public profile” in the app means a member-facing profile, not a promise that every field is visible on the open internet. Visibility can depend on membership access, distance, age audience, block relationships, and participation rules.

Messages are available to the relevant conversation participants. A member joining an existing group can receive access to its earlier group-chat history. Group plans and confirmations are available to the group, and event hosts or eligible attendees may see participation information. Connection and follow counts can be member-facing even where the underlying lists are limited to the account owner.

Contact details and income stored in private account fields are distinct from information you intentionally put in a profile, event, photo, comment, or message. Reports are not published as community posts, but information may be reviewed by our team or used in an investigation. We cannot guarantee that someone will not infer who made a report from its circumstances.

Messages are not represented as end-to-end encrypted. CoMinded’s systems process and store them, and authorized personnel may access relevant information to operate the service, respond to support or safety issues, or meet legal obligations. Recipients can copy, screenshot, forward, or save content. Uploaded image delivery links and recipient-held copies may remain accessible outside a current in-app view. Blocking limits interactions supported by our systems; it cannot recall copies someone already obtained.

9. Service providers and other disclosures

Providing the Services requires disclosure to vendors that host data, deliver content and communications, process payments, or perform other service functions. They receive information relevant to their role. A provider may also have independent obligations or purposes, such as payment-fraud prevention. The principal provider categories and current integrations are described below.

We may also disclose relevant information when required by law or a valid legal process; to protect people, investigate abuse or fraud, enforce our terms, or establish or defend legal rights; with your direction or valid consent; or in connection with a proposed or completed financing, merger, acquisition, restructuring, or transfer of the business, subject to appropriate confidentiality and applicable legal requirements. We do not make member information available to every vendor merely because it is listed here.

Hosting and database infrastructure

We use privately managed hosting and infrastructure arrangements involving Bluehost and Microsoft. Hosting, database, backup, and network services process application and account records, community content, and operational data needed for their role. Our data systems use MongoDB. Private hosting does not mean information never reaches the service providers described here, and it is not a guarantee of a particular physical storage location.

Stripe and payment methods

Stripe processes checkout and subscription payments, billing contact information, payment credentials, and payment-related device or transaction information. Stripe may use cookies or similar technologies for checkout, wallet functionality, authentication, and fraud prevention. If you choose Link or an eligible digital wallet, that provider also processes information under its own terms. CoMinded receives the billing references and limited status or payment-method details needed to manage the membership, not your full card security code.

Cloudinary

Cloudinary receives and hosts selected uploaded photos and associated media metadata, and delivers images to people viewing them. Removing a content record in the app is not necessarily an immediate deletion of every hosted image or cached copy; see the retention section.

OpenAI

OpenAI processes the group-planning and group-description inputs described in the AI section. It is not the payment processor and is not supplied structured payment credentials for these features.

Expo, Apple, and Google

Expo’s push service, Apple Push Notification service, and Firebase Cloud Messaging support delivery to registered devices. Delivery involves tokens, routing data, and the notification payload, which can include a sender, message preview, or plan information depending on your settings. App-store and operating-system services also handle their own distribution, diagnostics, and permission functions.

Microsoft email services

Our transactional-email integration uses Microsoft Graph to send application-status and welcome messages. It processes recipient email addresses, message contents, and delivery-related records. Your own email provider also processes messages sent to you.

Marketing and analytics providers

Our website uses Meta Pixel tracking by default as described in section 10. Google Analytics and contact-list audience integrations remain planned. When enabled, advertising and analytics providers may receive the identifiers and activity data described in section 10. CoMinded plans to manage promotional email sending through its own setup rather than a separate email-marketing platform; hosting, delivery infrastructure, and recipients’ email providers still process the data needed to deliver email.

ZIP lookup and services you open

The ZIP lookup integration sends the ZIP code, rather than your complete application, to Zippopotam.us to resolve approximate geography. Calendar providers, map services, social-media sites, and other external destinations receive the information needed when you choose to open or export to them.

10. Local storage, cookies, and advertising

The app and related web experiences use storage and identifiers for essential functions such as keeping you signed in, restoring an authenticated session, remembering settings, and registering notifications. Native session credentials use device secure-storage facilities; web sessions can use browser storage. Clearing app or browser storage can sign you out or reset local preferences, but does not delete the records held on our servers.

The application form keeps unfinished answers in page memory while you move between its steps. Submitting sends the application to our service; refreshing the form can discard unfinished answers. Website, hosting, payment, and security services may separately receive technical request information and use technologies needed to operate their features.

Our website automatically uses Meta Pixel on the home, Privacy Policy, Terms, and application pages to measure visits, application openings, first interaction, steps reached and completed, and submission or validation outcomes. Progress events contain step numbers and a form version, not your answers or the text of errors. Meta can receive online identifiers, IP addresses, browser/device information, page URLs, and referring sources, and associate activity with information from other websites or its own services. Account, password recovery, billing, and application confirmation pages are excluded. Google Analytics and contact-list audience uploads remain planned integrations.

After an application with tracking metadata is successfully saved, we send a Lead event with normalized, SHA-256-hashed email and phone for matching. When our server connection is enabled, the Conversions API sends the same event with a shared event identifier to avoid double counting; it may include Meta browser/click identifiers and the browser user agent. This installation does not send names, birth date, gender, income, business details, interests, or free-text answers as matching or event parameters, and the application Lead itself does not report a payment or membership approval. Hashed contact information remains personal information used for matching. Server delivery records are saved with the application for reliable retries; temporary matching data is removed after successful delivery, a permanent failure, withdrawal, or expiry within 24 hours while the delivery worker is operating. Minimal tracking and delivery-status records may remain with the application.

When membership outcome measurement is enabled, applications submitted under this notice also support later server-side sharing with Meta of a confirmed approval and the first positive membership payment, including its actual amount and currency. Matching uses hashed email and phone and available, unexpired Meta browser or click identifiers. Free trials, free memberships and later renewals are not reported as new paid acquisitions. This sharing starts automatically for newly covered applications; an old application or prior Pixel choice alone does not authorize these expanded outcomes. You can turn future outcome sharing off in your website Account under Advertising measurement, or contact support before an account is available. The account choice does not change billing, promotional email preferences or the public-page Pixel. Outcome eligibility lasts at most 180 days unless you make a new choice; browser/click identifiers expire independently within 90 days. Temporary encrypted delivery data is removed on completion, terminal failure, withdrawal or expiry. Delivery may retry for up to seven days after an outcome, without changing its original date. Business application and payment records remain subject to their operational retention policy.

We may use email addresses and phone numbers supplied by applicants or members with advertising platforms for contact matching, campaign audiences, and related measurement, subject to applicable permissions, disclosures, and opt-out rights. A platform may match these identifiers with accounts it already holds. Hashing an identifier, when used, does not make this matching anonymous. This is different from merely buying advertising space without providing customer information.

We do not sell personal information for money. However, disclosure to advertising platforms may qualify as a “sale,” “sharing” for cross-context behavioral advertising, or processing for targeted advertising under applicable privacy laws even when no money changes hands. We therefore do not make an unqualified legal claim that marketing activity involves no sale or sharing. The classification depends on the actual integration and applicable law, and your applicable rights remain available.

CoMinded promotional emails are opt-in and will be sent through our own email setup. Applying, buying a membership, or receiving necessary account messages does not by itself subscribe you to promotional email. You may withdraw email-marketing permission using the unsubscribe instructions in a promotional message or by contacting [email protected]. Marketing emails must provide a working opt-out method. Necessary account, security, application, and billing messages may still be sent. This email preference is separate from any advertising-audience or cookie preference; opting into email does not automatically authorize promotional text messages.

To request that your information not be used for advertising audiences or legally defined sale, sharing, or targeted advertising, contact [email protected] and describe the choice you want to make. You do not need an active membership to contact us. Identify the email address or phone number involved without sending a password, identity document, or payment credentials. Advertising opt-outs do not require the same ownership verification as requests for access to private account records. You can also review privacy settings offered by your browser, device, and the advertising platform.

Meta Pixel tracking starts automatically on the public pages listed above, without an accept/reject prompt. Previous choices saved by the former website prompt and Global Privacy Control (GPC) do not disable this automatic integration. Browser or device blocking tools may still prevent Meta requests. We keep a random tracking identifier and timestamp in local storage when available, for up to 180 days; this record is not an affirmative consent choice. Meta browser and click identifiers may be stored in cookies for up to 90 days. For advertising privacy requests, including audience-use restrictions, contact [email protected] using the method above. Requests cannot undo information already sent. Planned advertising tools and contact-list uploads remain subject to applicable permissions and opt-outs. A material change in purposes or providers requires updated disclosures and any additional permission required by law or platform rules.

11. Sensitive information and children

Income information, authentication records, private communications, and some other information may be sensitive. Interests, messages, photos, or reports can also reveal religion, health, ethnicity, or other sensitive characteristics even where we do not ask for those details. Do not send us government identification numbers, full payment credentials, medical records, or other highly sensitive information through posts or ordinary support messages unless we specifically provide an appropriate, necessary process.

CoMinded is intended for adults aged 18 and older, not children. We collect birth-date or age information to assess eligibility and support age-relevant introductions; a focus on entrepreneurs in their 20s is a marketing focus, not an invitation for minors to join. We do not knowingly permit children under 18 to maintain member accounts. If you believe a child supplied personal information, contact us so we can investigate and address the account and associated information as required.

12. How long we keep information

We retain personal information for as long as reasonably necessary for the purposes explained in this policy, such as operating accounts and community features, reviewing applications, meeting legal obligations, maintaining security, and resolving disputes. We determine retention based on the type and sensitivity of the information, the status of the account or application, the ongoing purpose, and applicable legal requirements. There is no single fixed retention period for all information, and we have not implemented a comprehensive automatic deletion schedule for every category.

Our discretion is limited by those purposes and applicable law; it is not permission to retain everything indefinitely or disregard a valid deletion request. When information is no longer reasonably needed and no lawful retention exception applies, it should be deleted or appropriately de-identified. We may retain a limited record of an opt-out so that later marketing activity does not override your choice. The criteria below explain why particular records may remain, not a promise that all records are automatically erased after a set number of days.

Some technical records, such as expiring sessions and notification registrations, have system expiry mechanisms. That does not mean application records, messages, tickets, uploaded media, billing records, or the entire account are automatically deleted when those technical records expire. Signing out, uninstalling the app, cancelling a subscription, or turning on vacation mode does not itself delete your account.

Applications and review records

Used to complete review, communicate a decision, manage a waitlist or later application, and handle related safety or legal issues. Declined or abandoned applications are not automatically converted into public member profiles. You can request removal of an application through the privacy-request process.

Active account and community records

Kept to maintain the account, deliver conversations and community history, manage groups and events, and support the choices you make. Deletion requests require review of related records as well as the primary account document.

Billing, consent, safety, and legal records

Certain transaction, accepted-price, complaint, abuse-prevention, and legal records may need to remain after closure for accounting, dispute resolution, fraud prevention, enforcement, or compliance. Any exception to deletion should be limited to the information and duration needed for that purpose, rather than retaining the entire account indefinitely for convenience.

Media, logs, caches, and backups

Copies can remain in media hosting, delivery caches, operational logs, or backups until removed or overwritten under their lifecycle. Deleting a post from its app listing does not necessarily remove its Cloudinary asset. Include the relevant post or image in a deletion request if you want us to address the underlying media too. Copies saved by other members, in their calendars or email, or on independent services are outside our direct control.

13. Your controls and privacy requests

You can edit available profile and My Info fields in Account, manage membership through the Membership section, adjust phone-notification preferences, use available post or comment deletion controls, manage blocking, and turn vacation mode on or off. These controls have different effects: for example, cancelling billing does not erase messages, and blocking does not delete a previously submitted report.

You may contact us to request access to, a copy of, correction of, or deletion of your personal information or account, to withdraw an application, or to raise a concern about how we use your information. Depending on applicable law, you may also have rights to restrict processing, object to certain processing, withdraw consent, obtain portable data, or opt out of particular uses. Withdrawing consent does not make earlier lawful processing unlawful, and a feature may not be available without information necessary to provide it.

Use the privacy contact in section 18. Signed-in members can also use Account → Help, select Account & profile or Something else, and clearly describe the privacy request. For account deletion, identify the account email and state that you want the account and associated personal information deleted, not merely a subscription cancellation. For an application-only request, identify the application email. Do not include your password, full card number, or card security code.

For access, correction, or deletion requests, we may need to verify that you control the relevant account or are authorized to act for the person, and ask only for information reasonably necessary to do so. We evaluate requests under applicable law and explain any lawful limitation, necessary retention, verification problem, or available appeal process. A request concerning another member cannot be used to obtain that person’s private information. Advertising and email opt-outs are handled as described in section 10 rather than requiring unnecessary identity documents.

A CoMinded team member will provide an initial response within 48 hours of receiving a privacy request through Help or [email protected]. This does not mean verification, an investigation, account deletion, or all third-party processing will be completed within 48 hours. We complete requests within applicable legal deadlines and explain any permitted extension or limitation. An internal review does not suspend a legal deadline.

Self-service account deletion is available in Account → Settings → Delete your account, and from https://companyminded.com/delete-account without reinstalling the app. Confirm ownership with your current password and authorize permanent deletion. Once confirmed, account access ends, future Stripe subscription billing is stopped, and a retryable cleanup removes associated account data and identifiable media. The confirmation page shows progress and completion; keep that confirmation to check status after signing out. Cleanup usually finishes within 24 hours; contact support if it is still pending. Explicitly held safety/legal cases, payment-provider records, minimal deletion identifiers, and restricted backups or logs may remain under the retention criteria above. Deletion is not an automatic refund or a reversal of charges already processing. Requests through Help or email are reviewed by our team and do not instantly erase an account. Removing the app is not a deletion request.

14. Additional regional privacy information

Membership is offered only in supported U.S. locations. Privacy rights depend on where you live and whether a particular law applies to our activities. Nothing in this policy takes away a right granted by applicable law or asserts that CoMinded automatically meets every threshold of every state privacy statute. A U.S.-only service offering is not a promise that every service provider processes data only within the United States.

For California and other applicable U.S. state laws, the categories described in section 2 include identifiers and contact information; personal records such as age or birth date; commercial or subscription information; internet or application activity; approximate location; photos and message content; professional or business information; and inferences used for matching or participation. Some account credentials, communication content, or voluntarily supplied details may constitute sensitive personal information. Sections 3, 4, 8, 9, and 12 describe sources, purposes, recipient categories, and retention criteria. They apply to the information collected during the period in which we operate these Services, not an invented history of collection before launch.

Where the relevant state law applies, rights may include confirmation of processing, access or knowledge, correction, deletion, portability, limits on certain sensitive-data uses, and opt-outs of sale, targeted-advertising sharing, or certain legally defined profiling. A service recommendation is not automatically the same as a legally significant automated decision. Authorized agents may submit requests with appropriate authorization and identity verification. You may ask us to review a denied request or exercise any appeal right provided by applicable law. We will not unlawfully discriminate against you for exercising a privacy right.

If EEA, UK, or comparable privacy law applies to a particular interaction, the basis for necessary account and membership processing is generally performance of a contract or steps you request before a contract; safety, service reliability, and support may rely on legitimate interests where permitted and balanced against your rights; required recordkeeping relies on legal obligations; and optional processing that requires consent relies on that consent. You may have rights to object or complain to a competent supervisory authority. This paragraph does not mean that we currently market the Services in every such jurisdiction.

15. Security and international processing

We use account authentication, password verification safeguards, server-side access checks, protected service credentials, and other technical and organizational measures designed to protect personal information. Authorized administrative access supports application review, support, safety, and operations. No internet service, device, transmission, or storage method can be guaranteed completely secure. Keep your credentials and activation links private and contact us if you suspect unauthorized access.

The Services are operated for a U.S. launch, but infrastructure and service providers may process information in the United States and other countries where they operate. Those countries may have different data-protection laws. Where applicable law requires a transfer mechanism or additional safeguards, those requirements must be satisfied; this policy is not a claim that all data stays in Arizona, in the United States, or on your device.

16. Other websites and offline activities

Other members, hosts, venues, payment wallets, calendar providers, and websites you choose to visit operate independently unless we tell you otherwise. Their collection of information outside our Services is governed by their own notices and practices. Choosing a social link, directions link, calendar export, or payment method can transfer information to that destination.

An in-person meetup is not a confidential environment controlled by CoMinded. Other attendees may independently collect contact details or take photos. Consider what you share and obtain appropriate permission before posting someone else’s image or information. Report safety or privacy concerns through Help or the report controls; use emergency services for an immediate threat rather than relying on an app report.

17. Changes to this policy

We may update this policy when the Services, vendors, data practices, or legal requirements change. The version and updated or effective date identify the applicable notice. For material changes, we will provide additional notice and obtain additional consent where required by law or applicable platform rules. A policy update alone does not authorize a new use that requires separate permission.