Privacy Notice

Last updated: November 20, 2026

What changed: Optional analytics now also counts which landmark models generated maps include. Only the landmark names are sent, with nothing else about the map, and they are kept as daily totals per landmark with no identifiers. It also counts when a mouse or pen rests on a link or button that leads to the seller license. A new section, Text messages, says that Mini Skyline sends automated texts only to its owner’s phone to report a new donation, and does not collect phone numbers for texting.

Mini Skyline is run by Joseph Olson, who is the controller for this service. For privacy questions, access requests, deletion requests, objections, or showcase-removal requests, email support@miniskyline.com.

Privacy choices

Current setting: necessary only. You can change this any time on this page.

What stays in your browser

In the Cloudflare-hosted app, browser Web Workers build the preview mesh, generated model file, Project Mode pieces, and project ZIP on your device. Workspace drafts and autosaves, GPX routes, custom buildings and linework, terrain paint, Map Text, color presets you have not shared, and generated model files remain in browser storage, active-tab memory, or downloads you control. Mini Skyline does not host a generated model, Project Mode piece, or normal export file, and keeps a restorable workspace only when you save a project to your account or tick the project file box on an issue report (kept for 30 days, described below). Network requests and operational records can still contain the limited selection and settings information described below, but they do not contain the generated mesh or archive file.

Generated Project Mode buffers exist only during the active browser session and are cleared when that session ends. Downloaded workspaces, presets, model files, and project ZIPs remain under your control until you move, share, or delete them or your browser clears its local data.

Data Mini Skyline receives and stores

Ordinary requests to the site and same-origin APIs can expose the request time, URL, IP address, user agent, referrer, and security or rate-limit metadata to Cloudflare. Necessary generation lifecycle records can include selection bounds and shape, a location label or country, selected mode and settings summaries, action, phase, status, timings, model or feature counts, provider summaries, app/browser revision, random job or session identifiers, and a daily visitor key. These records support generation, capacity planning, reliability, abuse prevention, and aggregate usage counts. They do not store a restorable project or generated model file.

The daily visitor key is derived, not random. Mini Skyline’s server combines the request’s IP address, user agent, and the current date with a random value made for that day alone and stores only the resulting hash; neither the IP address nor the full user agent is kept in the record. The random value is thrown away soon after the day ends, so not even Mini Skyline can work out a past day’s keys. The key is pseudonymous: it does not show who you are, but it is still personal data. Because the date is part of the calculation, the key is new every day and does not link one day’s activity to another day’s. It exists so aggregate counts can tell how many people generated apart from how many runs they made, and the same key distinguishes unique visitors in the optional visit counts. Mini Skyline cannot look up which key was yours, so an access or deletion request usually cannot be matched to it; it is deleted on the retention schedule below.

Mini Skyline’s operator can ask for a live count of how many people have the site open. Outside a count, each open tab only checks about once a minute whether a count is running; that check sends nothing about you and is not recorded. During a count, which lasts about a minute and a half, each open tab answers once with a random number made for that count and whether the page is on screen. If you allow analytics and diagnostics, your browser’s tabs share that number, so you are counted once; otherwise each tab keeps its own: in the page’s memory before you answer the privacy banner, and in session storage after “Necessary only”. This happens whatever your privacy choice, because the answer carries nothing that identifies you or links it to anything else. When the count ends the answers are deleted and only the two totals are kept.

Each landmark page lets you download that landmark’s model, up to five a day per device and a fixed number a day for the whole site. To count them, Mini Skyline stores one row per download: the landmark, the day and time, a salted hash of your IP address and a salted hash of a random ID your browser keeps in local storage. Neither your IP address nor the ID itself is stored, and the hashes are used only to count downloads. The rows are deleted after 30 days.

When you share a color preset with the community, Mini Skyline stores what you share: its name, the credit name you choose, its colors, the preview picture if you include one, and when you shared it. It is public as soon as you share it, and the operator removes ones that do not belong. The preview picture is public with it; the operator takes down a picture that does not belong, and a picture taken down is not shown again and is deleted after 30 days. To limit how many presets one network can share in a day, Mini Skyline also stores a salted hash of your IP address with the share, never the address itself; that hash is blanked 30 days after you share. If you share while signed in, the preset is also linked to your account. The share also records which version of the Terms of Use you accepted by sharing it, and when.

