This Privacy Policy explains how Misd collects, uses, shares, and retains information when you create an account, use our app, participate in social or location-aware features, communicate with other users, or contact us. It is meant to describe our data practices in a way that is legally meaningful without turning this document into a technical blueprint of our internal systems.
Information You Provide to Us
1. We may collect information you provide directly when you sign up, configure your account, join a waitlist, redeem access, update your profile, upload a profile image, contact support, submit a report, respond to a prompt, or otherwise use interactive features in Misd.
2. This may include information such as your name, username, date of birth, email address, password, profile details, profile image, invite or access details, waitlist details, communication preferences, deletion feedback, and privacy or Passport visibility settings.
3. Where a feature asks you to provide additional context, labels, text, media, or profile fields, we may collect the information you choose to submit as part of that feature.
A lot of the information in Misd starts with what a user chooses to type, upload, or turn on. We want that to feel understandable: most of this is about creating an account, setting up a profile, and using the features someone chooses to use.
Profile, Passport, and Account Information
1. We may collect and use account, profile, and Passport information so Misd can present your account, support discovery, personalize feature access, and operate social, map, and privacy-related functionality.
2. Depending on the choices you make, this may include display information such as your username, profile image, bio, link, approximate location, and profile or Passport fields you choose to provide, including fields relating to age, generation, gender, ethnicity, or identity.
3. Information you choose to display may become visible to other users consistent with your settings, feature design, relationship context, and the in-app surface where that information appears.
Misd works best when people can shape how they appear in the app, and that includes real control over what parts of a profile are shown. Some profile fields can feel sensitive, so we want to be upfront that those choices belong to the user and can affect what others see.
Posts, Messages, Comments, and Other Social Content
1. If you create, upload, send, receive, share, save, or interact with content in Misd, we may process the text, images, video, links, reactions, comments, direct messages, shares, and related metadata needed to operate those features.
2. We may also process records about when content is viewed, opened, delivered, reported, moderated, or otherwise acted on inside the service.
3. Content and communication records may be used to provide the service, support social features, enable delivery and display, investigate abuse, enforce policies, troubleshoot product issues, and maintain safety and system integrity.
When someone posts, comments, or messages through Misd, the app has to handle that content so the feature can actually work. We also need room to respond if content is reported, unsafe, or clearly being misused.
Location, Moments, and Place-Related Information
1. If you use location-aware features, we may process location-related inputs, place labels, movement or visit context, privacy settings, and related metadata needed to operate map, Moments, connection, ranking, and safety-oriented features.
2. Some features may require more detailed place or device-location information to be handled during setup, feature processing, or integrity review than is later shown in ordinary user-facing product surfaces.
3. We may also process approximate-location signals, location-derived summaries, hidden-place settings, and related records so the service can balance feature utility with privacy and safety goals.
Location is one of the most sensitive parts of Misd, so this section is intentionally careful. Some features need place information to work, but the user-facing version of that information can be more limited than what the app briefly needs behind the scenes to operate safely.
Privacy, Hidden Places, and Visibility Controls
1. Misd may let users mark certain places, profile elements, or account surfaces as private, hidden, reduced, or otherwise limited in visibility.
2. We may store the settings and supporting records necessary to apply those privacy choices, detect conflicts, preserve account integrity, and operate the related product logic.
3. These controls are designed to reduce unnecessary exposure of sensitive places and account information, but the specific methods used to do so may change over time as the product, infrastructure, safety practices, and legal requirements evolve.
Private-place features exist because some information deserves extra care. We want the policy to say that plainly without pretending any product can promise perfect invisibility in every situation.
Setup, Permissions, Device, and Technical Information
1. We may collect information about the setup steps you complete and the permissions you grant, deny, or later change, including permissions related to notifications, camera access, photo-library access, Bluetooth-related capabilities, and location-related features.
2. We may also receive technical information necessary to operate these features, such as device tokens, account-linked device identifiers, app state information, session data, settings state, and similar records associated with app operation and communications.
3. We may locally cache certain content, preferences, or feature state on your device to support performance, continuity, safety, or user experience, subject to the controls available through the app, your device, or account lifecycle flows.
Phones keep track of what an app is allowed to do, and Misd has to respond to that. Some technical data also helps with basics like remembering settings, sending notifications, and keeping the app from feeling broken every time it opens.
How We Use Your Information
1. We may use information we collect to create and maintain accounts, authenticate users, process access or waitlist flows, verify eligibility, operate app features, and support user-requested functionality.
2. We may also use information to personalize the app experience, support profile, messaging, map, Moments, ranking, connection, and content-sharing features, maintain security, detect fraud or misuse, troubleshoot issues, improve the product, and comply with legal obligations.
3. Where permitted, we may use information to measure product performance, understand feature adoption, evaluate what is working, inform product decisions, and support safety, operational, and service-improvement work.
Most data use in Misd is practical: making the account work, making the app useful, and making the product better over time. We want the service to feel personal and alive without making the policy sound more mysterious than the product really is.
Karma, Clout, Rankings, and Inferred Interests
1. Misd may create, display, or use activity-based scores, summaries, rankings, badges, categories, or similar feature signals derived from account activity, content interactions, connection behavior, or feature participation.
2. We may also generate or use inferred preference, interest, or relevance signals to support profile presentation, ranking, discovery, or other product functionality.
3. These signals may be visible to you, other users, or internal reviewers depending on feature design, account settings, moderation needs, and the context of the surface where they appear.
Some parts of Misd summarize activity so the app can show momentum, reputation, or interests in a lightweight way. That is meant to help the product feel social and dynamic, not to quietly build a hidden dossier on people.
Safety, Reporting, Blocking, and Enforcement
1. We may collect and use reports, moderation inputs, block lists, ignore lists, enforcement records, and related account or content information to investigate complaints, protect users, and enforce our rules.
2. Safety-related records may include the reporting user, the reported user or content, the reason submitted, supporting details, account relationships, and other context reasonably necessary to review a concern.
3. We may retain, review, disclose, or act on this information where reasonably necessary for safety, abuse prevention, legal compliance, dispute resolution, or the integrity of the service.
Safety tools only work if the app can remember what was reported and act on it. We want users to know that reports, blocks, and similar actions are treated as part of protecting the community, not as throwaway buttons.
Communications and Notifications
1. We may use your contact information and device-related messaging information to send verification messages, onboarding notices, account or security alerts, support responses, invite or waitlist communications, and service notifications.
2. We may also use communication preferences, notification settings, message-delivery records, and related technical data to deliver the types of notifications or service messages you enable or expect from the app.
3. Some messages are necessary to operate the service or secure your account, even if optional promotional or marketing communications are limited or not currently active.
Some messages are just part of keeping the app useful and your account secure. Verification codes, important notices, and the notifications someone asks to receive are different from spam, and we want that difference to stay clear.
How Information May Be Visible to Other Users
1. Depending on the feature, certain information may be visible to other users, including profile details, content you post, comments, messages sent to recipients, shared links, ranking or activity surfaces, approximate place context, and other information you choose to make available through the service.
2. Visibility may depend on your privacy settings, account relationships, feature-specific rules, moderation action, and the surface where the information appears.
3. Information disclosed to other users may be copied, saved, reshared, or acted on by recipients or viewers, subject to the limits of the service and applicable law.
Social apps work because people can see and respond to each other, but visibility is not the same on every screen. We want users to understand that settings matter, context matters, and anything shared with another person can travel farther than intended.
Sharing and Disclosure
1. We do not describe Misd as selling personal information in the ordinary course of operating the current service.
2. We may share information with service providers, infrastructure vendors, cloud-storage providers, communications vendors, analytics or security vendors, platform partners, and similar processors where reasonably necessary to run, support, protect, or improve Misd.
3. We may also disclose information where required by law, legal process, safety concerns, contractual enforcement needs, fraud or abuse investigations, or transactions involving a merger, acquisition, financing, reorganization, or sale of assets.
Running an app still means working with vendors for things like storage, email, infrastructure, and safety. We want to be clear that there is a difference between using vendors to operate the product and casually handing user data around.
Advertising, Analytics, and Tracking Context
1. Misd does not currently present itself as a heavily ad-driven consumer experience inside the app, and our present-tense disclosures should be read in that context.
2. We may still use information for analytics, product measurement, abuse prevention, service integrity, and similar internal purposes consistent with this policy and applicable platform disclosures.
3. Misd does not currently track users across third-party apps, websites, or services for advertising or advertising measurement. If that changes in a material way, we may update this policy, in-app notices, and any required platform disclosures accordingly.
Right now, the positive thing worth saying is that Misd is not built around a heavy ad model. If that changes in a meaningful way, the right move is to say so clearly instead of quietly stretching old language to cover something new.
Retention and Account Lifecycle
1. We retain information for as long as reasonably necessary to provide the service, maintain security, support legitimate business operations, comply with law, resolve disputes, and enforce our agreements.
2. Different categories of information may be retained for different periods depending on the nature of the feature, the sensitivity of the data, operational need, safety considerations, restoration windows, and legal requirements.
3. If you request account deletion or similar account-lifecycle changes, some information may remain temporarily or in limited form where reasonably necessary to process the request, support restoration windows, preserve safety records, comply with law, or protect the integrity of the service.
Not everything needs to be kept forever, and not everything can disappear instantly the moment someone taps delete. Retention is mostly about balancing user expectations with safety, security, support, and the practical realities of running the service responsibly.
Your Choices and Rights
1. You may be able to access, update, or change certain account, profile, privacy, Passport, messaging, and communication settings directly in the app.
2. You may also control certain permissions through your device settings, including notification, location, camera, photo-library, and Bluetooth-related permissions where applicable.
3. Depending on where you live, you may have additional rights regarding access, correction, deletion, portability, restriction, or objection with respect to certain personal information, subject to applicable law and available verification procedures.
People should be able to manage a real amount of their own data and settings without having to email support for every small change. We want the controls to feel practical, and if local law gives someone additional rights, we want room to honor that too.
Children and Age-Related Information
1. Misd is not intended for anyone under 17, or anyone who does not meet the higher minimum age required by applicable law.
2. We may collect age-related information, including date of birth or age-gating information, to support eligibility checks, safety controls, feature design, and legal compliance.
3. If we learn that information was collected in a way that is inconsistent with applicable age-related requirements, we may take appropriate remedial action, including restricting or deleting accounts where appropriate.
Age checks are there because some responsibilities come with running a social app, not because we want to collect extra personal information for its own sake. This is one of the places where legal compliance and user safety overlap directly.
Changes to This Policy
1. We may update this Privacy Policy from time to time to reflect changes in Misd, our practices, legal requirements, platform requirements, or business operations.
2. Where required, we may provide additional notice or request renewed acknowledgment for material changes.
3. Your continued use of Misd after an updated policy becomes effective means the new policy will govern to the extent permitted by law.
Privacy policies should evolve when the product evolves. If something important changes, the right move is to update the document and the platform disclosures instead of quietly hoping no one notices.
Contact
1. Questions or requests relating to this Privacy Policy may be directed through the support methods provided in the app or through the support contact information associated with Misd.
2. If we need to respond to a privacy request or account-related issue, we may use the contact information associated with your account to do so.
If someone has a privacy question, there should be a real path to ask it. A policy should help people understand the product, not make them feel like there is nowhere to go when something matters.