Ownership & Privacy

Your work stays yours.

Remanet is free to use and does not require an account.

Your artwork, panoramas, exhibition information, and project data are designed to be processed locally in your browser. Remanet does not claim ownership of your work or your exhibition.

When you export a tour, you receive a standalone exhibition that you can host wherever you choose, move between websites, modify, archive, back up, transfer, or preserve indefinitely.

Your published exhibition does not require a Remanet account, subscription, license server, or continued connection to Remanet.art for normal operation.

The Remanet Builder itself is proprietary software. It is free to use, but it is not open-source software.

Your work. Your files. Your exhibition.

What Remanet owns

Remanet retains rights in the Builder, its original code, interface, branding, documentation, and original software assets. Third-party components retain their own ownership and licenses.

What you own

You retain the rights you already hold in your artwork, panoramas, photographs, text, audio, video, metadata, exhibition content, and project data. The Builder license does not transfer those rights to Remanet.

What happens when you export

You may host your exported exhibition anywhere compatible, move it between hosts, archive it, back it up, transfer it to another custodian, and maintain it after Remanet is discontinued. You can use your exhibition commercially or noncommercially, including on a commercial gallery or institutional website.

The included Remanet Runtime is covered by the separate Export Runtime License. Ordinary operation requires no Remanet account, subscription, license server, or connection to Remanet.art. The export contains local viewer code, styles, configuration, and media. Optional external services remain separate.

Local-first processing

Remanet is designed to process your exhibition project in your browser rather than storing your artwork and project files in a Remanet account.

When you visit the site, your browser downloads the Builder's HTML, JavaScript, styles, and sample media from the site hosting it. Your browser and the web host exchange ordinary request information to deliver those files. Opening the editable demo downloads its sample exhibition into browser memory; practice edits are discarded when you leave.

Folders you choose are accessed using browser permission. Panorama processing, tiles, cover images, artwork records, metadata, and saved project configuration are created locally. The Builder has no project-upload endpoint, account database, remote license check, or automatic error-reporting service. Errors are shown locally or written to the browser console.

Browser storage

Recent projects are stored in this browser using IndexedDB, including folder handles, project titles, folder names, and last-opened dates. The list remembers up to six folders. Removing a recent entry does not delete project files.

Terms acceptance is stored locally with the accepted Builder and Ownership & Privacy versions and a timestamp. It is not sent to Remanet for licensing and does not establish the accepting person's identity. Clearing browser storage removes these records and may require fresh acceptance and folder permission. If storage is unavailable, acceptance can last only for the current page session.

Optional Google Analytics in published tours

The hosted Remanet website, including the editor, uses Google Analytics (measurement ID G-PXH9MK8EK9) to measure website use. Google may receive usage and device information and use cookies. The website tag loads on these pages, including local previews served over HTTP or HTTPS. This is the standard Google tag, which measures website usage. Remanet does not add project files, artwork fields, folder names, or terms acceptance records to tracking events. The website tag is not included in exported tours. An exhibition creator may explicitly enable GA4 for a published tour and supply a measurement ID (a public tour URL is not required for analytics). In that case, the published tour can load Google's remotely hosted tag and send exhibition visits, individual scene views, artwork information views, and scene-navigation interactions to Google; cookies may be used. Remanet does not receive or control the analytics reports in the artist’s Google Analytics account. Analytics is optional and is not required for an exhibition to function.

The default enabled configuration asks visitors before loading Google's tag. Visitors can allow or decline and revisit Analytics preferences. Their choice is stored in that published site's browser storage. Creators can turn the consent prompt off, so the published exhibition's configuration determines whether analytics loads immediately. Creators are responsible for their analytics configuration and disclosures.

External links and resources

Polygons may link to other websites or tours. Following a link opens that destination, which has its own data practices. The current Builder includes no remote fonts, CSS frameworks, CDN libraries, remote image-processing service, external media embeds, donation integration, or feedback submission endpoint. Inter and DM Mono are bundled locally with their open-font licenses; native browser APIs are used. Google Analytics is loaded remotely on the hosted Builder website and in published tours where their creator enables it.

No ownership claim

Remanet does not claim ownership of your artwork, exhibition, project data, or exported exhibition.

Third-party material

You remain responsible for rights to materials you did not create, including permissions required for artwork, photographs, audio, video, fonts, or other assets you include. Third-party licenses govern their own components and are not replaced by the Remanet licenses.

Document hierarchy

Third-party licenses govern their components; the Export Runtime License governs original Runtime code included in legitimate exports; the Builder License governs the proprietary Builder. This page describes actual product and data practices.

Feedback

Feedback submissions are not connected yet. If you are testing with Ian, share what you were doing, what you expected, and what happened. No project files are submitted from this page.