momstash

Legal / Privacy

Privacy Policy.

Last updated: 2026-10-08

This policy explains what the Momstash app and the momstashapp.com website collect, why, who else touches it, how long we keep it and what you can do about it. We've tried to write it the way we'd want it explained to us: plainly, and without hiding anything in the small print.

Privacy controls during the app update. Updated app builds introduce the separate analytics choice described below. If your app does not show that choice, it still uses the older controls: product analytics follows the iOS tracking answer, and older attribution could start after setup. Earlier builds also sent more analytics context, as described in section 3.4. The new controls do not erase that history. Backend subscription analytics and its queue described in section 11 apply when that feature is enabled on our service.

The short version

  • Momstash is your private stash. The links, screenshots, recipes, places and notes you save are yours. We use them to run Momstash for you and for nothing else.
  • To read a link, we have to open it. When you save a link or a screenshot, our server fetches the public post and uses AI (OpenAI) to turn it into a recipe, a place, a product or whatever it contains. Details are in section 5.
  • Your account is a username and a password. The iPhone app does not ask for your email address or phone number.
  • Your precise location never leaves your phone. If you let Momstash show where you are on your map, that position stays on the device. Older analytics captures included approximate IP-derived location; new captures are configured to discard IP data and disable that location enrichment (section 3.4).
  • Analytics and ad measurement are optional. In updated app builds, a separate choice in Momstash controls both PostHog product analytics and Singular install attribution. Apple's tracking choice is separate and controls access to the advertising identifier. You can use Momstash if you decline either choice.
  • No ads in the app, no selling. We don't sell your data and there are no ads in Momstash. If you allow measurement, Singular helps us learn which of our own ads and links bring people to Momstash. It gets your device's advertising identifier only if you also allow tracking when iOS asks, and it never gets anything you saved (section 3.5).
  • Apple takes your payment. We never see your card.
  • You can wipe your data or delete your account entirely from inside the app (section 12).

1. Who we are

Momstash is operated by Mimi Studio d.o.o., a limited liability company organized under the laws of the Republic of Slovenia, with its registered office at Trubarjeva cesta 79, 1000 Ljubljana, Slovenia ("Mimi Studio", "we", "us").

For the General Data Protection Regulation (GDPR), Mimi Studio is the controller of the personal data described here. Because we are established in the European Union, we don't need a separate EU representative.

Questions about this policy or your data: [email protected].

2. Who Momstash is for

Momstash is made for grown-ups, mostly busy parents, who want one place for everything they save. It is not directed at children. You must be at least 16 to use Momstash, and if you are under 18 you need a parent or guardian's permission (the Terms of Use say the same). We don't knowingly collect data from children under 16. If you think a child has given us information, write to us and we'll delete it.

3. What we collect

3.1 Things you give us

What Details Where it lives
Account A username and a password you choose. The password is stored only as a secure hash by our sign-in service. The iPhone app does not ask for an email address or phone number. Our sign-in server (Logto), section 9
Links and screenshots you import The web address of each link you share to Momstash (TikTok, Instagram, YouTube, Reddit, Pinterest, Google Maps, articles and so on), and any screenshot or photo you choose to import. Our servers
Your library Your saves and what was extracted from them, collections, meal plans, grocery lists, notes, ratings and reviews, comments on your own saves, archived items and custom save types. On your phone, and backed up to our servers while you're signed in
Profile The name, username and short bio you type into your Momstash profile, and your profile visibility choices. On your phone, and backed up to our servers while you're signed in
Onboarding answers What you tell us during setup: where and what you save, what frustrates you, what matters most, your age range and how you heard about Momstash. We use the save answers to create your first collections. On your phone, and backed up to our servers while you're signed in
Posts and social activity Posts and replies you write in the Social tab, who you follow, and what you like. Our servers
Settings Language, appearance, notification choices and similar preferences. On your phone, and backed up to our servers while you're signed in
Support emails Whatever you write to us, and the email address you write from. Our support mailbox

Please don't put things into Momstash that you would not want stored on a server, such as health records, ID documents or passwords. If a screenshot you import contains other people's details, that's something you've chosen to save; please be thoughtful about it.

