Privacy Policy
Last updated: November 20, 2026
Article 1 (Introduction)
This Privacy Policy ("Policy") explains what information the app "meshitelop" (the "Service"), provided by meshitelop (the "Operator"), collects, and how it is used, stored, and shared with third parties. By using the Service, you agree to the terms of this Policy.
Article 2 (Information We Collect: Account and Profile)
At sign-up, we collect your email address, password, display name, and username. Authentication is handled by a third-party provider (Clerk); the Operator's servers never hold your password itself. Your email is used only for sign-in and is never shown on your public profile.
If you sign in with Google, our authentication provider (Clerk) receives and stores the information needed for authentication and account linking, such as your Google account identifier, your name, your email address and its verification status, and the URL of your profile picture. For a new account, part of the name we receive is used as the initial value of your display name. You can change your display name; the display name you register is stored in the Service and shown publicly to other users. When you link Google to an existing account, Clerk may also store your name and similar details. We do not use or display your Google profile picture as your avatar in the Service. The Operator and the Service never receive your Google password. Separately from leaving the Service, you can review and remove the Service's access in the "Third-party connections" section of your Google Account; removing it there alone does not delete your account or posts in the Service. If you sign in with Apple, Clerk receives and stores your Apple account identifier, your name (Apple provides it only the first time), your email address (your real address, or the private relay address Apple issues if you choose "Hide My Email") and its verification status. If you choose "Hide My Email", the relay address is treated as a different email address, so it creates a separate account from any existing account registered with your real address. The Operator and the Service never receive your Apple password. Even after you leave the Service, the connection on the Apple side may remain; you can review and remove it in your Apple Account settings (Sign-In and Security > Sign in with Apple).
Your display name, username, bio, profile photo, and profile banner (a photo set by Plus members) are shown publicly to other users.
Your location (a country/region you pick from a list — your device location is not used) and, for Plus members, links to your other accounts (the username or URL for Instagram, X, TikTok, YouTube, Facebook, or a website) are also shown on your public profile. Opening a link takes you to that service's site.
Your profile photo can be selected from your device's photo library. Doing so uses permission to access the photo you choose.
Article 3 (Information We Collect: Post Photos and Content)
When you create a post, we collect the photo you take (in-app camera only — uploading from your photo library is not supported), the dish name, caption, hashtags, and rating (1–5 stars). Hashtags are shown publicly with your post and can be searched and browsed by other users. Post photos are automatically converted into several sizes (full quality, feed display, and thumbnail) and stored on our servers; any location metadata (EXIF/GPS) embedded in the photo is automatically stripped before upload. On our servers each photo is also decoded and saved again as a new image, so nothing from the original file's metadata can remain.
MeshiMap: for each post you choose to show on your MeshiMap, we store a pin and show it to other users who view your profile. For a Restaurant post, the pin is the restaurant's own location (the coordinates of the venue's public address); for any other post, it is the spot you tap on the map, stored and shown exactly as chosen. Your device's current location is never saved automatically. If you set your MeshiMap to "Only me", other users cannot see it.Even before you press the post button, the photo you took is sent to our server ahead of time and checked, to get your post ready. Photos you do not post are deleted from the server automatically after a while.
Article 4 (Information We Collect: Comments and Direct Messages)
We collect the text of comments on posts and direct messages (DMs) between users. DMs are not end-to-end encrypted (E2EE). Messages are encrypted in transit (e.g., via HTTPS), but are stored and processed on our servers as needed to provide the Service. Only the two participants in a conversation can read it.
Article 5 (Information We Collect: Location Data)
Home posts: we determine only your country/region (e.g., Japan, Tokyo) from your current location and display it publicly on the post. Exact coordinates are never stored or shown.
Restaurant posts and Nearby's nearby search: your current location is used temporarily to search for nearby restaurants. Venue data is fetched from the Operator's own delivery service (Cloudflare) by the numbers of the map tiles that cover your search area. Your exact GPS coordinates are not included in these requests (the delivery service can see the tile number, which reveals your approximate area, and connection details such as your IP address). The Operator's own servers do not receive or store raw location data for this search. Note: apps that have not received this update send your device's raw coordinates directly to a third-party service (OpenStreetMap's Overpass API) for this search.
Municipality name on Restaurant posts: When you create a Restaurant post, the name of the municipality determined from your current location (e.g., Aomori City) is saved with the post and shown publicly, such as on post cards, as a rough indication of where the restaurant is. Exact coordinates are not stored or shown. Because the municipality is based on your location at the time of posting rather than the restaurant's address, a neighboring municipality may be shown near a boundary. Home posts never store or show a municipality name.
Restaurant post check-in verification: your current coordinates are temporarily sent to the Operator's servers to confirm you are at the venue. Only the distance to the venue (in meters, rounded) is recorded — raw coordinates are not stored.
Article 6 (Information We Collect: Social Data)
We collect your follows/followers, likes, blocks, saved-places history, notifications, and any reports you file. If you choose a private account, people you have not approved cannot see your posts, your MeshiMap, or your follower and following lists. We also store follow requests, including those still waiting for approval. If you enable push notifications, we also collect the push token (a string that identifies your device for delivery) and the platform (iOS/Android), and store them linked to your account.
We also store the date you last opened the app (updated once a day), your device's offset from UTC (used to cut days; it is not a location), your app display language (used to word notifications), your "Daily reminder" setting (on by default; you can turn it off any time in Settings > Notifications) and a record of the days a reminder was sent (used to keep to one a day and five in any seven days; entries older than 7 days are removed the next time a reminder is sent), and the MeshiMap opening view you chose (map center and zoom only — not your device location). We use existing data (the number of likes and comments on posts, the posts you liked, the people you follow, the country / region you chose in your profile and the places of your latest posts) to decide the order of posts in the World feed's "For You" tab and each region's "For You", "Restaurants" and "Other" tabs. To avoid showing the same posts again and again, the ids of posts that stayed on your screen for a moment, with how many times you saw each one (counted at most once per 10 minutes), are kept on your device only (the latest 300, for up to 14 days). When the order is requested, the ids of the latest 200 seen posts, and how many times you saw those seen twice or more, are sent to the server, used only for that answer and not kept on the server. To understand usage and running costs, we also record aggregate counts that do not identify you, such as posts, active users, likes, and translations per day.
If you use Plus (monthly or yearly) or tip the developer, the purchase is processed by Apple (App Store) and the purchase status is managed with RevenueCat. We receive from RevenueCat, and store, an internal ID that identifies your account, the product purchased, the expiry date and the purchase status (trial, renewal, cancellation, refund, etc.). Payment details such as card numbers are not sent to us.
Usage statistics (optional): only if you agree, to count how the app is used, the app sends our server, in batches, which screens you viewed and for how long, the number of times you do a few things (take a photo, share, open a notification, see and like For You posts, etc.), and your device generation, OS version and app version. No outside analytics service is used. We store only daily totals (counts and seconds), not a usage history per user name or account (only a temporary marker, tied to your account and deleted within 2 to 3 days, so nothing is counted twice). You can use every feature without agreeing. You can stop any time in Settings > Privacy; when you stop, sending stops and anything not yet sent is discarded. Whether you agreed is recorded on your account.
User counts (optional): separately from the usage statistics, and only if you agree, we count you in our user numbers: how many people used the app each day, week and month, how many per country or region, and the share of people still using it N days after signing up (only people who agreed on the day they signed up). For this we use the last day you opened the app and the country/region you chose in your profile. The results are only numbers of people, without user names, and groups of fewer than 5 people are not shown. You can use every feature without agreeing. You can stop any time in Settings > Privacy; when you stop, you are not counted from the next count on. Whether you agreed is recorded on your account.
Gender (optional): if you agreed to the user counts, you can answer your gender (male, female, other) at sign-up or later in Settings. You can use every feature without answering. It is used only for the monthly user counts, and is counted only in months when at least 30 people answered. It is never shown to other users, and you can change or erase it any time. If you stop agreeing to the user counts, your gender answer is erased too. We do not guess gender from names or photos.
Article 7 (Information We Do Not Collect)
The Service does not use advertising tracking technology or outside analytics services (e.g., Google Analytics, Meta Pixel). Detailed usage statistics (screens, device and so on) and the user counts (daily and monthly users, users per country or region, the share who keep using the app, and gender) are counted only inside the operator's own server, and each only if you agree to it (see Article 6). Aggregate operating counts that do not identify you, such as posts and users per day, are recorded as described in Article 6. We do not collect or verify birthdate or age (see Article 11).
Article 8 (How We Use Information)
We use the information we collect to:
• Provide and operate the Service (posting, feed, DMs, and other core features)
• Search for nearby restaurants and verify check-ins to support post authenticity
• Show where a post is from (country/region, and the municipality for Restaurant posts)
• Deliver push notifications
• Provide caption/comment translation
• Understand usage and running costs through aggregate counts that do not identify you
• Improve the Service through usage statistics and user counts, only from people who agreed
• Respond to abuse and reports
• Provide customer support
Article 9 (Third-Party Sharing)
The Service relies on the following third-party services, each receiving only the data needed for its function:
• Clerk (authentication): account identifier, email, display name, username, and authentication/session information. For email-and-password sign-up, the password is managed by Clerk. If you sign in with Google, also the account identifier, name, email address and its verification status, and profile picture URL received from Google, and similar details. If you sign in with Apple, also the account identifier, name (first time only) and email address (real or relay) with its verification status received from Apple
• Google ("Sign in with Google"): the authentication request and connection details such as your IP address. As part of signing in with Google, information such as your Google account identifier, name, email address and profile picture is passed to Clerk for authentication. How Google handles information is described in Google's Privacy Policy.
• Apple ("Sign in with Apple"): the authentication request and connection details such as your IP address. As part of signing in with Apple, your Apple account identifier, name (first time only) and email address (or relay address) are passed to Clerk for authentication. How Apple handles information is described in Apple's Privacy Policy.
• Convex (database/backend): all data described in this Policy
• Cloudflare (image storage and delivery: R2, and delivery through our own domain): post photos, profile photo and banner (all sizes), and connection details when images are viewed (such as IP address), and connection details when venue data is fetched (the identifier of the map tile for the search area, which reveals your approximate region, and your IP address; your exact latitude and longitude are never included in these requests)
• OpenStreetMap Overpass API: current-location coordinates (apps that have not received this update only, sent directly from your device; updated apps do not use it)
• OpenStreetMap Nominatim: public venue identifiers only (no user location)
• OpenFreeMap (OpenStreetMap map-data delivery): map data requests to display the MeshiMap (the map area being viewed and your device's IP address are sent; your current location is not)
• Location and address-lookup features provided by your device's operating system (Apple on iOS, Google on Android): your current coordinates (which may be sent directly from your device to determine the country/region and municipality name at posting time)
• Anthropic (the Claude AI model): (1) Translation: caption, comment, dish-name and bio text and the target language (only when you tap "translate"). Translation results are kept on our servers for up to 30 days so the same text need not be translated again (the original text itself is not stored, and results are not linked to you). (2) Automatic detection of inappropriate content: the text of posts, comments, display names, usernames, bios and links, and post photos (through their public URLs). No other user information, such as your email address, is sent.
• Apple (App Store / payments): processing of Plus and tip purchases (we do not receive card details)
• RevenueCat (purchase status): internal account ID, product purchased, expiry date and purchase status, and connection details (such as IP address)
• Expo / EAS: information needed to deliver and update the app
• Expo Push Notification Service (and Apple APNs / Google FCM): push token, notification text (which may include usernames), and accompanying data such as post identifiers
・Overture Maps Foundation (venue data): venue data is served from the Operator's own storage. No user information or location is sent to Overture.
We do not sell your information or share it with third parties for advertising purposes. Because these third-party servers may be located in the United States or other countries, your data may be processed across national borders as part of using the Service.
Article 10 (Content Management and Reporting)
We provide reporting for posts, comments, and users, as well as a feature to block specific users. Reports are reviewed by the Operator and acted on as needed. The fact that you filed a report is not disclosed to the reported user. To find inappropriate content, posts (photo and text), comments, display names, usernames, bios and links are checked automatically by an external AI (Anthropic). Anything suspicious is queued for the Operator to review; nothing is hidden or removed automatically — the Operator reviews it and then decides.
What the Operator can see is limited to the content of reported posts, comments and users, and the public profile (display name, avatar, post count) shown when searching a username. The contents of a reported conversation (DM) are not shown on the Operator's screen. As a response, we may remove posts or comments or temporarily suspend an account, and we keep a record of the action (time, target, and a copy of the removed text). A suspended account can still view content but cannot post, comment, change its profile, or otherwise write.
Venue reports: from a venue's page you can report that it has closed or that its information is wrong (name, location, or other details). We store who reported, the venue's identifier and name, the type of report, and the time. There is no free-text field. A venue reported as closed by three different users may be removed automatically from lists (Nearby and the venue picker) before review, and the Operator may restore it after checking. The identity of the reporter is not shown to other users.
Article 11 (Children's Privacy)
The Service is not directed at children under 13. However, we do not currently have a technical mechanism to verify age. If we learn that a user under 13 has used the Service, we will promptly delete the associated data. If you are a parent or guardian and become aware that your child is using the Service, please contact us using the information in Article 16.
Article 12 (Data Retention and Deletion)
When a user deletes their account, the following data is promptly deleted: posts and photos (all sizes), MeshiMap pins, comments, likes, saved-places history, follow/follower relationships, blocks, notifications, restaurant check-in records, the Operator's moderation records about that user, and profile information (including the banner photo).
Note: Because DMs are stored per conversation, deleting your account deletes the entire message history of every conversation you were part of — including messages sent by the other participant.
Records of actions taken by the Operator (date, target, and the Operator's own identifier) may be kept for audit purposes separately from the deletion of the person they concern. To stop a profile from being created again from a login account after its data was deleted, the identifier of the deleted login account is stored for up to 90 days. The identifier of a login account that has ever been suspended is stored without a time limit, to prevent registering again to evade a suspension.
Some information may remain in backups for a limited time after deletion for legal-compliance or anti-abuse purposes. Logs and backups held by third-party providers (Clerk, Convex, Google, etc.) are subject to their own respective policies.
The results of the usage statistics and user counts (numbers that cannot be traced to anyone) remain after you stop agreeing or delete your account.
Article 13 (Your Rights)
You can view and edit your profile information, and delete your account, at any time from the app's Settings screen. For requests regarding access, correction, or deletion of your data, please contact us using the information in Article 16.
Article 14 (Security)
The Service employs industry-standard technical and organizational safeguards (including encryption in transit), but no system can be guaranteed to be completely secure.
Article 15 (Changes to This Policy)
This Policy may be updated to reflect changes in law or in the Service. We will provide notice of material changes through the app or other appropriate means.
Article 16 (Contact Us)
If you have questions or requests regarding this Policy, please contact us at meshitelop@gmail.com.
