Voyarc

Privacy Policy

Effective date: 31 August 2026 · Last updated: 7 November 2026

Voyarc is built to hold as little about you as possible. There are no accounts, we never receive the files you import, and the maps and films are drawn in your browser. What does leave it is small and listed on this page: the stops of a trip's road, bike and walking legs go to a routing service, what you type in the place search goes to a place search, the two ends of an imported track go to the same place search, rounded, to be named, a trip you choose to share is stored behind its short link, and a purchase leaves your email address with us.

Who we are

Voyarc is a product of Quiet Cockatoo Pty Ltd, an Australian company, which provides the service and holds the information this policy describes. Privacy questions: hello@voyarc.app.

No accounts

Voyarc has no sign-up, no login and no profile. You can use every current feature without telling us who you are.

Your files stay on your device

Every file you import, a recorded track (GPX, KML, KMZ, TCX or GeoJSON), the logo you add to a film or a photo you add to a stop, is read and parsed entirely in your browser. The file is never uploaded to us or to anyone else. The track tools work the same way: a file you view, convert or fix there is read and written in your browser, and nothing of it is sent to us or to anyone else. A music file you pick for a film is read in your browser too and, on a Film pass or Pro, kept in your browser's storage until you choose No music; it is never uploaded. The vehicles' sounds and the film's music are recordings served from our own site, mixed in your browser to the trip's timing, and nothing of your trip is sent to make them.

A track does leave a trace in the trip itself. Its first and last points become the trip's stops, at their exact positions and named Start and Finish or by the place they are in (Place search and routing), and its dates become the trip's date line. Those are part of the trip's link like any other stop (Trip links). If a track starts or ends somewhere private, such as your home, that position is in any link you share. To keep it out, turn on "Trim the ends" under the import button before you import: it drops the first and last 500 m of the track in your browser, so the stops sit that far along it instead.

The app keeps a thinned and cleaned copy of each imported track, and the logos you add, in your browser's storage, so the trip opens again with them (see Settings in your browser). An imported track's own points are never sent to be routed. A photo you add to a stop is downscaled in your browser and kept in your browser's storage, to be drawn into the film there; it is never uploaded and never in a trip's link, so a link opened anywhere else shows the trip without its photos. A face you crop to draw a scene as yourself stays in your browser's storage too, never in a link (a link says only how many faces a scene has, and opened anywhere else it shows the scene's vehicle), and goes to another device only in a handoff or trip file you start. Voyarc saves no file of yours on our servers.

Place search and routing

Three things leave your browser, and only so that the app can draw the trip you asked for:

  • Road, bike and walking legs. To follow real roads and paths, the two ends of each such leg (their coordinates and the kind of travel) are sent to our server, which asks a routing service for the way between them: openrouteservice, run by HeiGIT in Germany, or, when it cannot answer, Geoapify. Each processes the request under its own terms. We keep the answer (the line of the road between those two points) in a cache for up to 30 days, keyed by a scrambled (hashed) copy of the coordinates, so the same leg is not asked for twice.
  • Searching for a place. A stop you type is matched as you type against a list of places that ships with the app, in your browser (a three-letter airport code is looked up there too). Once you have typed three letters, what you typed is also sent to our server and on to Photon, komoot's public place search, to find the places that list does not have, together with the position of the stop before it, so the nearest place of that name comes first. We keep its answer in a cache for up to 7 days, keyed by a scrambled (hashed) copy of the search text and of that position rounded to the nearest degree. The ends of a track you import go to the same place search, rounded, as the next item says.
  • Naming a track's ends. The two ends of a track you import, each rounded to about a kilometre, are sent to our server and on to Photon, so they can be named by the town or suburb they are in. Nothing in between leaves your device. We keep the answer in a cache for up to 7 days, keyed by a scrambled (hashed) copy of that rounded position.

None of them carries an identifier of you, and no cache records who asked. To keep these services from being overwhelmed, our server counts requests per address per hour; the count is kept under a copy of the address scrambled with a secret key of ours, never the address itself, and is deleted after two hours.

Everything else stays in your browser: rail and ferry legs are routed there over networks that ship with the app, legs by air are great circles, a leg you sketch is drawn from its stops, and the show and the film itself are drawn on your device. None of that is sent anywhere.

Your trip lives in the URL: a link carries its stops (their names and positions), how each leg was travelled, and what you set for the film, such as its title, scene names, date line, vehicles and lengths, so that a link reproduces the map. That means the trip travels wherever you paste the link, and it appears in our hosting provider's request logs like any other web address. A trip is as private as the places in it: a link that names your home is one to share with care.