3.2 Things collected automatically

  • Account identifiers. A random account ID created by our sign-in service. It links your library, your imports and your subscription to you. It is not your name or email.
  • Account activity. When your account was created (this is what starts your 14-day free access, see the Terms) and the last day you used it.
  • Import records. For each import: the link, its status, timing, which of our providers answered, and what it cost us to process. We keep these to show your import history, to retry failed imports, and to apply daily limits.
  • Technical data. Like any internet service, our servers see the IP address your phone connects from. Our API uses it briefly in memory for rate limiting and doesn't store it in its logs. Our sign-in service records sign-in events, which can include the IP address and device/browser type, for security. Our server logs record each request's time, path and result, and error logs can include your account ID.

3.3 Things we get from others

  • Subscription status from Apple, via RevenueCat: which product you have, whether it's active, when it renews or expires, and transaction identifiers. We never receive your card number or billing address.
  • Public information about the posts you save: when we fetch a link, we get what the post publicly shows, such as its title, caption, the creator's name or handle, images, video, audio and public comments. See section 5.

3.4 Things Momstash does not collect

  • No precise location on our servers. If you allow location access, Momstash uses it on your phone only, to put a "you are here" dot on your map of saved places. It isn't sent to us or anyone else.
  • No contacts, calendar, microphone or health data.
  • Photos only when you choose them. Momstash sees only the screenshot or photo you pick or take to import, never the rest of your library.
  • No ad networks inside the app and no data brokers. The one attribution tool we use, and exactly what it receives, is described in section 3.5.
  • Crash reporting is off unless Momstash's Sentry project is configured. The app contains a privacy-filtered Sentry integration, but without its project address it never starts or sends anything. If enabled, it can send a stack trace, exception type and basic app/device/OS fields; it strips identity, exception messages, URLs, request bodies, console/network/UI breadcrumbs, device names, tracing, screenshots and session replay.
  • Product analytics only with consent. Momstash uses PostHog, open-source product-analytics software run for us on Google Cloud in Iowa, United States (us-central1), including event, profile and backup storage; Mixpanel is not used. Our selected policy keeps events for 48 months, profiles until deletion, and backups for 14 days (section 11). In updated app builds, you choose whether to allow analytics inside Momstash. Apple's tracking prompt does not make that choice for you. Until you allow the current analytics notice in those builds, we do not create an optional analytics identity, keep an analytics event queue or send these events. Declining leaves Momstash usable.

After you allow analytics in an updated build, we record only approved actions and basic app information: for example finishing onboarding, an import's source category and result count, app version, coarse device type, language, and subscription outcomes. Events use a random analytics ID; after you sign in, they can be joined to your opaque Momstash account ID. Subscription events can include the product, transaction ID, price and currency. Analytics does not receive your username, email, saved titles, source links, notes, place names, search terms or anything you type. Captures from updated builds do not include page URLs or referrers, advertising identifiers, or automatic browser/session context. Automatic capture, page views, session recording, performance capture, heatmaps and exception capture are disabled.

Like any internet endpoint, the analytics service sees the connecting IP address while handling a request. For new captures, we instruct it to discard client IP data and disable IP-derived location enrichment. Earlier builds and historical collection: older app builds send internal app routes and SDK device/session context. Earlier service settings also retained IP addresses and estimated approximate location (city, region and country, accurate to roughly 10 km). Those historical records are not erased by the new collection settings or by switching analytics off.

In updated builds, you can change the independent analytics choice in Settings → Storage & data. Withdrawing it stops new optional PostHog and Singular measurement, clears the app's optional analytics queue and identity, and removes the analytics identifier it supplies to RevenueCat. This does not confirm deletion of records already held by those services; section 12 explains the current deletion limitations and how to contact us. We do not replay actions from before you allowed analytics.

3.5 Ad attribution (Singular)

When we advertise Momstash, we want to know which ads and links actually bring people to the app, so we don't pay for the ones that don't. For that the iPhone app includes the software kit of Singular (Singular Labs, Inc., United States), an attribution service.