When you ask for something on the request board (/requests), Mini Skyline stores what you send: whether it is a landmark or a feature, its title, any details you add, when you sent it and, for a landmark, the map view you were looking at. The landmark request window on the map also files the place you name there as a landmark request, with that map view. A request is shown only after the operator has read it. From then on its title, details, map view and vote count are public, and the operator may edit it, merge it with another request, decline it or remove it, so do not put personal details in a request. While a request waits to be read, Mini Skyline keeps a salted hash of your IP address with it, so one network cannot leave many requests waiting; the hash is blanked when the request is read. Sending a request counts as your vote for it. A vote stores the time, a salted hash of a random ID your browser keeps in local storage, so each browser votes once and can take its vote back, and a salted hash of your IP address, so one network cannot add many votes. Neither the ID nor your IP address is stored. Your browser also keeps in local storage the list of requests it voted for. Mini Skyline relies on service necessity to show the requests you send and on legitimate interests for these hashes. A declined, removed or merged request is deleted with its votes 90 days after that decision; Retention, below, lists every period. To report a request, use the Report link next to it. The report form, its bot check, what a report stores and how long it is kept are the same as for a report about a shared preset, described below.

If you contact support, share a make, or report an issue, Mini Skyline collects the information you send: name, optional email address, subject, message, topic, public photo or post link, showcase consent, map bounds, a screenshot of the 3D preview unless you untick its box, which starts ticked, and your project file only if you tick its box, which starts empty. Both boxes start this way every time. An issue report also sends the ID of the model run it is about; a report about a failed model also sends the error and the generation log (the steps, timings and settings of that run). The landmark request and landmark report windows send what you type (the place or building, the problem and details), an optional email address for a reply, the site language and the map view you were looking at. All of these reach Mini Skyline as email: sent through Resend, received through Cloudflare Email Routing, and kept in the operator’s mailbox at Mini Skyline’s email provider. A project file is the same file Save writes: the selected area and its shape, the map view, your settings, the model and place names, and anything you added, such as GPX routes, transit routes, custom buildings, drawn lines, terrain paint, Map Text and the positions of models you imported (not the model files themselves). It is not sent by email. Mini Skyline keeps it in private Cloudflare R2 storage, the report email holds only a link to it, and only the operator can open that link, through the signed-in operator dashboard. It is used only to reproduce and fix the problem you reported, and it is deleted 30 days after the report, or sooner if you ask.

If you report a shared preset, its name, description, credit name or picture, or a username, Mini Skyline stores the reason, what the report is about, your explanation, your email if you give one (needed for a copyright report), the language you use the site in and your confirmation that the report is accurate, together with which shared preset it is about — nothing else about you and no IP address. Reports and moderation decisions, below, says how these are used.

If you publicly support Mini Skyline through Buy Me a Coffee, the hosted app may store the sanitized display name, formatted support amount, currency, support date, public/private visibility state, refund state, and a bounded non-hidden support message. If your support is public, its name, amount and message are shown on miniskyline.com (in the supporter banner, in a thank-you pop-up for visitors and in the site’s public list of recent supporters) and in the Discord supporter feed, and its name is shown on the banners in the loading scenes. A member’s name is also listed on the Members page and at the top of the Attributions page, with the kind of membership (monthly or annual) and the month it began. The supporter who gave the most in the last 30 days is named as the top supporter, with that total. Mini Skyline treats a support as public when Buy Me a Coffee marks it public or, where Buy Me a Coffee sends no such mark, when it passes on a display name that is not marked anonymous, private or hidden. A supporter appears only after operator approval. To have your name taken off, email support@miniskyline.com. When the supporter-notification integration is configured, that approval also sends the approved display name, formatted amount, support date, and non-hidden message to Mini Skyline’s public Discord discussion channel. Pending, rejected, private, refunded, or hidden-message supports are not sent. Mini Skyline does not store Buy Me a Coffee emails, country, referer, payment platform, transaction ID, hidden messages, or raw webhook payloads for that banner or Discord notification. When the operator turns a supporter down or removes one, the decision is kept with a short reason, and a removed supporter’s Discord post is deleted.

When you support Mini Skyline through Buy Me a Coffee or PayPal, the hosted app uses the email address Buy Me a Coffee or PayPal sends with that payment to email you a supporter code, and keeps it with the code so support can find, resend or move a code you have lost. For PayPal it also keeps a keyed hash of the transaction ID, so a refund can cancel the code; it does not store the transaction ID itself, the name on your PayPal account, your address or the amount. It is shown only in Mini Skyline’s private operator dashboard. A supporter code hides the support prompts on the devices it is entered on. Mini Skyline stores a keyed hash of each code, whether it was emailed or made by the operator, and a keyed hash of a random device ID for each device the code is entered on (up to 20), with the dates it was first and last checked. It also keeps the last two characters of each code, so your account page can tell your codes apart; on their own they are not enough to use a code. Your browser keeps the code and that random ID in local storage; neither identifies you, and clearing site data removes them.

