Privacy Policy

Version 1.0-draft — This is an AI-assisted draft prepared for Owner and lawyer review. It is not legally binding until approved and published for production.

Introduction

Welcome to the Privacy Policy for I Am Musician ("IMM", "we", "us"). We provide a mobile and web platform where musicians, bands, organizations, and music enthusiasts connect, collaborate, and grow together.

Imagine You have just signed up to find a drummer in Your city. Or maybe You are browsing rehearsal rooms as a guest. Either way, You deserve to know exactly what happens with Your information. This Policy explains what personal data we collect, why we need it, and what choices You have — in plain language.

The identity of the data controller and contact details will appear in the Imprint once filled by the Owner.

Definitions

To keep things clear:

Application / Service: the IMM mobile app and web platform, including all feeds, messaging, profiles, and related features.
Personal Data: any information that identifies You or can be used to identify You (name, email, location, etc.).
You / Your: the person using IMM — whether as a registered user or a guest.
device_id: a random identifier generated and stored locally on Your device. It is not a government ID, not linked to Your real identity, and not used for continuous tracking.
Consent record: a timestamped entry showing which Privacy/Terms versions You accepted, when, and in what context.

What We Collect

When You create a profile, post "Na Dushe", or book a rehearsal room, here is what we may process:

Account data: email address, display name, password hash or social login identifiers, language preference, and verification status.
Profile and content: Your musician/band/organization profiles, specializations (guitar, vocals, sound engineering...), portfolio media, posts, comments, classifieds, collaboration content, and messages You send to other users.
Location (optional): the city or coordinates You choose so nearby feeds can show relevant results. We do not run continuous background GPS tracking.
Device identifier: a locally generated device_id used for guest flows — consent audit trails, guest data deletion, and limited anonymous features. Think of it as a local bookmark, not a tracking beacon.
Technical logs: IP address, app/site version, approximate timestamps, and security-related events. These help us prevent abuse and keep the platform reliable.
Consent records: which Privacy/Terms versions You accepted, when, and for which context (account registration or a guest form).

Information You Choose to Share

IMM is built around community — but You control what is public:

Required for account: email and a display name so others can find and message You.
Optional profile fields: specializations, bio, portfolio, city, contact details. You decide which to fill.
Public by design: posts in feeds, published profiles, and band pages are visible to other users (and potentially guests). If You do not want something public, do not post it in a public feed.
Private: direct messages are between You and the recipient. We do not display them in feeds or share them with third parties (except where legally required).

Why We Process Data

Every piece of data we collect has a specific purpose:

To create and secure Your account so only You can access it.
To show relevant feeds and map results — like musicians near Your city who play bass.
To enable messaging, band memberships, and rehearsal bookings between real people.
To enforce Community Guidelines and keep IMM safe from spam and abuse.
To respond to Your Support requests.
To comply with applicable law (for example, retaining consent records).
To improve reliability and product quality through aggregated, non-identifying analytics.

Legal Bases (Where GDPR or Similar Laws Apply)

Contract: providing the service You request when You sign up — Your account, messaging, bookings, and collaboration features.
Legitimate interests: security, fraud prevention, product improvement, and aggregated analytics that do not replace consent where consent is legally required.
Consent: where required — for example, certain guest forms that collect Your name or email, or optional marketing communications (not enabled in this draft unless separately configured).
Legal obligation: when applicable law requires us to retain or disclose data (e.g. court orders, tax regulations).

Sharing

We do not sell Your personal data. Period. We may share data with:

Processors under strict contracts — hosting providers, email delivery, push notification services, and map providers who process data on our instructions and cannot use it for their own purposes.
Other users — only the fields You publish as public profile content, posts, or band pages.
Authorities — when required by law or to protect rights, safety, or the integrity of the service (e.g. responding to a valid legal request).

International Transfers

Our infrastructure may be located outside Your country. Where required, we use appropriate safeguards — for example, EU standard contractual clauses. Specific details for production will be confirmed by the Owner and lawyer.

Retention and Deletion

You are in control:

Delete Your account: go to Settings in the app. Your profile, posts, and messages will be removed or anonymized according to the product deletion flow.
Delete guest data: Settings → "Delete my data" removes data linked to Your device_id.
Backups: operational copies expire on a rolling schedule after deletion.
What we may keep longer: consent audit rows and certain security logs — for legal compliance and dispute resolution only.

Your Rights

Depending on Your region, You may have the right to:

Access the personal data we hold about You.
Correct inaccurate information.
Request deletion ("right to be forgotten").
Restrict or object to certain processing.
Receive Your data in a portable format.
Withdraw consent where processing is consent-based (without affecting prior lawful processing).

To exercise these rights, contact us via the in-app Support form or the address listed in the Imprint. You may also lodge a complaint with Your local supervisory authority.

Security

We use industry-standard measures appropriate to a community platform: HTTPS everywhere, access controls, hashed passwords, and regular security reviews. No method is 100% secure — please use a strong, unique password and protect Your device.

Children

IMM is not directed at children under 16 (or a higher age if required by local law). If You are below the applicable age, please do not register or submit personal data.

Changes to This Policy

We may update this Policy as the product evolves or laws change. Material changes will bump the version string visible in IMM Settings and may trigger in-app re-consent before You can continue using account features. We will not silently reduce Your rights.