What Singular receives from the app:

  • Device and install information: device model, iOS version, language, country, app version and network type, the time of the install and app sessions, and the IP address your phone connects from. The native SDK can also process your iPhone's vendor identifier (IDFV, a random ID that is the same only across apps from the same developer), subject to the identifier limits applied for your tracking choice.
  • Your advertising identifier (IDFA) only if you allow tracking when iOS asks. If you decline, or iOS restricts tracking, the identifier isn't available and isn't sent.
  • A random analytics ID, only if you allow analytics. This is the anonymous product-analytics ID described in section 3.4, never your Momstash account ID. It lets the install's source (for example "came from that campaign") be recorded in our own product analytics. Without analytics consent, Singular gets no such ID.
  • A few app events: that you finished onboarding and that you bought Momstash Pro, with the product, the actual store transaction ID, the price, currency and confirmed trial status when available. Restoring an existing purchase is not reported as new purchase revenue. Earlier versions also reported account creation; the current version does not send that event. Singular uses Apple's SKAdNetwork too, which reports installs to ad networks without identifying you.

What it never receives: anything you save or import (no titles, links, notes, places, screenshots or searches), your username, your Momstash account ID, your profile or your onboarding answers.

When it starts in updated builds. Singular requires your separate in-app analytics permission and a settled iOS tracking answer. If you decline analytics, it remains off even if you previously allowed tracking in iOS. If you allow analytics and decline tracking, or iOS restricts tracking, measurement can start with advertising identifier limits. If the iOS tracking answer is unavailable or still undecided, Singular stays off; completing onboarding does not override that. Declining either choice doesn't change what you can do in Momstash. Earlier builds could start attribution after setup without a settled tracking answer; the advertising identifier still requires iOS authorization.

Singular may pass the result (for example "this install came from that campaign") back to the ad network that ran the ad, so it can count its results. If you allow analytics, its anonymous analytics ID also lets the install source be joined to our product analytics through the Singular Hub. This join does not send your Momstash account ID or anything you saved to Singular. You can stop optional measurement in Settings → Storage & data and change advertising identifier permission in iOS Settings → Privacy & Security → Tracking. Stopping measurement does not itself erase earlier attribution records.

4. Why we use it, and our legal basis

Why What we use Legal basis (GDPR Art. 6)
Creating and securing your account, signing you in Username, password hash, account ID, sign-in events Contract
Importing and organizing what you save Links, screenshots, the public content they point to, your library Contract
Backing up your library and restoring it on a new phone Your library, profile, settings, onboarding answers Contract
Social features: posts, replies, likes and follows Your posts and the author details you choose to show Contract
Free access period, daily limits and Momstash Pro Account creation date, import counts, subscription status Contract
Preventing abuse, fraud and runaway costs, and keeping the service secure IP address (briefly), request logs, import cost counters Legitimate interests (keeping Momstash safe and affordable to run)
Processing public information about the creators and commenters of posts you save Names, handles, captions and comments that are already public Legitimate interests (giving you a useful copy of what you chose to save)
Answering you Support emails Contract, or legitimate interests
Keeping accounting records of purchases Transaction records Legal obligation
Understanding how Momstash is used, so we can improve it, in updated builds (section 3.4) Approved app actions, anonymous/account analytics identifiers, basic app/device information and subscription events Your separate in-app analytics consent, which you can withdraw in Settings → Storage & data
Measuring which of our ads and links bring people to Momstash in updated builds, using the advertising identifier (section 3.5) Advertising identifier and attribution information Your separate in-app measurement consent and your permission in the iOS tracking prompt; either can be withdrawn
The same in updated builds, without the advertising identifier Device and install information, anonymous analytics join ID, onboarding and purchase events Your separate in-app measurement consent, which you can withdraw in Settings → Storage & data
Showing your location on your map (on your phone only) Device location Your permission in iOS, which you can withdraw in Settings at any time

Earlier builds. The previous policy described product analytics as following the permission given in the iOS tracking prompt, and attribution without the advertising identifier as relying on legitimate interests (understanding which of our own marketing worked). These are historical policy positions. A new in-app analytics choice does not retroactively authorize earlier collection, and this description does not establish whether earlier processing met applicable legal requirements. Older records and pending deletion are described in sections 3.4 and 12.

Where we rely on legitimate interests you can object (section 13). We don't use your data for automated decisions that have legal or similarly significant effects on you, and we don't profile you for advertising.

5. How an import works, and who helps