When you report a problem or ask for a feature in Mini Skyline’s Discord server, the Updates page (/updates) may credit the change to your Discord display name, as “Reported by” or “Requested by”. Mini Skyline keeps only that display name, with the patch note it belongs to. To have your name taken off, email support@miniskyline.com or ask in Discord.

If you donated through PayPal, you may choose a display name for the submarine flag in Mini Skyline’s loading animation on the PayPal thank-you page (/thanks/paypal), using the supporter code from your email. This is optional, and Mini Skyline never shows the name on your PayPal account: only a name you type there, with the box ticked to show it publicly. It stores that name, when you ticked the box, which supporter code it belongs to, and the operator’s decision with its reason. The name is shown only after the operator approves it. To have it removed, email support@miniskyline.com; it is then deleted.

Accounts

An account is optional; everything else on Mini Skyline works without one. If you create one, Mini Skyline stores your email address, the username you pick, which is shown on things you share, when the account was created and last signed in, and, if you sign in with Google, the account number Google gives Mini Skyline for you. Presets you save to your account, color presets you mark as favorites and supporter codes you tie to it are stored with it, and color presets you share while signed in are linked to it so you can follow their review and withdraw them. Saved presets are an exception to what stays in your browser: a saved print preset holds a place (the area you selected and its name) and the settings it is made with, and it is not shown to anyone else. Your routes, drawn buildings and lines, terrain paint, map text, imported models and frame or keychain text are never part of a shared preset, and are saved to your account only when you save a project or a frame preset there. A picture you add to a share is different: it shows your model as the preview shows it, so any routes, map text and frame text on the model are visible in it. When you change your username, or delete the account, the old username is kept for 30 days so nobody else can take it, then deleted. Mini Skyline also stores which version of the Terms of Use you accepted when you created the account, and when.

Your account email is used to sign you in, send you sign-in codes, find supporter codes bought with it and answer you when you contact support. It is never shown publicly and never sold, and Mini Skyline does not send you newsletters or marketing email unless you choose to receive them. Account data goes only to the providers named here that run sign-in (Cloudflare, Resend and, if you use it, Google). You must be at least 13 to make an account.

Signing in by email: Mini Skyline sends you a six-digit code by email through Resend. Only a keyed hash of the code is stored, for ten minutes, with how many codes were sent to the address in the last hour and how many wrong codes were tried in the last day; those counts stop people guessing codes and are kept for about a day. Signing in with Google: Google tells Mini Skyline your email address and whether Google has checked it. Mini Skyline never receives your Google password or contacts, and Google's own privacy policy covers your Google account. Before a code is sent, and before you share or send something, Cloudflare Turnstile checks that a person rather than a program is asking; it runs in your browser and sends Cloudflare what it needs for that check.

Signing in puts a sign-in cookie in your browser. Mini Skyline stores only a hash of it, with when it was made and last used. A sign-in ends after 60 days without use, or when you sign out. While you sign in with Google, a second cookie holds the sign-in check for up to ten minutes. Both are needed to sign in, and neither is used for advertising or analytics.

A supporter code is tied to your account only when you ask, and only if it was bought with your account's email. A tied code then works only while you are signed in, on any device, without counting against its device limit. Mini Skyline's operator can see which account a code is tied to and can move a code to another account, for example if you lose access to an email address.

For EU, UK and similar laws, accounts and what you save, share or send rely on providing the service you ask for; the bot check and the limits on codes and guesses rely on Mini Skyline's legitimate interest in keeping accounts safe.

Sharing presets with the community

When you share a print preset or settings profile, Mini Skyline stores what you share: its name, description and credit name, its settings, the place (the selected area and its name) for a print preset, and the preview picture if you include one. It is public as soon as you share it: anyone can see its name, description, credit name, place and picture, open it and make their own model from it, and the library shows how often it has been opened. Mini Skyline's operator looks over new shares, sees your account email and username next to them, and removes ones that do not belong. Your email is never shown. You can withdraw a share on your account page: it leaves the library at once, its picture is deleted and the rest is kept as a record of what was removed. 90 days after a share is withdrawn or removed, everything but a bare record (its ID, the reason and the dates) is deleted, and that record goes after 12 months. If Mini Skyline removes your share, your account page shows the reason and how to ask for another look. The picture is checked automatically when you share it: only the picture is sent to an AI model that runs on Cloudflare (Workers AI), which answers whether it shows anything unsafe, such as nudity, gore or hate symbols, and whether it is a picture of a map model; that answer is stored with the share. A picture the check finds unsafe is not shown, your account page tells you why, and it is deleted after 30 days. A picture the check could not look at, because it failed or did not answer, stays hidden and is checked again every 15 minutes until it has been looked at. Any other picture is public straight away. This check relies on Mini Skyline's legitimate interest in keeping unsafe pictures off the site. Each share also records which version of the Terms of Use you accepted by sharing it, and when.

