Privacy Policy - Oameni

Last updated: 18 September 2026

This Privacy Policy explains how RedShift IT S.R.L. processes personal data when you use the Oameni website, backend services and mobile application (the "Platform"). It is intended to provide the information required by the GDPR, Romanian data protection law and applicable EU rules in clear language.

Account and data deletion: you can initiate deletion in Account using “Delete account”, or externally through [email protected] with the subject “Oameni account deletion request”. Section 17 below explains the restore period, legally retained data and withdrawal of consent.

1. Controller

The controller is RedShift IT S.R.L., registered office Romania, Bucharest, Str. Piscului no. 14, Bl. 47, Sc. A, Ap. 1, Sector 4, Trade Registry no. J40/5296/21.05.2010, tax identification code RO26963888, VAT payer.

Contact for privacy requests: [email protected]. Please include "Privacy request" in the subject where possible.

We have not appointed a formal Data Protection Officer where not legally required, but privacy requests are handled through the contact above.

2. Roles of Oameni and Organizers

For core Platform operation, account management, security, billing and Platform-level moderation, RedShift IT S.R.L. acts as controller. For data used by an organizer to manage a specific community, event, attendee list, community subscription, custom question, email campaign or local event decision, the organizer may act as an independent controller or, depending on context, receive data from Oameni for the event/community purpose. Organizers must process participant data lawfully and only for the relevant purpose.

3. Data We Process

Account and identity data: name, email, password hash, language, role, account status, terms acceptance, restore tokens and account deletion status.

Profile data: phone, avatar, gender, date of birth, social profile links, notification preferences, privacy settings and profile visibility choices.

Authentication data: login history, password reset tokens, social login identifiers, Apple/Google/Facebook data where enabled, passkey/WebAuthn public credential data and security metadata.

Community data: memberships, roles, join answers, invitations, ratings, notes, suspensions, pages, announcements, galleries, albums, polls, membership passes, subscription status and moderation history.

Event data: registrations, attendee status, guest data, custom answers, special codes, vouchers, waitlist records, arrival time, ticket codes, check-in status, wallet pass data and post-event communications.

Messages and social features: event chat, community chat, direct messages, connection requests, blocks, mutes, reports and related notification metadata.

Payment and billing data: billing name, address, country, VAT/CUI, company data, invoices, payment records, Stripe identifiers, Apple/Google IAP transaction data, subscription records, refunds, payout records and fiscal metadata. We do not store full card numbers.

Device and technical data: IP address, browser, device type, operating system, app version, logs, security events, CSRF/rate-limit metadata, cookies, local storage identifiers, push tokens, web push subscriptions, crash or diagnostic signals where available.

Analytics data: usage events, page views, feature interactions, approximate country and aggregated statistics collected through configured analytics tools such as Google Analytics/Google Tag Manager where enabled and allowed.

Support and legal data: emails, reports, appeal messages, evidence, correspondence and records needed to answer requests or defend legal claims.

4. Purposes and Legal Bases

Account creation, login, profile management and terms acceptance: contract performance and legitimate interest in account security.

Event registration, tickets, memberships, communities, chat, wallet passes and notifications: contract performance and legitimate interest in operating the Platform.

Payments, subscriptions, invoices, refunds, VAT, payouts and accounting: contract performance and legal obligations under fiscal/accounting rules.

Organizer administration and participant selection: contract performance, organizer legitimate interests and, where needed, user consent or explicit user action.

Safety, reporting, moderation, blocking, fraud prevention, rate limiting and abuse detection: legitimate interest, legal obligations and protection of users.

Transactional emails, push notifications and service alerts: contract performance and legitimate interest. Optional notification preferences can be changed in account settings where available.

Marketing or non-essential communications: consent or legitimate interest where allowed by law, with opt-out options.

Analytics, cookies and product improvement: consent where required by law, or legitimate interest for strictly necessary or privacy-preserving operational analytics.

Legal requests, consumer protection, DSA notices, disputes and compliance: legal obligation and legitimate interest.

Sharing transaction usage details with Apple after you request a refund directly from Apple, to help Apple evaluate that request: your explicit, specific consent (“Share purchase activity with Apple to help resolve refund requests” toggle in Account settings), revocable at any time. Withdrawing does not affect information already shared before you withdrew.

5. Who Can Receive Data

Depending on the feature, data may be received by: Oameni staff and authorized contractors; community admins and event organizers; payment providers such as Stripe, Apple and Google; invoicing providers such as Oblio; hosting, database, storage and CDN providers; email, SMS/WhatsApp or push notification providers; analytics providers; maps providers; fraud/security providers; professional advisers; banks; public authorities; courts; or other users when you intentionally publish or send content.

