mikum.me™

Privacy Policy

Last updated: August 19, 2026

We care about being clear on how we handle your data. This Privacy Policy explains how MIKUM-ME INC, which operates mikum.me ("mikum", "MIKUM-ME", "we", "us"), collects, uses, and shares information when you use our website and service (the "Service"), which lets people create and share photo-based location arrival guides.

Information we collect

Account information. When you sign in, we collect an identifier depending on how you sign up: your email address, your phone number (if you use SMS verification), and, if you use Google or Apple sign-in, the name and basic profile information those services provide. You can also add a display name.

Guest sessions. You can start building a guide before signing up. We create a temporary anonymous session so your draft is saved while you work. If you don't sign up, an unpublished draft is automatically removed after a period of inactivity.

Content you create. The guides you build, including photos and short videos you upload, captions, addresses, map coordinates, floor and parking details, door or access codes, and contact numbers you choose to add. If you set up custom branding, this also includes your organization name and logo.

Contacts you add. If you designate approval contacts for a gate code, or add a phone or WhatsApp number to a guide, we store those names and numbers so we can text them an approval request or show them to your visitors. Only add someone else's number if they have agreed to it.

Payment information. If you subscribe to a paid plan, payments are processed by Stripe. We do not store your full card details; we retain a Stripe customer identifier and your subscription status.

Usage & technical information. Basic, aggregated activity such as how many times a published guide has been opened (which we also show owners as simple statistics), and standard technical data (like device, browser, and IP address) needed to operate, secure, and rate-limit the Service. Open counts shown to owners are totals only, and we don't track you across other websites. For our own internal statistics we also keep, per guide opening, an approximate location (the country, city, and approximate geographic coordinates at city-level precision, which our content network derives from the IP address; never the IP itself, and never your device's GPS or precise location), the kind of device, the browser language, and the website a link was tapped from. These records carry no identifier for you and are not shown to guide owners.

Product analytics & session recordings. To see where people get stuck or give up, we use a product-analytics service (PostHog) that records how our own pages are used: pages viewed, taps and clicks, how far you scroll, and which steps of a guide you reach. It also captures a session recording: a replay of the pages as they appeared and the actions taken in them, reconstructed from your browser. We configure it to mask everything typed into a form (so codes, names, and phone numbers appear as asterisks) and to mask any door or access code that a guide reveals, and pages whose link is itself a private token (a gift claim, an approval request, a sign-in link) are excluded from analytics and recording altogether. If you are signed in, we identify these records by your account's internal id, never by your email or phone number. Recordings are kept by PostHog for a limited retention period and are used only to improve the Service. If your browser sends a "Do Not Track" signal, we disable analytics tracking and session recording for your visit.

Message records. For the text messages we send (verification links and gate-code approval requests) we keep the recipient number, when it was sent, and the delivery status our SMS provider reports back, so we can show you whether a request went through and prevent abuse.

Text messaging. Message frequency varies based on visitor activity (typically a few messages per code request). Message and data rates may apply. You can stop receiving approval texts at any time by removing your number from your guide settings, replying STOP, or contacting us at privacy@mikum.me. Mobile numbers and SMS opt-in consent are never shared with third parties or affiliates for marketing purposes.

Location information

Some guides use an optional feature that reveals a door or access code only once a visitor confirms they are at the location, or once the owner approves. A guide owner may enable this in one of two ways:

Personalizing the guide. When a host enables the location feature, we temporarily access the visitor's device location to determine their position relative to the route: for example, to pre-select the way in you are standing closest to, to pick the nearest parking spot, or to show where you are on the parking map. This data is processed in real time and immediately discarded: it is never stored or logged. Before your browser asks, the guide shows a short notice saying what your location is used for and linking to this policy, and you can always decline the prompt.

Real-time arrival sharing (opt-in, on paid plans). Separately, a guide owner on a paid plan can let visitors share their live arrival time. If you choose to start sharing, your browser asks your permission for your device's precise location, and while you keep the guide open your device's GPS location is sent to our servers at intervals so we can estimate your driving time to the destination. We use it solely to compute that estimate and do not store it: what we record for the visit is the estimated minutes away and the distance, never your coordinates, and that record is removed after the visit. Depending on our infrastructure configuration, computing the estimate may involve a third-party routing provider; in that case only the momentary coordinate is transmitted to that provider, and it is not retained by them. When no routing provider is configured, all computation happens on our own servers. You can decline the browser prompt, and stop sharing at any time by closing the guide.

Gate-code approval requests

If a guide uses owner approval, requesting a code shares information with that guide's owner and approval contacts. We record the name the visitor types; if the visitor is signed in, we instead use the name on their account, along with their organization (if set), their account phone number, and a marker showing they are verified. We text each approval contact a personal link showing who is asking and for which location, and we store the outcome (approved or denied, by whom, and when). Approving a request reveals that location's gated codes to that visitor. We keep these request records so owners have a history of who asked and to detect abuse; we don't use them for anything else.

How we use information

We use information to provide and improve the Service, authenticate you (by email, SMS one-time code, or a sign-in provider), display and share the guides you create, process subscriptions, prevent abuse and secure the Service, and communicate with you about your account. We also send transactional SMS to numbers you add and confirm in mikum.me: gate-code approval requests and one-time number-verification links. SMS verification codes and these transactional texts are used for security and account operation, not marketing; reply STOP to unsubscribe.