Sending landmarks

When you send a landmark, Mini Skyline stores the file you send (a kit return or a 3D model), the landmark's name, place and location, your notes and source links, your credit name, and when you agreed to the rights statement. Files are kept privately in Cloudflare storage and are never published as sent. Mini Skyline's operator reviews them and sees your account email next to them. An accepted landmark can become part of the models Mini Skyline makes. Withdrawing a landmark that is not yet accepted deletes its file. The file and the submission are deleted 12 months after the final decision; for an accepted landmark, a short record of the rights you granted is kept.

Settings saved to your account

If you are signed in, the site settings that follow your account are stored with it, so they are the same in every browser where you sign in: the theme, language, text size, motion and tooltip timing, the start page, map settings such as the imagery, map views and projections, the places in your map search history, your keyboard shortcuts, the editor's layout choices, your filament list, saved print sizes and preview views, and which tips and tours you have closed. Each is stored with the time it last changed. Settings that only describe one computer, such as how much of it a model may use while it is made, and your privacy choices stay in that browser. Clearing recent places on the Settings page clears them on every device; your favorite places stay. These settings are deleted with your account. While you are signed in, that browser also keeps a list of the last areas you made a model of, for your account page; it is not stored with your account. Signing out removes your map search history, the place the map opens on and that list from that browser; your other settings stay in it.

Projects saved to your account

When you save a project to your account, Mini Skyline stores the whole project file in private storage at Cloudflare (R2): the selected area and its name, every setting, and anything you added, such as GPX routes, drawn buildings and lines, map text, terrain paint and imported 3D models, with its preview picture if it has one, its size and a checksum. Only you can open it. Mini Skyline's operator does not look at it or share it, and it is used for nothing else. A project can be up to 25 MB, and an account can hold 50 projects or 250 MB. A project is kept until you delete it or your account. Projects saved to a folder on your computer are uploaded only if you copy one to your account. Saved projects are not a backup: keep your own copy of any project you can't afford to lose.

Seller licenses

If you buy a seller license, Stripe takes the payment and is the seller of record for it. Stripe receives your name, email address, billing country and payment details, adds sales tax or VAT where it applies, and sends the receipt. Mini Skyline never sees or stores your card number. With your account, Mini Skyline keeps the license number, how it was paid for, the start and end dates, Stripe's customer and payment references, and which version of the Terms of Use you agreed to at checkout and when. For a monthly or yearly plan bought earlier it also keeps the plan, the renewal date and Stripe's subscription reference, and Stripe sends the renewal reminders. These stay with your account, also after a license ends, until you delete the account; deleting it cancels a monthly or yearly plan that is still running first. Stripe keeps its own payment records for as long as the law requires. For EU, UK and similar laws, this relies on the contract you enter by buying a license.

Anyone who has a license number can ask Mini Skyline whether that license is active and the name it is held under: your approved shop name or, without one, your username.

If you choose to list your shop on the licensed sellers list, its name, link, where it ships, the country it is based in, its one-line description, what it sells, the contact you give for custom orders, a contact email and phone number if you give them, its logo and the photos you add are public once Mini Skyline's operator has approved them, for as long as your switch is on and the license is active. Your browser encodes each picture again before sending it, which leaves out the location and device data a camera stores, and Mini Skyline refuses or strips a file that still carries any. A picture may also be checked automatically for unsafe content by Cloudflare Workers AI before the operator looks at it. The entry and its pictures are stored at Cloudflare. A picture is deleted when you remove it; the entry is hidden when you turn the switch off or the license ends, and is deleted with your account. If you trade under your own name, that name is personal data and is shown only because you chose to list it. Do not add photos that show people.

If you report a listed shop, Mini Skyline stores which shop, the reason, your explanation and your email address if you give one, and sends them to the operator by email. The report form uses Cloudflare Turnstile to check that a person is asking. Mini Skyline keeps the report and what was decided as the record of why a shop stayed on the list or was taken off it.

Reports and moderation decisions

When you report something shared, Mini Skyline uses the email you give, if any, only to send you a receipt and later the decision, and stores the language you use the site in so those emails are written in it. At most three receipts a day go to one address; that limit is counted from the reports themselves and stores nothing extra. When a report arrives, Mini Skyline's operator gets an email at support@miniskyline.com with the reason, your explanation, which share it is about and whether you gave an email (not the address itself); it is kept like other support email, for up to 24 months. When Mini Skyline refuses, removes or restricts something you shared, it keeps a record of the decision: which share and which part (the whole share, its picture or its credit name), the ground and any note, whether a person or an automatic check decided, when, the report it answered, whether you were emailed, and the link to your account. That record shows you the decision on your account page and is what a person looks at again if you ask. If you have an account, Mini Skyline also stores the language you last shared in, only so that these decisions reach you in that language; it is deleted with the account. A decision record is kept for 12 months after the decision; its link to your account is removed after 90 days, or straight away when you delete the account. Reports, with the email you gave, are kept for 12 months after they are closed. This relies on Mini Skyline's legal duty to handle reports and explain its decisions (EU Digital Services Act, Articles 16 and 17).

