1. Who is responsible
MORVAIYN is responsible for the processing described in this policy. Privacy and support requests can be sent to help@morvaiyn.com.
2. Data we process
Depending on the features you use, we may process:
- Account and identity data, including email address, username, authentication identifiers, declared age range and profile information.
- User content, including plans, Moments, messages, reports, profile media and other content you choose to submit.
- Participation and trust data, including reservations, attendance, dynamic QR check-ins, reliability signals, blocks, reports and moderation outcomes.
- Approximate or precise device location when you grant permission for nearby discovery or check-in. Your profile location is not published as your public profile location.
- Device, security and diagnostic data, including IP address, device identifiers, push tokens, logs, crash information and anti-abuse signals.
- Transaction and balance records needed for deposits, refunds, gifts, competition features, payouts or legal and accounting obligations. Full payment-card details are handled by the applicable payment provider rather than stored by MORVAIYN.
3. Why we use data
We use personal data to create and secure accounts; show relevant nearby plans; enable plan creation, reservations, chat and check-in; operate deposits and transaction records; prevent fraud and overlapping reservations; moderate content; investigate reports; provide support; improve reliability and performance; comply with law; and protect users and the service.
The legal basis may be performance of our contract, your consent, compliance with legal obligations, or our legitimate interests in providing a safe and reliable service. You may withdraw consent for optional processing through device or account settings, without affecting prior lawful processing.
5. Location, nearby discovery and check-in
Location is used only when needed for features such as nearby discovery and attendance verification. Permission can be managed in your device settings. A check-in may confirm that you were at the plan location at the relevant time, but the raw location is not displayed as your public profile location.
6. Age, groups and safety
MORVAIYN uses declared age information and server-side rules to separate age groups and restrict access to plans where required. Do not misrepresent your age. Parents or guardians may contact us about a minor's data. The service is not directed to children under 13.
7. Retention
We keep information only for as long as needed for the purposes above. Active-account data is generally retained while the account remains open. After deletion, live account data is removed or anonymised, while backups may take up to 90 days to be overwritten. Security, fraud-prevention, dispute, legal and accounting records may be retained for up to six years or longer when law requires it.
8. Security and international transfers
We use encrypted transport, access controls, authentication safeguards, logging and service isolation designed to protect data. No system can guarantee absolute security. Where data is processed outside your country, we use an applicable legal transfer mechanism and contractual safeguards.
9. Your choices and rights
Depending on your location, you may request access, correction, deletion, restriction, objection, portability or withdrawal of consent. You may also complain to your local data-protection authority. We may need to verify your identity before completing a request.
Contact help@morvaiyn.com from the email linked to your account. Do not send passwords or security codes.
10. Delete your account
You can start permanent deletion through the MORVAIYN account deletion page. If you signed up with Google or cannot authenticate with a password, request deletion from the registered email address. Deletion is permanent, subject only to limited legal or safety retention described above.
11. Changes to this policy
We may update this policy as the service changes. Material changes will be communicated through the app, website or registered email where appropriate. The effective date at the top identifies the current version.