Skip to main content
Privacy · Útgarðr

Your data, kept inside the boundary.

The short version of what the project-update and contact forms collect, how historical payment records are handled, and the single address to write for privacy and access requests. The site collects only what the current concept project needs.

Privacy · Útgarðr
What we collect

Only the data the project needs.

The public forms collect an email address, consent, and the item or project context needed to send requested updates. The contact form also stores the message and the details you choose to include.

The current storefront does not collect new deposits, reservations, shipping addresses, or checkout data. Historical payment and reservation records remain unchanged and are used only for reconciliation and support.

We use the minimum information needed to answer a message, send a requested project update, or support an existing payment record.

Cookies

No analytics, no third-party trackers.

No cookies are set for analytics. No third-party tracker ships on this site. There is no Google Analytics, no Meta pixel, no segment of any kind watching where you go after this page.

The only preference set in your browser is the theme — light or dark — and it is held in `localStorage`, not as a cookie. The theme toggle in the top bar reads and writes it; nothing else does. There are no session cookies, no login cookies, no advertising IDs, no cross-site identifiers of any kind.

Third-party processors

Email and contact services for project communication.

The contact and project-update forms use the email and contact infrastructure already wired into this site. Submissions are stored so the founders can respond and notifications can be delivered.

Stripe may remain relevant to historical payment reconciliation, but the public storefront no longer starts new Stripe checkout or reservation flows.

We do not engage a marketing automation suite, advertising network, or third-party CRM for this concept project.

Retention

Kept only for the reason it was collected.

Project-update and contact submissions are retained for communication, support, and audit of consent, then removed according to the company’s operational retention practices.

Historical payment and reservation records are preserved rather than deleted or rewritten so existing customer support and reconciliation remain possible.

The current concept storefront does not request a shipping address because it does not offer shipping or a fulfillment date.

Contact channel

One address for privacy and project questions.

For access, correction, deletion, or questions about an existing payment record, write to tgarr@polsia.app. The same inbox handles project updates and contact messages.

Include enough context for the founders to locate the record, but do not send card details or other sensitive payment credentials.

At a glance

The short version, in one band.

Project-update and contact submissions are retained for communication and support. Historical payment records remain available for reconciliation. No new deposits, reservations, shipping addresses, or checkout data are collected by the current concept storefront. One address for privacy and access requests: tgarr@polsia.app.

Write to the founders
tgarr@polsia.app

The same inbox handles project updates, historical payment questions, and the contact form. Replies are read in the order they arrive.

Continue

Read on.

The FAQ explains the concept-stage project; the contact page is the inbound channel for everything else.

or step into the brand story and the founding rationale behind the line.

Last updated 2026-10-19 · written and held at https://tgarr.polsia.io · Útgarðr