Organizers may see attendee lists, answers, billing-relevant details, guest data, membership information, check-in status and messages needed to administer their event or community. Community admins may see reports and moderation data for their community.

Where you have accepted the “Advertising measurement” category, the data described in section 16 may also be received by the advertising platforms we or the community you are visiting have actually connected: Meta (Facebook and Instagram), Google (Google Ads and Google Analytics 4) and TikTok. Without that consent nothing is sent to them.

6. International Transfers

Some providers may process data outside Romania or the European Economic Area. Where this happens, we rely on adequacy decisions, Standard Contractual Clauses, provider transfer safeguards or other mechanisms allowed by GDPR.

The advertising platforms named in section 16 — Meta, Google and TikTok — process data in the United States. Those transfers rely on Standard Contractual Clauses and on the EU–US adequacy framework where the provider is certified under it.

7. Retention

Account data is kept while the account is active and then deleted or anonymized after the applicable restore grace period, unless longer retention is required.

Deleted accounts may be restorable for up to 30 days where the Platform offers restore functionality.

Invoices, payments, VAT, accounting and fiscal records are retained for the period required by Romanian tax and accounting law (currently 10 years, under Accounting Law no. 82/1991).

Security logs, rate-limit records and technical logs are retained for a limited period needed for security, debugging and abuse prevention.

Chat, direct messages, reports, moderation decisions and evidence may be retained while relevant to account safety, disputes, legal obligations or community integrity.

Event attendee data is retained as long as needed for event administration, tickets, disputes, invoices, legal claims and organizer records.

Push tokens and web push subscriptions are kept until revoked, invalidated, account deletion or inactivity cleanup.

Analytics data may be retained according to provider settings and is preferably aggregated where possible.

Visits recorded for advertising measurement lose their technical context (IP address, user agent, page address, referrer, device type and click identifiers) after 30 days, and are deleted entirely after 395 days. The receipt recording your consent choice is valid for 395 days.

Where exact deletion is not possible because data is part of backups, logs or legal records, we restrict further processing and delete according to backup rotation or legal retention schedules.

8. Your Rights

Under GDPR you may have the right to access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and the right not to be subject to decisions based solely on automated processing with legal or similarly significant effects. You also have the right to lodge a complaint with the Romanian supervisory authority, Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP), or another competent EU authority.

To exercise rights, contact [email protected]. We may need to verify your identity before acting on a request. Some requests may be limited where retention is required by law, where data belongs to another person, or where we need data for legal claims, security or fraud prevention.

9. Automated Decisions and Profiling

The Platform may use rules and settings to show events, apply access gates, detect abuse, apply waitlist/capacity rules, hide reported content pending review, calculate ratings, badges or community statistics, and route notifications. These are used to operate the Platform and support moderation; they are not intended to produce solely automated legal decisions about you. Human review is available for relevant moderation or restriction decisions by contacting us.

10. Cookies, Analytics and Similar Technologies

We use necessary cookies, local storage and similar technologies for login, security, language, preferences and core app operation. Where enabled, analytics tools such as Google Analytics and Google Tag Manager may help us understand usage and improve the Platform. Non-essential cookies or analytics are used according to applicable consent requirements and browser/device settings. You can limit cookies through your browser, but some features may stop working.

The “Privacy settings” window asks about three categories: strictly necessary cookies, which are always on because the app cannot work without them; analytics; and advertising measurement. We do not ask about each provider separately — one choice covers the whole category, and the providers we use are listed in section 16. You can change or withdraw your choice at any time in the same window.

11. Push Notifications, Email and Device Tokens

If you enable push or web push notifications, we process device or browser tokens and notification metadata to deliver account, event, chat, payment, ticket and community notifications. You can revoke notification permissions in your device/browser settings or account settings where available. Some transactional emails, such as security, password, ticket, invoice or account notices, may still be sent where necessary for the service or legal compliance.

12. Children

The minimum age to use the Platform is the age shown in the app store listing for your region (currently 16 in most countries, 15 in Brazil and South Korea), or the minimum legal age required in your jurisdiction if higher. We do not knowingly allow anyone under this age to create accounts. If you believe a minor has provided data without meeting the applicable minimum age, contact us so we can review and take appropriate action.

13. Security

We use technical and organizational measures such as access controls, authentication, rate limiting, CSRF protections, encryption where appropriate, backups, logging and provider security controls. No system is perfectly secure. Please report suspected security issues to [email protected].

14. Data From Third Parties

We may receive data from payment providers, app stores, social login providers, organizers, invite senders, guests, report submitters, public authorities or other users. We process it only for the purposes described here and according to applicable law.