Copy link copies a short address instead, like /l/aB3dE9x. To make one, the trip part of the link (everything listed above) is sent to our server and stored with Cloudflare, our host, behind that short address, with no account and no identifier of you attached; making one is counted per address per hour, as above. A card image of the trip's map, the picture a chat app shows beside the link, is kept with it, again with no record of who made it. Short links do not expire, and anyone with the link can open the trip. To have a short link removed, email it to us.

An imported track's line is not in the link; its two ends are, as stops. When a link is opened in a browser that does not have the track, the leg's two ends are routed as an ordinary leg, as described above.

Continuing on your computer

Continue on your computer moves a trip from your phone to your computer, and the finished film back, and nothing of it leaves your devices: the trip, its photos and the film travel directly between your own phone and computer, encrypted by the browser (WebRTC's DTLS), and our server sees only the handshake. That is two short connection descriptions, a few kilobytes at most, with the network addresses each device can be reached at, kept in a room named by the code your phone shows for one minute after the last of them is written, and then deleted. It is never the trip, the photos or the film. The code is checked with each request and is not kept.

To find a way between them, each device asks Cloudflare's address server (stun.cloudflare.com) which public address it is reaching the internet from. That server sees the device's public address and nothing else. On one Wi-Fi network the trip never leaves it. With the trip go its photos, your logos, the faces its scenes draw, the sound choice, your own music file if you chose one and, on a Film pass or Pro, the token that unlocks it with its renewal reference, so your computer has the same pass.

When your phone and your computer cannot reach each other directly, the trip is not sent through us instead: the page says so, and you can send the trip as a file yourself.

Settings in your browser

Voyarc keeps what it needs to remember in your browser's storage: the logos you add (up to five), the faces you crop (up to five), your imported tracks, the photos you add to stops, the music file you choose for your films, whether the sounds are on, which hints you have seen and the link to the last trip you made, so the home page can offer it again, under keys of its own; the last film you made, kept on the device until the next one takes its place, and a small note of how its render is going (its stage and frame), so a page the browser closed can say so when it loads again; and, on Pro or a Film pass, the token that unlocks your purchase together with Stripe's customer reference, under voyarc-entitlement* keys. The logos, the faces, the tracks, the photos, the music file and the preferences are never sent to us. The purchase token and reference are sent to our server only to check and renew your purchase. All of it stays on your device until you clear site data; the purchase token also goes when you choose Forget on this device on the pricing or restore page. Voyarc sets no cookies of its own.

Hosting

Voyarc is hosted on Cloudflare. To deliver the site and protect it from abuse, Cloudflare processes standard request metadata: IP address, timestamp, requested URL, user agent and approximate location. That is Cloudflare acting as our infrastructure provider under their terms, and requests may be processed on Cloudflare servers outside Australia. We use it only for delivery, security and debugging, and we don't build profiles from it.

The maps come from our own tile servers. If those are out of reach, the map falls back to the public tile servers of OpenFreeMap, which then receives the same kind of request metadata for the files your browser asks it for. The maps' label fonts and icons, by day and by night, come from our own site.

Analytics

We use cookieless, aggregate analytics (Cloudflare Web Analytics) to count page views. Cloudflare adds its measurement script to the pages it serves for us. It does not set cookies, does not follow you across other sites, and does not identify individuals. It does see each page's path, and the path of an open trip includes the trip's own path: its stop names and coordinates.

The trip-film app sends our server counting beacons: the Look, format and tier of an export, the kind of link made, a click on Pro, and the seconds a render ran while its tab was hidden. They carry no identifier.

When a checkout is opened or a purchase completes, our server counts which product it was. There is no identifier, no address, no route text and no file name in that count, and every event is added into a monthly total. It tells us how many people go on to buy, and nothing about who anyone is.

When our server asks a routing service for a leg, it adds one to a daily count of how that went: which service answered, or why none did. There are no positions, no route, no kind of travel and no address in that count, and each day's total is deleted after about 90 days. It tells us how often a leg falls back to a curve, and nothing about whose trip it was.

Payments (Pro)

Payments are handled by Stripe: you give your card details to Stripe, not to us. We keep only what unlocks your features and keeps our records: your email address, the plan, and Stripe's customer reference. We also keep a scrambled (hashed) copy of your address, which is how “restore by email” finds your purchase without our storing a list anyone could read. Stripe processes that data under its own privacy policy, and Stripe's own checkout pages set their own cookies. The return address Stripe holds for a checkout, so it can send you back to your trip, carries the trip's path (its stop names and coordinates) and nothing else.

The purchase record is kept for seven years after your last purchase, as tax law asks, then deleted. Requests to restore a purchase are counted per address and per email address, both scrambled (hashed), for up to two days, to stop the form being abused.

We send three emails, all plain text: one when a subscription ends, carrying the link that restores your saved data; one when you ask us to restore a purchase by email, with a link to your Pro; and, if you ask in the 30 days after a subscription ends, one with a link to your saved data instead. They go out through Resend, our email provider, which processes the address in order to deliver the message. We send no newsletters and no marketing.

Voyarc Flights

This policy also covers Voyarc Flights, the flight app, which maps great-circle flight routes. Everything above applies to it, with the same processors (Cloudflare, Stripe, Resend) and one purchase unlocking both apps, except where this section says otherwise.

  • Files. A route list, a logbook CSV or a flown track is read in your browser and never uploaded; close the tab and it is gone. Its contents reach us only in a link, or as the rows you file into a Pro logbook (below).
  • Links. A route link reads like /route/SYD-LAX-JFK. Copy link shortens a URL longer than 120 characters (in practice, an imported logbook) by storing its route part, the airport codes and map settings the app writes, with Cloudflare behind a short /r/... address. No identifier of you and no file contents; short links do not expire.
  • Browser storage. Its preferences (distance unit, projection, export aspect, route colours, the look, the ring diversion speed, open panel sections, hints seen, and whether a paid session kept the Voyarc mark) and “Recent”, the last 10 route lists you typed, stay in localStorage under voyarc-* keys, with its Pro token under voyarc-entitlement*.
  • Counters. A finished export sends one event: the format (MP4), the look on screen, the style the file came out in, and free, Pro or Film pass. Copying a link says only which kind (long, short or embed), and pressing a Get Pro link only which one (the panel's button, its menu, or a hint beside a feature), each with free, Pro or Film pass. No identifier, address, route text or file name; monthly totals only.
  • Embeds. When another site embeds a flight map, the iframe loads from our domain, so the request metadata described under Hosting reaches Cloudflare for that page's viewers. Embeds carry no account data, set no cookies, and tell the embedding site nothing about its visitors.
  • Saved collections (Pro). The only place we store something you made: named route lists and a flight logbook that sync between your devices. Stored: airport codes and how many times you flew each route, the dates you add to the logbook, each collection's name, and the map settings needed to reopen it (colours, style, flat or globe, how the map is shown, the legend's title and labels); no notes field, no photo upload. Kept against your Stripe customer ID, not your name or address, in Cloudflare's storage, which we cannot guarantee stays in Australia. Held while your subscription is active and for 30 days after it ends, when you can still open, download and delete it but not add to it, then deleted automatically; the logbook exports to CSV at any time. The purchase record is not on that clock: your email address, the plan and Stripe's customer reference stay until you ask us to delete them, so a restore or a refund can still be answered. To delete your saved data, open the Pro chip at the top of the panel and choose “Delete my saved data”: it goes at once, and your browser's Recent list is untouched. We do not read, analyse or profile it, use it to target advertising, or share or sell it; our usage counters record only how many collections and entries exist.

Your rights

Because we hold so little, most requests are quick to answer. Email hello@voyarc.app to ask what we hold about you, to correct it, or to have it deleted, and we will respond within a reasonable time. If you're unhappy with our answer, you may also raise it with the Office of the Australian Information Commissioner.

If you are in Europe or the UK

If you are in the European Economic Area, the United Kingdom or Switzerland, the company named under Who we are is the controller of the personal data this page describes. We use it to provide what you asked for (routing, place search, short links, your purchase) and, on the basis of our legitimate interest, to keep the service secure and to count its use in aggregate. You can ask for access to your data, for a copy of it, or for it to be corrected, deleted or restricted, and you can object to its use, by emailing hello@voyarc.app. You can also complain to your local data protection authority. Your data is processed in Australia and wherever our providers operate, including the United States and Germany.

Australian privacy law

Voyarc is a small business. Whether or not the Privacy Act 1988 (Cth) applies to a business of our size, we handle personal information in line with the Australian Privacy Principles: we collect only what this page lists, use it only for the purposes it gives, keep it secure, and answer requests for access, correction and deletion.

Children

Voyarc is a general-audience mapping tool, not directed at children under 16, and we don't knowingly collect information from them.

Changes

If this policy changes we will post the new version here with a new effective date. Material changes will be called out on the page rather than slipped in.