Keeping and deleting account data

Your account and what is stored with it are kept until you delete the account; Mini Skyline does not yet delete unused accounts on its own. You can delete your account at any time on the account page. That straight away removes the account, its sign-ins, saved presets, favorites and code ties (tied codes then work without an account again), deletes anything you shared that is still waiting for review, and withdraws landmarks you sent that are not yet accepted and deletes their files. Presets already public and landmarks already accepted stay under their credit name with no link to your account; email support to have those removed as well, or for a copy of what your account holds.

How data is used

Data is used to operate the site and provider requests, run accounts you choose to create, show presets you share, track generation lifecycle and reliability, prevent abuse, diagnose failures, answer support requests, show aggregate usage counts and approved recent public supporters, send supporter codes, improve capacity planning, and publish makes only when you consent.

Legal bases

For EU, UK, and similar privacy frameworks, Mini Skyline relies on service necessity to operate requested previews, exports, provider access, shared presets, supporter codes, support, security, and abuse prevention; consent for optional analytics (including Cloudflare Web Analytics), client-error diagnostics, showcase use, showing your approved support publicly on the site and in Discord (your choice to make your support public), and showing a PayPal flag name you chose; legitimate interests for minimal generation lifecycle records, service reliability, aggregate planning, the anonymous tally of privacy-banner outcomes and the consent-state report, the operator’s on-demand live count, the screenshot and project file sent with an issue report (to reproduce and fix the problem you reported), crediting a Discord display name on the Updates page (to thank the people whose reports and requests shaped a release), the bot check, and the salted network hash that limits preset sharing; and legal obligations where records must be preserved or disclosed. You can object to any processing based on legitimate interests (see Your right to object).

Your right to object

You have the right to object, at any time and on grounds relating to your particular situation, to processing of your personal data that is based on legitimate interests (listed under Legal bases). Email support@miniskyline.com. Mini Skyline then stops that processing of your data unless it has compelling legitimate grounds that override your interests, rights and freedoms, or needs it to establish, exercise or defend legal claims.

Optional analytics and diagnostics

Mini Skyline’s visit counts, browser provider-usage telemetry, outbound link-click metrics, and client-error diagnostics are optional. One choice covers both: “Allow analytics and diagnostics” turns on the analytics and the error diagnostics described here, and “Necessary only” turns both off. Analytics also covers the export-dialog and other click funnels, the browser-session count and the Minecraft steps; error diagnostics also covers renderer-crash reports and device details such as CPU cores, device memory and memory limits, which are not sent without it. When analytics is allowed and a map you generate includes landmark models, the browser sends the names of those landmarks and nothing else about the map: not its place, its outline or your settings. They are added to daily totals per landmark, which hold no visitor key, IP address, account or other identifier. Analytics also counts when a mouse or pen rests for half a second on a link or button that leads to the seller license, once per button per page load; these counts are kept like the link-click metrics. Choosing "necessary only" keeps the app usable while preventing those app-controlled browser telemetry calls, apart from the anonymous banner tally described next. Necessary generation lifecycle records and request records used to operate same-origin API routes, providers, security, and rate limits may still be created.

Whatever you choose, Mini Skyline counts how the privacy banner was used: that it was shown, and whether it was accepted, declined, or later changed. Each count is a single event name added to a daily total. It carries no visitor key, IP address, user agent, or other identifier, and no individual record is stored, so your answer cannot be linked to you or to anything else you do. While the banner is unanswered, the page keeps only the date it last reported the banner, in its own memory and not in your browser’s storage, so moving between pages of the app does not count it again; reloading the page can. The tally exists to show how many people accept and how many decline. Separately, whatever you choose, each browser reports which of three states it is in: analytics allowed, necessary only, or not yet answered. It does so once per day, week and month it opens the app, and again if its state changes. A report is a state and a period added to a total; it carries no visitor key, IP address, user agent, or other identifier. The browser keeps a small record of what it last reported so it does not report the same thing again: in the page’s memory until you answer the banner, then in the tab’s session storage after “Necessary only”, or in local storage if you allow analytics and diagnostics, so each such browser is counted once per period.