15. Changes

We may update this Policy. Material changes may be highlighted in the app, by email or through renewed consent/acceptance where required. The current version is published on oameni.org.

16. How We Collect Data and Additional Provider Disclosures

We collect data directly from you when you create or manage an account, complete a profile, register for an event, make a payment, contact us, or upload content; automatically when you use the Platform, through cookies, local storage, logs, push tokens and technical device data; and from third parties when you choose social sign-in, payment or communication services, or when an organizer or another user provides data needed for an invitation, event or community.

Apple, Google, Facebook and Instagram Sign-In

If you choose sign-in through Apple, Google, Facebook or Instagram, we receive and use only data made available for authentication and account creation/linking: the provider identifier, name, email address, profile photo and/or profile link, where supplied by the service and authorized by you. For Sign in with Apple, the email address may be an Apple private relay address. We do not retrieve, store or use birthday or gender through Facebook Login.

WhatsApp and Communications

If you or the relevant organizer use WhatsApp functionality, we may process phone number, contact name, message content, message variables, message identifiers, sent/delivered/read/failed statuses, and technical identifiers of the connected WhatsApp Business account. This data is transmitted to Meta/WhatsApp to provide the communication. Organizer-initiated communications must have the legal basis and consent/opt-in required by law and WhatsApp rules. You can stop messages from a community by replying STOP; replying START may reactivate communications for that community.

Payments and Stripe Connect

Payments and Stripe Connect account onboarding may involve transmitting billing data, transaction data, payment identifiers, entity-verification data and IBAN/payout data to Stripe where required by Stripe. Stripe processes that data under the Stripe Privacy Policy. We do not store full card numbers.

Analytics and Push Notifications

Where enabled and permitted, Google Analytics/Google Tag Manager may receive usage, page-view and interaction data. For push notifications, we may use Firebase Cloud Messaging and/or operating-system notification services for device/browser tokens and metadata needed for delivery. Non-essential cookies or analytics are used only in accordance with applicable consent requirements.

We share data with providers acting for us only when necessary and, where applicable, contractually require them to protect data to at least an equivalent standard to that described in this Policy and required by law. Organizers, Stripe, Apple, Google, Meta and other recipients acting as independent controllers may have their own duties and policies; our Terms require them to process data lawfully and for the relevant purpose.

Advertising Measurement

If you accept the “Advertising measurement” category, we may send conversion events to the advertising platforms we or the community you are visiting have actually connected and switched on: Meta through the Conversions API, covering Facebook and Instagram; Google Ads; TikTok through the Events API; and Google Analytics 4 through the Measurement Protocol. Nothing is sent to a platform that is not connected, whatever your consent says.

We send a pseudonymous identifier derived by hashing your internal identifier; the event type, such as an event registration or a purchase; the value and currency; and the click identifier from the ad link you arrived through — fbclid, fbp and fbc for Meta, gclid, gbraid and wbraid for Google Ads, ttclid for TikTok — which we store encrypted. To Meta and TikTok we additionally send the IP address, the browser user agent and the address of the page visited, because those platforms require them for web events. We do not send your email address, phone number or name to any of them.

We signal to these platforms that the data may be used for measurement but not for ad personalisation: our consent window neither asks for nor grants personalisation.

Your choice is recorded separately for the Oameni platform and for each community. When a community connects its own advertising accounts, it decides what is measured for its own events and answers for that choice.

You can change your mind at any time in “Privacy settings”, including withdrawing consent entirely. Withdrawal stops the collection and sending of new data; it cannot recall what was already sent before it. Retention periods are in section 7.

17. Account Deletion, Data Deletion and Withdrawal of Consent

You can initiate account deletion in the app or website, in Account, by using the “Delete account” option. For an external request, including after uninstalling the app, email [email protected] with the subject “Oameni account deletion request”, from the email address associated with the account or with enough information for us to verify your identity. This page is Oameni’s public web resource for account and data-deletion requests.

Your account is moved to a restore period of up to 30 days, during which it may be restored through the emailed link where that function is available. After that period, we delete or anonymize data associated with the account, including data processed through providers where necessary and possible. We may retain data strictly necessary for invoices, accounting, tax obligations, fraud prevention, security, dispute resolution, backups and other legal obligations, in line with the retention periods described in this Policy.

You can withdraw consent for non-essential cookies/analytics through the available preference mechanism or browser settings; for push notifications through device/browser settings; and for optional communications through account settings or the applicable unsubscribe mechanism. Withdrawal does not affect the lawfulness of prior processing and does not stop transactional communications or processing necessary for the service, security or legal obligations.