Privacy Policy
Marco · Last updated 31 October 2026
This policy explains what information Marco collects, why, who it is shared with, and what control you have over it. It covers Marco's website, mobile apps and Chrome extension.
Marco is operated by Josh Payton, publishing as Marco ("we", "us"). Marco was previously
called "Your Favorite"; the app is served at myfriendmarco.com, and the older
yourfavorite.co address now redirects there. You can reach us about anything in
this policy at support@yourfavorite.co.
The short version
- Guides you share are public. Marco's whole point is that a guide becomes a link you can send to anyone. Anything you put in a shared guide — places, links, photos, comments, and the name and picture on your profile — can be read by anyone who has that link, without signing in. Please read "What is public, and what that really means" before you add anything you would not want seen.
- We do not sell your information, and we do not use it for advertising.
- We measure how Marco is used, with Google Analytics for Firebase, so we can find what is slow, broken or confusing. These records are linked to your account. We do not use advertising SDKs and we do not record your screen. You can turn this off at any time in Profile → Settings → Usage data — see "Usage measurement".
- Location is used, not kept. We ask for your location only when you use a feature that needs it, and we use it to run the search — we do not store your location history.
- You can delete your account from the app, which deletes your profile, your comments, your personal data and every guide you still own — anyone you shared those guides with loses access. A few things survive — items you added to other people's guides, and a record of emails we have already sent you — and we list exactly what and why in "Deleting your account".
What we collect
Everything Marco holds falls into these categories.
| Category | What it is | Why |
|---|---|---|
| Account & identity | Your email address, display name, username, and the identifier from the sign-in method you chose (email, Google, or Apple). Optionally a profile photo and a short bio. | To create and secure your account and to attribute your contributions. |
| Your content | The guides you create, the places and links you add to them, any images you upload, and the comments you write. | This is the product — shareable guides with a comment thread per item. |
| Social connections | Who you follow and who follows you; guides you have saved; items you have favourited; the guides you contribute to or can edit. | To run the follow, save, favourite and collaboration features. |
| Location | Your device's precise location, when you grant permission. | To show what is near you on the map and to order search results by distance. See Location. |
| Notification tokens | A push-notification token issued by Firebase Cloud Messaging for each device you sign in on. | To send you notifications about activity on your guides. |
| Invitation emails | If you join a guide through an invitation link, we record the email address on your account against that guide. | A record of how you joined that guide. It is not readable by the guide's owner or by any other user, and nothing in Marco currently uses it. |
| Usage measurement | Which screens you open and a fixed set of actions you take — creating a guide, adding an item, opening a place, how long you spend on a place page, opening or sharing a guide, and sign-in attempts. Each record carries your account identifier. It never contains what you typed: not your search terms, not the titles of your guides, not your comments. | To find what is slow, broken or confusing. See Usage measurement, including how to turn it off. |
| Technical & security data | Standard server logs from our hosting and backend (including IP address and timestamps), and a device-attestation token intended to confirm requests come from a genuine copy of the app — see Security for its current status. | To keep the service running, diagnose faults, and prevent abuse of our backend. |
What we do not collect
Marco does not read your phone's address book, calendar, microphone, health data, or device sensors, and does not collect payment or financial information. Marco does not use your device's advertising identifier (the IDFA on iOS or the advertising ID on Android) for advertising. On iOS, Marco never asks for tracking permission, which iOS requires before any app can read the IDFA. On Android, Google Analytics in test builds released before this policy update could read the advertising ID; from the next Android release, the app is configured not to read it. Marco does not ask to track you across other companies' apps and websites. We ask for camera and photo-library access only at the moment you choose to attach a picture. We never see or store your password: if you sign in with a password, it is handled by Google's Firebase Authentication and is never sent to us. Marco has no Facebook login and no Facebook application.
What is public, and what that really means
Marco is built around sharing, so some information is public by design. This is the section most worth reading carefully.
Your profile is public
Your display name, username, profile photo and bio can be viewed by anyone, including people who are not signed in. Your followers and following lists, and their counts, are visible to other signed-in Marco users but not to signed-out visitors. Your email address is not public — it is stored separately from your public profile and is readable only by you and by our servers.
A shared guide is readable by anyone with the link
When you share a guide, we mint a link. Anyone holding that link can open the guide and read its contents — the places and links in it, the comments on them, and who contributed — without signing in and without you knowing. Links get forwarded, so treat anything you add to a shared guide as public.
Making a guide private later may not take it back
You can switch a guide out of public visibility, and that stops it appearing in Marco's public feeds and discovery surfaces. But we cannot promise it retroactively locks out someone who already has the link. A person who received a share link keeps the guide's identifier, and parts of the underlying data remain reachable by identifier to a technically capable person even after the guide is made private.
We are telling you this plainly rather than implying a guarantee we do not yet have. We are working on closing it. Until then: the reliable way to remove something you no longer want shared is to delete it, not to switch the guide to private.
Comments are public
Comments on an item in a guide are readable by anyone who can reach that guide.
Location
Marco asks for location permission only when you use a feature that needs it — opening the map to see what is nearby, or running a search that should be ordered by distance. We deliberately do not ask on app launch.
Your coordinates are sent to our own backend to run that search and are used to compute distances. We do not store a history of where you have been, and your location is not saved to your profile. You can withdraw location permission at any time in your device settings; the map and search still work, they simply stop being centred on you.
Usage measurement
Marco uses Google Analytics for Firebase to measure how the app is actually used. We do this for one reason: to find the parts that are slow, broken or confusing, which we otherwise only learn about if someone tells us.
What is recorded. Which screens you open, and a fixed, deliberately small set of actions: starting and finishing creating a guide, starting and finishing adding an item to one, opening a place page and how long you spend on it, whether that place page had any written content, how far down a guide or a place page you scroll (as a rough band, such as "halfway"), when a place search finds nothing (we record only how many characters the search had, never what you searched for), opening a shared guide, joining a guide you were invited to, creating a share link, and signing in or signing up (including when it fails, and which method you used).
What is never recorded. Anything you typed. We do not send your search terms, the titles or descriptions of your guides, your comments, your display name or your email address. The records contain identifiers and fixed labels only — never free text you wrote.
It is linked to your account. These records carry your Marco account identifier rather than being anonymous, and we want to be plain about that rather than hide behind the word "anonymous". Marco is a small, early product with a handful of testers, and an anonymous count cannot answer the question that actually matters — which person got stuck, and where. The trade-off is a real one, which is why the off switch below exists.
How to turn it off. Go to Profile → Settings → Usage data and choose "Don't send usage data". Collection stops immediately and stays off on that device until you turn it back on. Nothing else about Marco changes.
Google acts as our processor for this data. We do not sell it, we do not use it for advertising, and there are no advertising SDKs or session-recording tools in Marco.
Device identifiers and approximate location. To tell one installation from another, Google Analytics for Firebase uses an identifier it creates for each installation of the app, and on iOS the identifier Apple gives an app's developer for that device. It also estimates your approximate location, such as your city or country, from your IP address. It is configured not to use your device's advertising identifier, except in Android test builds released before this policy update. Turning usage data off stops this too.
How we use your information
- To measure how Marco is used, so we can fix what is slow or confusing — see Usage measurement.
- To provide the service: your account, your guides, and the sharing and collaboration features.
- To send notifications you have asked for — activity on your guides, invitations, and collaboration emails.
- To keep the service secure and working: diagnosing faults, preventing abuse, and enforcing rate limits.
- To operate the closed alpha. Marco is pre-launch, and we currently receive an automatic email notification when a new account is created that is not one of ours, so we know when a real person has found the app. That notification contains the new account's email address.
Where the UK GDPR or EU GDPR applies, our legal bases are performance of a contract (running the account and features you asked for), consent (location access and push notifications, which you grant on your device and can withdraw), and our legitimate interests (keeping the service secure and knowing that it is being used).
Who we share it with
We do not sell your information. We share it only with the services that run Marco:
- Google (Firebase) — our hosting, authentication, database, file storage and push-notification provider. Most of your data lives here.
- Google Maps Platform — map tiles and place lookups. When you use the map, Google receives the requests needed to render it, including your device's IP address, and on the web version the Google Maps script loads directly in your browser. In the iOS app, the Google Maps SDK also sends Google its own diagnostics, such as crash and performance reports and a device identifier.
- Apple — only if you choose Sign in with Apple.
- Our email delivery provider — to send invitations and collaboration notifications to the address you or a guide owner provided.
Search runs on our own infrastructure, not a third-party search vendor, so your search queries are not passed to another company.
We also read place information from Google Places, Wikipedia, Wikidata and Overture Maps to populate places in Marco. That is data flowing to us; your personal information is not sent to those sources.
We may disclose information if we are legally required to, or where necessary to protect our rights or someone's safety.
Shared links and previews
When a Marco link is posted to a messaging or social platform, that platform fetches the page to build a preview card showing the guide's title and image. This is how link previews work everywhere, and it means the platform you post to sees the link and its public preview content.
On iOS and Android, your phone can help load previews for links you add or see in a guide when our server cannot retrieve them. This is enabled by default, including when you are signed out. The linked website receives your IP address even if you have not tapped the link. These requests do not use your browser cookies or sign-in credentials. Accepted titles, descriptions and preview images are shared with other people who have the same link.
You can turn this off under Link preview settings in any guide, or in Settings: choose Use existing previews only. Automatic preview loading is limited and pauses when the app is in the background or your device has Low Data Mode or Data Saver enabled. Marco remembers the setting and recent preview attempts on your device.
Chrome extension
Marco's Chrome extension lets you preview webpages and links, save them to your guides, create guides and keep personal favourites. It uses your Marco account, including your email address and account identifier. Google or email sign-in is handled by Firebase Authentication; the extension stores its sign-in session in your browser.
Previews happen before you press Save. While you are signed in and the side panel is open, the extension reads the active page's URL and title, or the link you selected from the right-click menu. It sends the target URL to our backend to retrieve its preview and check which of your guides and favourites already contain it. The panel follows the active page as you browse. It does not read your existing Chrome browsing-history database.
Our backend may fetch the linked website to obtain a title, description and image. Preview metadata for public links can be cached and reused for other people viewing the same link, even if you do not save it. Shared preview records are not a personal browsing-history list and are not automatically deleted when you remove a save or your account. When the panel displays a preview image or guide image, your browser requests it from its image host, which receives your IP address. Our backend also keeps technical request logs, including IP addresses and timestamps, for operation and security.
Saving a link, creating a guide or changing a favourite sends the information needed for that action to our Firebase backend. Saved links, titles, descriptions and images follow the guide's access and sharing settings described above. Removing the extension does not delete your Marco account or saved content; use Marco's controls to remove that content or delete your account.
The extension remembers selected-guide preferences using Chrome's sync storage, which may sync them through your Chrome account. It also keeps the current capture target for the browser session, an unfinished save or removal operation for retry, and temporarily the email address used to request a sign-in link. It does not request your device's GPS location or run the mobile app's Analytics SDK. Closing the side panel stops its automatic page-preview requests; disabling or removing the extension stops its browser activity.
Limited Use. Our use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide or improve its features and to maintain, secure and diagnose them. We do not sell it, use it for advertising, or use it to determine creditworthiness or for lending. Transfers are limited to providing or improving these features, security, legal requirements, or a business transfer with explicit prior user consent. Human access is limited to specific user consent, security investigations, legal requirements, or aggregated and anonymised information used for internal operations.
For extension support and privacy questions, contact chrome-plugin-support@myfriendmarco.com.
Storage on your device
Marco stores a small amount of data on your device or in your browser to keep you signed in and to remember your preferences. On the web this uses browser storage rather than advertising cookies. We do not use tracking or advertising cookies, and we do not track you across other websites.
How long we keep it
We keep your account information for as long as your account exists. Content you have published into guides remains while those guides exist. Server and diagnostic logs are kept on our providers' standard retention schedules. When you delete your account, see below.
Deleting your account
You can delete your account from within the app, in profile settings. Doing so removes:
- your sign-in credentials and authentication record;
- your profile, and the private record holding your email address and push-notification tokens;
- your profile photo;
- your saved guides, favourites, and your followers and following lists;
- your comments;
- your username reservation, and your membership of guides you contributed to or could edit — including the invitation-email record described above, if you joined a guide through an invitation link;
- every guide you still own, together with the places in it, the comments on it, and the access you had given other people to it.
Deleting your account deletes the guides you created
If you created a guide and still own it when you delete your account, that guide is deleted with it. Anyone you shared it with loses access, including people you had added as editors, and anything they added to it goes too. We do not hand your guide to someone else, and we do not keep it running without an owner.
Guides created by other people are not affected. Items you added to their guides stay where they are and simply stop carrying your name; your comments are deleted everywhere, including on their guides.
One place your email address is not yet erased automatically
We would rather list this than let you infer an erasure we do not currently perform:
Records of emails we have already sent (invitations and notifications) retain the address they were sent to, as sent mail ordinarily does. Email support@yourfavorite.co and we will erase it by hand — your right to erasure covers it and we will honour it on request.
What deletion does not remove — and why
Items you added to other people's guides remain. If you added a place or a link to someone else's guide, that item stays in their guide after your account is gone. Deleting it would silently remove content other people are relying on, and in a collaborative guide it would look like the recommendation was never made. (This applies to items only — your comments are deleted, as listed above.)
Your identity is detached from it: once your account is gone there is no profile left to resolve, and Marco simply credits the contribution to "a friend".
This covers other people's guides only. Guides you created are deleted with your account, as described above. They used to be kept, and that changed.
If you want a specific contribution removed as well, delete it before deleting your account, or email us at support@yourfavorite.co and we will remove it.
Your rights
Depending on where you live — including in the UK and the EEA — you have the right to access a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, to data portability, and to withdraw consent you have given (such as location or notification permissions).
You can exercise most of these directly in the app: edit your profile, revoke permissions in your device settings, or delete your account. For anything else, email support@yourfavorite.co and we will respond within one month.
If you are in the UK you may complain to the Information Commissioner's Office; in the EEA, to your local data protection authority.
Children
Marco is not intended for children under 13, and we do not knowingly collect information from them. If you believe a child has given us personal information, email support@yourfavorite.co and we will delete it.
International transfers
Marco runs on Google Cloud infrastructure, and your information may be processed in the United States and elsewhere. Where data leaves the UK or EEA, our providers rely on approved safeguards such as the European Commission's Standard Contractual Clauses.
Security
Access to data is enforced at the database level by rules that determine who may read and write each record, and sensitive fields such as your email address and notification tokens are stored separately from your public profile so they are never world-readable. No service can promise perfect security, but we design for the principle that private things should be unreachable rather than merely hidden.
One qualification, because we would rather state it than imply a protection we have not switched on yet: the app sends a device-attestation token with its requests, and our backend currently records that token but does not yet reject requests without one. Turning on enforcement is planned work. We mention it because "we verify every request comes from a genuine copy of the app" would be the natural thing to write here, and it would not be true today.
Changes to this policy
If we change what we collect or how we use it, we will update this page and change the "last updated" date above. Material changes will be communicated in the app.
The canonical location of this policy is
https://myfriendmarco.com/privacy. The older
yourfavorite.co/privacy address redirects to it.