AI processing

If you use our AI-assisted features (such as drafting step directions, suggesting annotations, or translating a guide), the relevant content (photos, short video frames, and text) is sent to our AI provider (Anthropic) to generate suggestions that you can review and edit. We don't use your content to train third-party AI models, and AI output can be inaccurate, so please review it before publishing.

How guides are shared

A guide you publish is public: anyone with its link can view its photos, details, and any contact information you added, and published guides can be embedded on other websites through our embed widget or grouped into a directory page. Hidden door and access codes are the exception: they are never included in the public page and are served only after a code-reveal check succeeds. Do not include sensitive information in a guide that you do not want to be publicly visible, and be mindful of other people or property that appear in your photos. You can unpublish or delete a guide at any time; search engines and anyone who saved a copy may retain it for a while afterwards. If you gift or transfer a guide, its content moves to the recipient's account.

Service providers

We rely on trusted third parties to run the Service, and share information with them only as needed:

Published guides also link to third-party navigation apps (such as Google Maps, Waze, and Apple Maps) that open on the viewer's device. Each of these providers processes data under its own privacy policy.

We don't sell your data

We do not sell your personal information, and we don't share it with third parties for their own marketing. Mobile numbers and SMS opt-in consent are never shared with third parties or affiliates for marketing purposes. Advertising on free-plan guides is served by Google AdSense under its own policies.

Cookies & local storage

We use cookies that are necessary to keep you signed in and to operate the Service securely. We also keep a few things in your browser's local and session storage rather than on our servers: the guides you recently opened (so we can show them on the home page), your language preference, and short-lived markers that keep an in-progress guide on the right step. The recent-guides list stays on your device; we only send those links back to check which guides are still published, so deleted ones drop off the list. You can clear all of this at any time in your browser. Free-plan guide pages may include advertising cookies set by Google AdSense. Google and other third-party vendors use these cookies to serve ads based on your prior visits to mikum.me or other websites on the Internet. You can opt out of personalized advertising at Google Ads Settings or at YourAdChoices. Our product-analytics service (PostHog) stores an identifier in a cookie and in local storage so a visit can be counted as one session rather than many. If you are visiting from outside Israel, we ask for your consent before setting analytics or advertising cookies; you can change your choice at any time here: .

International transfers

We and our service providers may process and store information in countries other than the one you live in, including the United States. Where required, we rely on appropriate safeguards for these transfers.

Data retention & deletion

We keep your information for as long as your account is active. Unpublished guest drafts are removed automatically after a period of inactivity. You can delete individual guides at any time, which removes their photos from our storage. You can also delete your whole account from your account settings: that cancels any active subscription and permanently removes your guides, their photos, and your profile, and it can't be undone. Some records are kept longer where we have to, such as billing and tax records held by our payment processor. You can also write to us at privacy@mikum.me (or support@mikum.me) and ask us to delete your account for you. We may first ask you to confirm the request from the email address or phone number on the account, and we'll act on it within one month. Once it's done we send you a written confirmation with a reference number listing what was removed. We keep that confirmation record afterwards as our evidence that your request was carried out.

Security

We use industry-standard measures to protect your information: encrypted connections, database access rules that keep your guides scoped to your account, rate limiting, and gated codes that are never included in a published page. No service can promise perfect security, so please use a secure sign-in method and tell us at privacy@mikum.me if you notice anything wrong.

Legal bases (EEA & UK)

If you are in the European Economic Area or the UK, we process your information to perform our contract with you (creating your account, hosting and sharing your guides, processing payments), with your consent (device location access for a code check, and the text messages you opt into; you can withdraw consent at any time), for our legitimate interests (keeping the Service secure, preventing abuse, and understanding basic usage), and to comply with legal obligations such as tax and accounting rules.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or export your personal information, to object to or restrict certain processing, or to withdraw consent. To exercise these rights, contact us at privacy@mikum.me, including if you simply want to be deleted and would rather not do it yourself in the app. So we don't hand someone else's data over, we may ask you to send the request from the email address or phone number on the account. We reply within one month, and for a deletion request we send written confirmation of what was erased. You may also have the right to complain to your local data protection authority.

Children

The Service is not directed to children under 16, and we do not knowingly collect their personal information.

Language

This Privacy Policy may also be published in other languages. Any such translation is provided for convenience and is intended to be consistent with this English version. In the event of any conflict, inconsistency, or difference of interpretation between a translation and this version, this English version governs, except where applicable law requires otherwise.

Changes

If we make material changes to this Privacy Policy (such as changes that significantly affect how we process your personal data or your rights as a data subject), we will provide at least 30 days' advance notice before those changes take effect, by email to your registered address or by prominent notice within the Service. This is consistent with the notice standard in our Terms of Service.

For non-material changes (such as typographical corrections or clarifications that do not affect your rights), we will update the "Last updated" date at the top of this page. Continued use of the Service after the effective date of any update constitutes your acceptance of the revised Privacy Policy.

Contact

Questions about this policy? Email us at privacy@mikum.me.

Privacy Policy·Terms of Service