When you share a link or a screenshot to Momstash, this is what happens:

  1. Your phone sends the link (or the image) to our server, together with your account ID.

  2. Our server fetches the public post. Depending on the site, we fetch it ourselves (using open-source tools that talk directly to the site) or ask a provider to fetch it for us:

    • Apify (Apify Technologies s.r.o., Czech Republic), a web data platform, for sites like Instagram, TikTok, Reddit, Facebook, Threads and Pinterest.
    • The platforms' own official APIs where available: Google (YouTube Data API), X, Pinterest and Meta (Threads).
    • Instantane, our own capture service, which stores a snapshot of the public post and its media so we don't have to fetch the same post twice. It holds public posts only. It doesn't know who saved them.

    These providers receive the link you shared, not your name, username or account ID.

  3. AI reads it. We download the media, turn speech into text and take a handful of still frames from videos. We then send the text, the transcript and up to twelve images to OpenAI (United States), which transcribes audio and extracts the useful things: ingredients and steps, places, products, films and so on. For a screenshot, OpenAI receives the screenshot itself. We send OpenAI the link, the post's title, author and text, the transcript and the images. We don't send your account ID, username or anything else about you. We ask OpenAI not to store the request (store: false), and under OpenAI's API policy it isn't used to train their models. OpenAI may keep API data for up to 30 days for abuse monitoring, or longer where the law requires.

  4. We look up details. To fill in a place's address, hours and photos we send the place's name to Google Places. To find a product's listing we search Amazon for its name through Apify. To find posters and details for films, shows and games we look up the title in a film and game catalogue service (Cinéphile, operated by, built on TMDB and RAWG data). Only the thing's name goes out, never anything about you.

  5. We save the result to your library, including copies of the post's images and media so your save keeps working if the original disappears.

"Ask Momstash" questions about a save are answered on your phone from what was already extracted. Your question isn't sent anywhere.

AI can be wrong. Always double-check quantities, allergens, opening hours, prices and anything important. See the Terms of Use.

6. What other people can see

Your library is private. Your saves, collections, plans, notes, reviews and profile details are not visible to other users. Sharing a collection uses your phone's share sheet to send a plain-text list to whoever you choose. Nothing is published.

The Social tab is the exception, and you pick who sees each post:

  • Only you: nobody else.
  • Followers only: people who follow you.
  • Anyone on Momstash: every signed-in Momstash user.

Posts show the author details linked to your account. Replies and likes are visible to people who can see the post. You can delete your own posts at any time.

7. Notifications

Notifications in the current app are scheduled and shown on your phone. The app does not register an Apple push-notification token, send it to our server or receive server push notifications. You can change notification permission in iOS Settings → Momstash.

8. Purchases

Momstash Pro is sold through the App Store. Apple is the merchant and handles your payment details under Apple's own privacy policy. RevenueCat (RevenueCat, Inc., United States) checks your purchase with Apple and tells the app and our server whether Pro is active. RevenueCat receives your Momstash account ID and your purchase records from Apple.

9. Who handles your data for us

We don't sell your personal data. The advertising measurement described in section 3.5 may count as sharing under some US state laws (section 13). We use these service providers for the purposes described:

Who What for Where
DigitalOcean, LLC Hosting our API, workers, databases (your library, imports, posts, account records) and our sign-in service Frankfurt, Germany (EU)
Appwrite (open-source software we run ourselves on DigitalOcean) Storing your uploaded screenshots and copies of media from your saves Same as above
Logto (open-source software we run ourselves on DigitalOcean) Accounts and sign-in Same as above
OpenAI, L.L.C. Transcribing audio and extracting saves from posts and screenshots (section 5) United States
Apify Technologies s.r.o. Fetching public posts and product listings for the link you shared Czech Republic (EU); its cloud providers may process data outside the EEA
Google LLC YouTube Data API and Google Places API lookups United States
X Corp., Pinterest, Inc., Meta Platforms (Threads) Official APIs for fetching a public post you shared from their platform United States / Ireland
Cloudflare, Inc. Storage for Instantane's snapshots of public posts; DNS Global network
Cinéphile (api.cinephile.unifiedsense.com) Film, TV and game catalogue lookups by title (only the title is sent) May be outside the EEA
RevenueCat, Inc. Subscription status United States
PostHog (open-source software run for us on Google Cloud) Product analytics, only with your separate consent (section 3.4): approved app actions, anonymous/account analytics identifiers, basic app/device information, subscription events and install attribution. Historical IP/approximate location collection is described in section 3.4. Iowa, United States (us-central1), including event, profile and backup storage
Singular Labs, Inc. Optional ad attribution: which ad or link brought an install, anonymous analytics join ID, and onboarding/purchase events described in section 3.5. The advertising identifier additionally requires your iOS tracking permission. United States
Apple App distribution, payments and notifications. An independent controller under its own policy. Global