When analytics is allowed, the browser also keeps the date of its first visit in local storage so visit counts can tell new visitors from returning ones. Only the label "new" or "returning" is sent; the date stays in the browser, and choosing "necessary only" deletes it.

Cloudflare Web Analytics (RUM), which measures how fast pages load, is part of analytics: the app loads Cloudflare’s beacon only after you choose “Allow analytics and diagnostics”, and never after “Necessary only” (a change takes effect from the next page load). The beacon reads page-load timings, the page address and browser details. Cloudflare’s RUM documentation (https://developers.cloudflare.com/speed/observatory/rum-beacon/) describes it as cookie-free performance measurement that does not read browser storage and discards the source IP at the nearest Cloudflare data center. Cloudflare controls its fields, retention, and account settings. This choice does not control Cloudflare’s ordinary edge request processing.

Processors and providers

Mini Skyline uses Cloudflare for public hosting, Worker APIs, D1 storage (accounts, sign-ins, saved and shared presets, supporter codes, telemetry and support records), R2 and KV storage and caching, dashboard access control, Cloudflare Turnstile, Workers AI (the automatic check of a picture shared with a print preset or settings profile), Cloudflare Web Analytics (only if you allow analytics), Workers Logs and request traces, Network Error Logging, and Cloudflare Email Routing for the support address; Google for Sign in with Google; Resend for sign-in codes and for support, makes, and supporter-code emails when email sending is enabled; Mini Skyline’s email provider for the support mailbox; Buy Me a Coffee webhook delivery for supporter data; and PayPal payment notifications for PayPal donations. Discord receives the approved public display name, formatted amount, support date, and non-hidden support message when the discussion-channel notification is enabled.

Cloudflare Turnstile runs in your browser before a sign-in code is sent and before you share a preset, report a shared preset or send a landmark, to check that a person rather than a program is asking. It sends Cloudflare what it needs for that check, under Cloudflare’s own privacy terms.

To run and debug the Worker, Cloudflare also keeps Workers Logs (see Retention) and a sample of 1% of request traces: the timings of a request and the addresses the Worker called to answer it, kept by Cloudflare for a short time. Cloudflare’s Network Error Logging makes your browser keep a reporting setting for this site for up to 7 days; only if a request to the site fails because of a network error does your browser send Cloudflare a short report (the address, the type of error and your IP address). Mini Skyline does not receive those reports.

Place search: the search bar’s suggestions and searches are sent by the Mini Skyline Worker to Esri’s ArcGIS geocoding service with the text you typed and the site language. Esri’s terms do not allow the results to be stored, and the Worker does not cache them. Naming a point on the map, the filtered search tabs such as Boundaries and Airports, the stops you type for a route between places, and any search Esri cannot answer go to Photon, a search service built on OpenStreetMap data, with the search text or rounded coordinates the request needs. The Worker makes these requests, so Esri and Photon receive the Worker’s request, not your IP address. The link server that lets AI assistants search places and build map links does the same with Photon, and when Photon fails or is slow it asks OpenStreetMap Nominatim instead, with the search text and language; Nominatim also receives only the Worker’s request.

The browser may request OpenFreeMap/OpenMapTiles map assets derived from OpenStreetMap, pinned Overture PMTiles ranges, Mapterhorn elevation and coverage tiles, Terrarium/Mapzen fallback elevation tiles, NASA/USGS planetary tiles or DEMs, OpenStreetMap details such as bridge structures from the public Overpass API (overpass-api.de), and other public data needed for a feature you turn on, such as LiDAR point clouds (USGS, NOAA, Natural Resources Canada), sea-floor depths (NOAA, EMODnet), tree canopy heights (Meta and WRI, through Source Cooperative), and Wikipedia and Wikimedia Commons for the landmark kit. The homepage trailer loads YouTube’s privacy-enhanced player (youtube-nocookie.com) only after you press play; Google then receives your IP address and browser details, and the player can store data in your browser, under Google’s privacy policy. The Mars close-up map view requests the Murray Lab CTX mosaic tiles directly from Esri’s planetary tile service (astro.arcgis.com), which then receives your IP address, the map tiles you view, and referrer/browser request metadata under Esri’s own privacy terms. Those providers can receive search terms, tile coordinates, map bounds, approximate coordinates, IP address, and referrer/browser request metadata needed to answer the request. Their own privacy and retention terms also apply.

Aerial photos: when the Satellite map view is on, government aerial photos (credited on the map) are fetched and cached by the Mini Skyline Worker, so for those photos the agencies see only the Worker’s requests. The aerial-photo features that find pools, ponds, dry riverbeds and similar details work differently: your browser fetches those photos itself, from USGS NAIP (imagery.nationalmap.gov) in the United States, PDOK (service.pdok.nl) in the Netherlands, and IGN’s Géoplateforme (data.geopf.fr) in France. Those agencies then receive your IP address, the photo area being read, and referrer/browser request metadata under their own terms. Where no government photos exist for the Satellite view, the browser requests Esri World Imagery tiles directly from Esri (ArcGIS), which then receives your IP address, the map tiles you view, and referrer/browser request metadata under Esri’s own privacy terms. The Worker starts that Esri session for your browser; no account or personal data is sent to Esri by Mini Skyline.

The desktop app

The Mini Skyline desktop app runs the same app on your computer and makes the same map and data requests as the website. About five seconds after it opens, and then at most every six hours while it stays open, it downloads the update file data.miniskyline.com/desktop/latest.json to see whether a new version is out. That request reaches Cloudflare with your IP address and the app version, and it happens whether or not you share usage statistics. You can switch it off with the app’s “Check for updates” setting (or by turning the online service off); then the app makes no update request. Mini Skyline counts these checks only by hour and app version, from Cloudflare’s request analytics; nothing in them identifies you.

The app asks whether you want to share usage statistics, and they stay off unless you turn them on. When they are on, the app sends the optional analytics and diagnostics described above; when they are off, it sends none of them.

Retention

Raw Cloudflare D1 telemetry, including generation lifecycle, client-error, and link-click records, defaults to seven-day retention. Derived activity buckets keep a 32-day buffer for 30-day trend views. The privacy-banner tallies are counters with no identifiers: daily, weekly, and monthly totals are kept for 400 days, and a single running total of browsers by state is kept without a time limit. Aggregate generation counts may be retained longer without user-specific payloads. Support and report rows default to 30 days. A project file attached to an issue report is deleted 30 days after the report. Landmark download rows are deleted after 30 days. The counts of landmark models in generated maps are daily totals per landmark with no identifiers and are kept without a time limit; the event behind each count is raw telemetry and is deleted after seven days. The salted network hash kept with a shared color preset is blanked 30 days after the share; the preset itself stays public until it is withdrawn or removed. On the request board, the IP hash kept with a request is blanked when the request is read, and the one kept with a vote 30 days after the vote; a declined, removed or merged request is deleted with its votes 90 days after that decision, and one never read after 12 months. A request that is shown keeps its votes while it stays on the board. Live count answers are deleted when the count ends, about a minute and a half after it starts; only the last count’s two totals are kept. The retired developer-chat feature accepts no new rows; any remaining legacy rows are deleted after their 30-day window. Browser-local projects and export files follow the user-controlled lifecycle described above. Cloudflare Web Analytics currently documents seven days of unsampled beacon data followed by aggregation and longer dashboard availability under its own service settings. Recent supporter display rows and moderation state are trimmed to a small recent buffer rather than a complete history; a member’s row is kept for as long as the membership runs. A Discord display name credited on the Updates page stays until you ask for it to be removed. Discord notification retries temporarily retain that approved public name, amount, date, and non-hidden support message; successful delivery clears those fields from the outbox and retains only hash-based deduplication and delivery metadata. Support, issue, and makes emails are retained for up to 24 months or until deletion is requested when retention is no longer needed. Account data is kept until you delete the account, with old usernames held for 30 days, sign-in codes for ten minutes, code and guess counts for about a day, and sign-ins ending after 60 days without use. Supporter codes: the email a code was sent to and the hashes of the devices it is used on are kept while the code is in use; the email is deleted once the code has gone unused for 24 months, a device’s hash once that device has not checked the code for 24 months, and all device hashes 30 days after a code is cancelled. The rest of a code’s row (the hash of the code, its last two characters, the keyed hash of the payment’s ID, the dates and whether the code was cancelled) has no end date: it is kept for as long as the code exists, so that a refund can cancel the code and a lost one can be found. None of it contains your name, your email or the payment amount. A PayPal flag name is deleted 24 months after you chose it, 30 days after the operator turns it down, as soon as its supporter code is cancelled or the payment refunded, and when you ask. Landmarks you send: the file and the submission are deleted 12 months after the final decision (accepted, declined or withdrawn); for an accepted landmark only a short record of the rights you granted is kept (its title, place, credit name, when you agreed and a fingerprint of the file). Shared presets and palettes that were withdrawn, removed or not accepted: the picture of one not accepted is deleted after 30 days, and after 90 days the preset, picture, names and account link are deleted, leaving only its ID, the reason and the dates; that record is deleted after 12 months. Reports about shared presets, and what was decided about them, are kept for 12 months after the report is closed; the record of a decision about something you shared is kept for 12 months after the decision, and its link to your account is removed after 90 days or when you delete the account. Settings-usage counts (which settings models are made with, with no identifiers) are kept for 180 days, and the per-run records behind them for 32 days. Cloudflare Workers Logs keep the messages the hosted app’s Worker writes, such as errors and rate-limit warnings with the address that was requested, for up to 7 days. Cloudflare keeps recovery copies of the D1 database for up to 30 days, so a row deleted from the database can remain in those copies until they expire; Mini Skyline uses them only to restore the database after a fault.

Your rights and choices

You can ask Mini Skyline for access to your personal data, a copy of it in a portable format, correction, deletion, or restriction of its use (for example while a correction is checked), by emailing support@miniskyline.com. Some records carry no identifier, or only a scrambled one, so they cannot be matched to you; the sections above say where that applies.

Where Mini Skyline relies on your consent (optional analytics and diagnostics, showcase use, showing your support publicly, a PayPal flag name), you can withdraw it at any time: on this page for analytics and diagnostics, and by emailing support for the rest, in which case Mini Skyline removes your public supporter entry or deletes your flag name. Withdrawing consent does not make what was done with it before unlawful.

What you have to give: nothing, to use the map and make models. Your browser’s ordinary request data (such as IP address and browser details) is needed to deliver the site and cannot be switched off. An email address is needed only for an account and to receive a supporter code. To contact support or report an issue you need to write a message; your name and email address are optional, though without an email Mini Skyline cannot reply. Analytics and diagnostics, screenshots and project files in reports, showcase use, and sharing presets or landmarks are all optional, and leaving them out never stops you using the rest.

You can complain to a data protection supervisory authority, in particular in the country where you live or work or where you think the problem happened. In Germany that is the data protection authority of your federal state; in the UK it is the Information Commissioner’s Office.

California residents can request details about collected categories and deletion. Mini Skyline does not sell personal information or share it for cross-context behavioral advertising.

Children

Mini Skyline is not directed to children under 13, and accounts are only for people 13 or older; the sign-in window says so too. If you believe a child under 13 provided personal data, email support so it can be deleted. Where the law of your country sets a higher age for agreeing to optional data use on your own (16 in Germany, for example), ask a parent or guardian before you allow analytics and diagnostics or share anything publicly.

Cookies and local storage

The public app uses localStorage for language and theme, app-instance coordination, planet/projection preferences, workspace autosaves and recovery, recent and pinned place searches, saved print sizes and printer beds, Project Mode ownership or session receipts where applicable, export-Terms acceptance, privacy choices, the first-visit date for optional new-versus-returning visit counts, the random ID used to count landmark downloads, optional telemetry deduplication, and a note that you clicked a Buy Me a Coffee or PayPal support link (miniskylines:support-coffee-clicked:v1), which is set on that click whatever your privacy choice, never leaves your browser and only stops the support prompt from asking again. If you allow analytics and diagnostics it also keeps there a record of the consent state this browser last reported and for which day, week, and month, the random number this browser used in the last live count, the date the banner was last counted, and the site’s last popup settings (miniskylines:popup-switches:v1, so a reload does not briefly show a popup that is switched off). After “Necessary only”, those notes stay in the tab’s sessionStorage and go when the tab closes. Before you answer the privacy banner, none of them is written to your browser: they stay in the page’s memory and go when you leave or reload it. Whether the map’s settings ribbon is hidden (miniskylines:settings-ribbon-collapsed) is saved in localStorage only once you show or hide it yourself. sessionStorage or active-tab memory also holds short-lived app and Project Mode state. The public app does not use advertising cookies. Signing in uses the cookies described under Accounts. The separate operator dashboard may use a token cookie when dashboard access is enabled.

Security and transfers

Mini Skyline uses hosted infrastructure, access controls, rate limits, input limits, and provider caches to operate the service. Data may be processed in the United States or other regions used by Cloudflare, Google, Resend, Buy Me a Coffee, PayPal, Discord, Mini Skyline’s email provider, Esri, and requested map, elevation, and aerial-photo providers. No internet service can guarantee perfect security.

Text messages

Mini Skyline sends automated text messages to one phone only: its owner’s, to report a new donation. They are sent through Twilio. A text holds the amount, the currency and the payment service, and nothing about the donor. We do not send text messages to visitors, customers or donors, and we do not collect phone numbers for texting. The owner’s mobile number and text-message consent are not sold and are not shared with third parties or affiliates for marketing. The consent form and how to stop the texts are at https://miniskyline.com/text-alerts (Donation text alerts).

Changes

This notice may change as the service changes. Material privacy changes will receive a new update date and be recorded in the app or changelog before deployment.

Map data © OpenStreetMap contributors, Overture Maps; elevation Mapterhorn and Mapzen · Credits