Your space. Clearly explained.
Your data, explained.
Privacy information for the Moylo website and iOS and Android apps.
Who is responsible?
Diego Rodriguez, trading as Rodriguez Web, Delftstraße 8, 27474 Cuxhaven, Germany, is the controller. Contact diego@rodriguez-web.de for any privacy question.
Your account and your space
We process your email address, account identifier and authentication information to register you and keep you signed in. With Google sign-in, Google also provides your account identifier and basic account information such as your name and profile image. You choose your Moylo handle and display name during onboarding.
The iOS app also offers Sign in with Apple. Apple provides a provider-specific account identifier and, when you authorize sharing them, your name and email address. If you choose Hide My Email, we receive Apple’s relay address instead of your personal address. Sign-in credentials are exchanged with Firebase Authentication; they are not published on your profile or included in content reports.
When you create your Moylo profile, we privately record the version of the community guidelines you accepted and the time of acceptance. This record is not part of your public profile.
We store your profile, uploaded images, post titles, descriptions, alt text, tags, comments, likes, follows and saved posts to provide the features you choose to use. A server timestamp keeps each feed refresh consistent while more posts load. Earlier feed-completion timestamps may remain on existing accounts; the web Home feed does not use them to hide older posts. A lowercase copy of your display name makes people search work.
You may optionally choose up to five interests. These choices and the completion of the discovery steps are stored privately. You can change your choices in Settings. For you uses the people you follow, your chosen interests, tags from your 24 most recently saved posts and the age of public posts to order recommendations. It also varies the people shown together. Your follows, interests and recently saved posts help shape recommendations and update them when they change. We do not record viewing time or scrolling behavior for this ranking. Recommendation labels explain a main reason for each post. Following shows posts from the people you follow, newest first.
Account and social features are provided under Article 6(1)(b) GDPR. Optional profile details are not required to use the core service. Without authentication details, we cannot create your account.
What is public, and what is private?
Your profile, bio, website and posts are public, including to visitors and search engines. Likes and comments can be read by signed-in users. Follower lists are visible to signed-in users; your following list, saved posts and activity are available to you.
Story records are available to signed-in users. Uploaded images use shareable download URLs: someone who receives an image URL can view it. Do not upload confidential images. Other people may retain copies of public content.
Direct messages are available in the app only to the two conversation members. They are not end-to-end encrypted. Authorized service administration may access stored data where necessary to operate the service, handle a support request or investigate abuse. We do not publish your login email on your profile.
Open Posts, where available, publish an optional invitation, language and closing time with your post. Introductions and participation decisions are private to the requester and post author, with access for authorized administration when necessary. Accepting a request starts or continues their private conversation and includes the introduction and a link to the post. Closing or expiry prevents new participation; it does not delete the record of a request. These records are removed when the source post or an involved account is deleted, except evidence retained for a reviewed safety report.
Your contact preferences, blocked-message list and message read markers are private. We store them to apply your choices and show your unread chats; the other person does not receive a read receipt. Message requests record who started the conversation and whether the recipient accepted or declined it. Reporting a message sends its reference, your account identifier, the selected reason and the time to authorized Moylo administrators for review.
Hosting and service providers
Moylo uses Google Firebase for authentication, the database, file storage, server functions and web hosting. Our application database and image storage are configured in Belgium, and web hosting in the Netherlands. This does not mean that every Firebase service processes data only within the EU.
Google may process data internationally. Its Firebase terms include data-processing provisions; Google describes transfer safeguards, including standard contractual clauses and the EU–US Data Privacy Framework, in its Firebase privacy information. Technical connection data such as IP addresses and user agents are processed to deliver and protect the service.
The native apps use Firebase and Google sign-in SDKs. These providers also process technical information to provide sign-in, maintain their services and diagnose problems. The iOS SDK privacy manifests declare account and device identifiers, technical usage data and diagnostics; Google sign-in also declares approximate location. Moylo does not request GPS access or use location to recommend posts. Provider technical analytics are separate from the interests, follows and saved posts used by Moylo’s feed. See Firebase’s Apple-platform data disclosures for the provider’s description.
Storage on your browser and device
Firebase stores authentication state in your browser so you stay signed in. Signing out removes the active session from this browser. The installable web app caches a generic offline page; its service worker does not cache your feed or messages. Google may use its own storage during Google sign-in.
After an account-deletion request is acknowledged, this browser keeps a receipt identifier, the response type and the time in session storage. This lets the confirmation page show the response you received; it does not track the later cleanup status or contain your email or password.
In the native apps, Firebase Authentication retains the session on your device. The native Firestore SDK can keep a local cache of data the app has accessed and pending changes. Signing out ends your active Moylo session; it is not a guarantee that all SDK cache files have been erased. Protect access to your device, especially if you share it. Your operating system and image components may also retain temporary image files or image caches.
The native photo picker lets you select an image to upload; Moylo does not request your address book, camera or microphone. Publication retry state is held in the running app and is not a durable backup of your draft after the app closes.
Moylo includes no advertising pixels or advertising SDK and does not use third-party data to target ads. The website does not include a separate analytics SDK or optional analytics cookie layer. The native provider SDKs’ technical data processing is described above; this is not a claim that the native app sends no diagnostics or technical usage data.
Safety, support and retention
Reports contain the content reference, your account identifier, a reason and a timestamp. Profile, comment and story reports also preserve the relevant public content and the account identifiers needed to review it. A story report keeps a private copy of the reported image, without a public download link, so it can be reviewed after the story expires. Reports and their retained content are available only to authorized administrators. We process reports and support correspondence to address the issue. Preventing abuse and maintaining service security are our legitimate interests under Article 6(1)(f) GDPR; legal obligations may require processing under Article 6(1)(c).
Account data and content remain until removed or an account-deletion request is fulfilled. You can delete your own posts and comments in the app. Stories stop appearing after 24 hours; a scheduled cleanup runs every 15 minutes, so physical deletion can happen later, especially during an outage. Replacing a story schedules its previous image for removal. A private copy retained for a received safety report is separate from the visible story and may remain while the issue requires review.
Account deletion requires you to sign in again and confirm the request. Once accepted, new activity on the account is blocked. Cleanup removes your profile and uploaded content, social interactions and private conversations for both participants, including the other person’s messages in those conversations. Payment records or unresolved safety reports require review before automatic cleanup; requesting deletion does not erase evidence needed for that review.
In the native apps, open Settings and choose Delete account. Apple-linked accounts require a fresh Apple authorization on iOS and revoke Apple access before the deletion request is sent. If you cannot complete this verification on your current device, contact support. Removing the app or revoking sign-in access on its own does not request deletion of your Moylo content.
A private deletion record lets interrupted cleanup resume safely. It contains your account identifier, processing steps and timestamps, without copying your email, name or message content. After cleanup is completed, the remaining record is kept for seven days and then removed by the scheduled cleanup. This technical record is separate from records that require a reviewed retention decision.
Technical logs and provider backups have separate retention periods. Firebase states that authentication information can take up to 180 days to disappear from live and backup systems after account deletion. We may retain information needed to resolve an active dispute, comply with a legal duty or establish legal claims, limited to that purpose.
Your choices and rights
You can change your profile in Settings and request deletion under Delete my account. For a copy of your data, or if you cannot access your account, use Help & contact. Request a data copy before deletion begins. Contact us from your account email and include your handle. We may need to verify ownership before releasing or deleting data. Never send your password.
Subject to the conditions of the GDPR, you can request access, correction, erasure, restriction or portability. You can object to processing based on legitimate interests and withdraw any consent for future processing. You may complain to a supervisory authority, including the Lower Saxony data protection authority.
The For you feed orders posts using the signals described above. You can use Following for chronological browsing. Moylo does not use automated decision-making with legal or similarly significant effects.
Last updated: 2 October 2026