When you tap a link on a save (for example a recipe's original post or a product page), it opens in Safari inside the app. That website then sees your visit under its own privacy policy, not ours.

If we add a provider, this list changes before any data goes to them.

10. International transfers

Our servers are in the European Union. Some providers above (OpenAI, Google, RevenueCat, Singular, our PostHog analytics and, depending on the request, Apify, Cloudflare, X, Pinterest and Meta) may process data in the United States or elsewhere outside the EEA. Where they do, we rely on the European Commission's adequacy decision for the EU–US Data Privacy Framework (where the provider is certified) or on the Standard Contractual Clauses, together with the providers' additional safeguards. You can ask us for more detail at [email protected].

11. How long we keep it

What How long
Your library, profile, settings, onboarding answers, posts, follows, likes, uploaded screenshots and media copies Until you reset your data or delete your account in the app
Import records 90 days after the import finishes
Daily usage and cost counters Scheduled to expire 2 days after their latest update; database cleanup may run later. This is separate from import-history retention.
Backups of our databases Up to 7 days (daily backups, kept for a rolling week)
Your account (username, password hash, account ID, creation date) Until you delete your account in the app (Settings → Account & sync → Delete account). "Reset everything" deletes your data but keeps the account itself, including the date your free access started.
A minimal deletion record (your random account ID and the fact it was deleted) Kept after deletion so an old signed-in phone can't accidentally recreate your data
Sign-in event records A limited period for security and troubleshooting, then deleted
Server logs A limited period for security and troubleshooting, then deleted
Instantane snapshots of public posts (not linked to you) Only as long as needed to serve imports, then deleted
Data sent to OpenAI Not stored by us beyond your save. OpenAI may keep it up to 30 days for abuse monitoring.
Support emails As long as needed to help you, then deleted
Purchase and transaction records As long as tax and accounting law requires
Product analytics events in PostHog (approved app actions, subscription/install attribution and historical IP/approximate location) Selected policy: 48 months total. The first 3 months are in active storage; older events move to Google Cloud Storage and are scheduled to expire at month 48. Email [email protected] to request deletion sooner; turning analytics off or resetting the app does not itself erase historical service records. Current deletion limits are explained in section 12.
PostHog person profiles (anonymous/account analytics identities and associated properties) Until erasure is requested and completed; they do not have a fixed 48-month expiry.
PostHog backups 14 days. Copies of deleted analytics records may remain in backups for this window.
Pending optional subscription analytics on our backend Delivery expires after 7 days. The background worker clears expired payloads; a worker outage may delay physical cleanup. Queued payloads clear when the backend receives withdrawal or reset; an offline choice reaches it when the app reconnects. Delivery identifiers used to prevent duplicate or withdrawn-event replay remain for 30 days, without an account ID or event body in those receipt records.
Attribution identifiers needed to complete a deletion request The minimum account-associated anonymous identifiers remain only while needed to complete and verify the provider erasure request. Deleting PostHog records does not itself prove Singular deletion.
Ad attribution data at Singular (device and install information, advertising identifier if you allowed tracking, the events in section 3.5) We are confirming the retention schedule for our account, including Singular Hub and any ad-network copies. Singular's published user-level log schedule varies by data type, generally 14–60 days, with partner restrictions; it does not establish the lifetime of every stored or exported record. The earlier version of this policy stated 25 months, which we have not verified for this account. Contact us about deletion using section 12.
Data on your phone Until you reset it or delete the app

12. Your choices and how to delete your data

In the app

  • Export everything: Settings → Storage & data → Export everything creates a file with every save, collection, plan, grocery list, setting and profile field.
  • Reset everything: Settings → Storage & data → Reset everything deletes your library, import history, posts, uploads and media copies from our servers and wipes this phone. This can't be undone, so export first if you're not sure.
  • Delete a single save or post from its own screen.
  • Location, photos and notifications can be switched off at any time in iOS Settings → Momstash.
  • Tracking (the advertising identifier Singular may use, section 3.5) can be switched off at any time in iOS Settings → Privacy & Security → Tracking.
  • Analytics and install attribution can be switched off together in Settings → Storage & data. This stops new optional measurement and clears the app's optional analytics identity and queued events. Apple's tracking permission remains a separate setting.
  • Sign out from Settings → Account & sync.

Delete your account completely. In the app, go to Settings → Account & sync → Delete account and confirm. This removes your account itself (your username, password and sign-in record), your library, import history, posts, uploads and media copies from our active services, then wipes this phone and signs you out. This can't be undone, so export first if you're not sure. If part of the account or file deletion remains pending, the app tells you and you can retry. We also request deletion of your RevenueCat customer record; an account-deletion success does not by itself verify that provider's completion. Apple's purchase and billing records are separate. The minimal deletion record, pending provider-erasure work and attribution identifiers described in section 11 may remain; database backup copies follow their stated retention window. If you can't sign in any more, email [email protected] with your Momstash username. We'll respond within one month, explain any remaining work and confirm what has been removed.

Historical analytics and attribution records are handled separately. Switching analytics off, signing out, resetting the app or deleting its local identity is not confirmation that PostHog, Singular or an ad network has erased earlier records. To request deletion of those records, write to [email protected]. We may need to confirm the relevant account or analytics identity and will explain the result and any records that must be retained. We do not treat local reset as proof of service-side erasure.

Current PostHog deletion limitation. The analytics service's event-deletion job is currently not running. A request can be queued while its live events remain, even if a person profile has been removed. We cannot promise prompt or complete analytics erasure until that job is repaired and deletion is checked. We will distinguish a pending request from confirmed removal when answering you. After live removal, backup copies may remain for their 14-day retention window. Switching analytics off still stops new optional measurement as described above.

Current attribution deletion limitation. We have not yet verified removal across Singular, Singular Hub and any ad-network copies. Removing a PostHog profile or stopping the native SDK does not establish that those copies are gone. Contact us at [email protected] about earlier records; we will explain which services have confirmed removal and which remain pending.

Deleting your account or data doesn't cancel Momstash Pro. Apple bills the subscription, so cancel it in iOS Settings → your name → Subscriptions. Otherwise it keeps renewing.

13. Your rights

If you are in the EEA, the UK or Switzerland, you have the right to access your data, correct it, delete it, restrict or object to how we use it, receive it in a portable format, and withdraw any permission you gave (this doesn't affect what we did before). You can also complain to a data protection authority. In Slovenia that's the Information Commissioner (Informacijski pooblaščenec, www.ip-rs.si), and you can also go to the authority where you live.

If you are in California or another US state with a privacy law, you have the right to know what we collect and why (this policy), to get a copy, to correct it, to delete it, and not to be treated differently for asking. We do not sell personal information. Measuring our own ads through Singular (section 3.5) may count as "sharing" for cross-context behavioural advertising under some state laws. To stop optional measurement, decline analytics in Momstash or turn it off in Settings → Storage & data. To prevent use of the advertising identifier, also decline tracking when iOS asks or turn it off in iOS Settings → Privacy & Security → Tracking. We don't use or disclose sensitive personal information for anything beyond providing the service.

Wherever you live, write to [email protected]. We'll answer within one month (or the time your law requires), may need to confirm it's really your account (for example by asking you to write from inside the app or confirm details only the account holder would know), and will explain if we can't do something and why. You can appeal a refusal by replying to our answer.

14. Security

Everything between the app and our servers is encrypted with HTTPS. Every request is checked against your sign-in token, and every database query is scoped to your account, so one person's library can't be read by another. Uploaded files and media copies can only be opened by their owner. Server secrets never ship inside the app. No system is perfectly secure, but if something ever goes wrong in a way that affects you, we'll tell you and the authorities as the law requires.

15. The website

momstashapp.com is an information site. It has no accounts. It is hosted by DigitalOcean in Frankfurt, sets no cookies, has no analytics or tracking, and loads no third-party scripts or fonts. The hosting provider sees your IP address when you load a page, as with any website.

16. Changes

If we change how Momstash handles your data, we'll update this page and the date at the top. If the change matters, for example a new kind of data or a new provider, we'll tell you in the app before it takes effect.

17. Contact

Mimi Studio d.o.o.
Trubarjeva cesta 79
1000 Ljubljana, Slovenia
[email protected]