Privacy policy

Effective 20 August 2026

Artist Alley Org LLC (“Artist Alley,” “we,” or “us”) operates 3place at 3place.world. This policy applies to 3place. It does not replace the separate privacy policy for the Artist Alley marketplace.

Privacy at a glance

• Public and lasting: placements and edit history can show exact world coordinates and your account attribution. For a protected staff action, ordinary viewers receive Staff member instead; authorized moderators and admins retain canonical attribution. A current voxel may be overpainted, erased, or removed by moderation, while its edit history and applicable moderation evidence are kept for the life of the service.
• Location is optional: 3place does not automatically ask for your device location. If you choose the location control, your browser uses it once to move the map and 3place does not store the raw position in your account.
• Temporary or private: live presence ends when you leave or disable it, signed-in gameplay IP observations leave live moderation lookups after 30 days, saved places are account-private, and drafts and local templates stay in your browser unless you choose Share.
• No data sales or behavioral ads: 3place does not sell your information, use behavioral advertising, or store full card numbers.

3place is a public, shared voxel world laid across a map of Earth. Where you build, publish, or appear can associate your account with a place you chose to visit; it is not normally your device's physical location. Avoid a home, school, or other sensitive place if you do not want that association public.

Information we collect

Accounts

• When you sign in with Google, Discord, X, Bluesky, or Telegram, we receive an identifier for that account and any email, display name, or profile image allowed by the permission shown during sign-in. We do not receive your password or keep provider access tokens as your 3place credentials.
• We store your handle, whether moderation has locked handle changes, account and activity times, provider profile-image URL, any profile picture you upload, avatar body and selected trail color, public nearby-presence choice, staff-only body, alliance-attribution, and public staff-status visibility choices, alliance, balances, purchases, gifts, progress, staff mode, and account or moderation status. A name-enforcement audit retains the replaced and safe replacement handles. Uploaded profile pictures are public while selected. For a timeout or permanent ban, we store a separate reason written for the restricted account. After a verified sign-in, that account can view the restriction type, any end time, and this reason without receiving a normal session. Staff may also send a private account warning. We store its text, the staff issuer, delivery time, related remediation, and when you acknowledge it. Only you and authorized staff can view it. The acting moderator or admin, staff-only notes, reporter identity, and evidence are not shown to the restricted account. Staff presentation and world-action privacy are recorded separately. At action time, Anonymous or Hidden staff placements and all moderation-tool world changes store a protected-attribution marker; Named staff placements remain publicly attributed. Authorized moderators and admins retain canonical authorship and immutable audit records. Staff may irreversibly apply the same public protection to a report-linked older staff batch.

Public gameplay and community information

• Placements and erases include exact 3place coordinates, color, time, and author. The current voxel also records whether Staff Mode was active for that placement. Voxels and edit history can be public with your handle and profile image. An admin may remove every current voxel still authored by a permanently banned account, while retaining edit history, staff audit, and restoration evidence. Inspecting a current voxel also shows your current alliance. Staff may disable that public alliance attribution; inspecting a staff-mode placement still shows a generic staff tag. Ordinary views of a protected action use the non-account label Staff member across current voxels, edit history, replay, contributor counts, and report receipts, without the canonical id, handle, profile image, or alliance. Protected User Mode placements spend ordinary charges but create no personal rewards or public score. This protection is fixed to the action; later visibility-setting changes do not rewrite it.
• Community Beacon, Firework Crate, and Tactical Nuke purchases store the account, chosen world coordinates, item, and time. Active beacon coordinates are public on the map, firework coordinates are sent live to connected players so nearby clients can show the launch, and a scheduled nuke's coordinates and countdown are sent to all connected players so every client can show the strike. These effects do not publicly identify the purchaser.
• Nearby players may receive your in-world position, viewing direction, and selected cell while you are connected. Receiving devices derive a short movement trail from those recent live poses; 3place does not transmit or store separate trajectory points. Signed-in players can choose Named or Anonymous public presence. Named shows an avatar, handle, and the selected Solid trail color. Anonymous shows other players a default avatar without the handle and uses a temporary standard Solid color; the selected trail color is not included in that public projection. Each device can show Full, Simple, or Off trail effects. Authorized moderators and admins still receive the real handle, avatar, position, viewing direction, selected cell, and trail color of every nearby signed-in player. Staff can separately choose whether visible presence shows a generic STAFF badge and Rainbow trail, independently of unlimited staff painting. Anonymous with that choice on reveals staff status but not identity. Staff can also choose Hidden, which reveals no public avatar, anonymous placeholder, aim, badge, or trail; other authorized staff still receive the canonical presence and actual staff status. Signed-out walkers remain anonymous; moderator views label them signed-out guests but receive no account identity for them. Except for an enabled generic staff status, public views receive no account-status distinction. A signed-in account without a handle is shown to staff by account number. Live presence stays in server memory, while the current-voxel staff tag described above persists with that voxel.
• Hosted templates contain the creator, optional alliance, name, exact world anchor, dimensions, voxel count, palette and voxel data, visibility, frozen revisions, and moderation state. Public projects are visible to anyone; alliance-only projects are visible to current members. Downloaded copies become independent local templates.
• Reports can include the people, alliance, or hosted template involved, coordinates, public profiles, exact template revision and name, evidence, optional context written by the reporter, staff notes, and actions. Staff can also record a separate response for the reporter. A signed-in reporter can view their own report number, submitted reason, safe target or location snapshot, review state, and that public response. A report about a protected world action retains the canonical staff author as restricted evidence while the reporter's receipt uses Staff member. Full report evidence, reporter-written context, staff notes, staff identities, enforcement details, and other reporters are restricted to moderators and admins and retained with the report. To investigate suspected alternate-account abuse or restriction evasion, authorized moderators and admins can use an open account-linked report to view 30 days of recent signed-in game-connection IP addresses and exact same-IP, same-day matches to other reported accounts. Every IP-and-match lookup is audited without copying an IP address into the audit or requiring a written case reason. Network observations for an account that is or has been staff are protected from this workflow; granting a staff role removes retained observations and any active pause address, and later role removal does not restore collection. Shared-IP evidence is supporting context rather than proof by itself. When other evidence shows ongoing disruptive activity, authorized moderators and admins may temporarily pause painting, recoloring, and erasing by non-staff accounts using one recently observed exact IP address for up to 24 hours. Viewing and sign-in continue, and an affected painting attempt shows the scheduled end time and contact route. If staff-channel notifications are enabled, Discord receives a limited report-operations feed containing an access-controlled 3place report link, report and action numbers, kind, fixed reason, target type and numeric id, the target account handle captured when a voxel or user report is submitted, optional report coordinates, lifecycle state and public disposition, fixed enforcement action kind, affected voxel count, timeout expiry, and event time. That feed does not include reporter identity or context, other handles or names, avatars, staff identity or notes, public-response prose, restriction reasons, or evidence. Showcase submissions include a photo or a finished replay video and poster, the photographer, times, review status, and either the photo camera pose or the replay’s history area, time range, edit and contributor counts, and lifetime/range label. Approved Showcase media, metadata, and attribution are public.

Location and map use

• The browser asks for device location only after you choose and confirm the location control. It uses the result once to move the map. 3place does not send the raw position to its server as a separate location field or store it in your account.
• Map-tile requests reveal the displayed area, IP address, and browser details to 3place and OpenFreeMap. OpenFreeMap applies its own privacy practices.
• Street view, painting, saved places, hosted templates, Showcase, and presence use world coordinates that can be converted to latitude and longitude. Opening a cell's Google Maps link sends its coordinates to Google.

Private, payment, and technical information

• Saved places are private account bookmarks with a world cell and optional name. Imported source models and textures, drafts, local guide progress, unshared templates, and most preferences stay in your browser unless you export them or choose Share. Sharing uploads only the canonical hosted template data described above.
• For purchases, we store provider order and payment identifiers, pack, amount, currency, status, and times. Stripe or PayPal processes payment details; 3place does not receive your full card number.
• We process IP address, request and connection metadata, device information, and security signals. When you connect to gameplay while signed in, we coalesce your account, IP address, and UTC day into a short-lived moderation observation. Graphics-failure diagnostics can include renderer, screen characteristics, failure details, IP address, and user agent.

How we use information

• Provide accounts, the shared world, presence, saved places, hosted template sharing, alliances, and Showcase.
• Attribute activity, process purchases and refunds, and keep financial records.
• Handle support, enforce rules, prevent abuse, secure the service, and comply with law.

Where required, our legal bases are performing our agreement with you, complying with law, our legitimate interests in running and protecting 3place, and consent for location or another consent-based use.

How we disclose information

• Other people receive public world activity, the Staff member projection for protected world actions, approved Showcase media, metadata, and attribution, leaderboard and alliance information, public hosted templates, alliance-only hosted templates when they are current members, public profile pictures, enabled public alliance attribution, enabled nearby presence and Named trail colors, generic staff badges and Rainbow trails attached to visible staff presence, and staff-mode tags attached to voxels.
• Service providers process information for us: your chosen login provider handles sign-in; Stripe and PayPal handle payments; Railway and its infrastructure providers host the service; OpenFreeMap serves map tiles; Discord may process the limited report-operations feed described above when staff notifications are enabled; and Google receives a coordinate if you open a Google Maps link.
• Legal, safety, or business disclosures may occur when reasonably necessary for law or legal process, fraud or security investigations, protecting people or 3place, or a protected financing, merger, acquisition, or asset sale.

We do not sell personal information, share it for cross-context behavioral advertising, or use third-party advertising pixels.

Cookies and browser storage

Necessary first-party cookies support sessions, sign-in, and access control. An active account-session cookie can last up to 90 days; temporary OAuth state expires after about 10 minutes. A one-time restriction-notice cookie can last up to 10 minutes after a restricted account verifies sign-in; it does not create an account session and is cleared when read.

Browser storage holds preferences including trail-effect detail, cached world data, local templates, blueprints, drafts, navigation state, and graphics-recovery state. When sign-in or handle creation would reload a finished replay, 3place can keep that one video, poster, and submission metadata on the device for up to seven days so the preview can resume afterward. It is cleared after submission, Retake, or discard. Browser controls can clear local storage, which may discard local work. Because 3place has no behavioral ads or cross-site tracking, Global Privacy Control and Do Not Track signals do not change its behavior.

Retention

• Raw device location is not retained. Live presence is removed when you leave or become inactive. Movement trails expire on receiving devices and are not retained as route history. A staff Hidden choice removes the public projection, not the in-memory presence available to authorized moderators. Device-only information remains until you, the browser, or 3place clears it.
• Account information and saved places are generally kept while the account is active or until the item is removed. Replacing or removing an uploaded profile picture deletes its live image bytes; a cached public copy may remain for up to five minutes.
• Hosted template projects remain available until an eligible player removes them or staff unlists them. Removal or unlisting ends player access; frozen revisions and report evidence are currently retained for the life of the service.
• Signed-in gameplay IP observations are used in live moderation lookups for 30 days and then removed by scheduled cleanup. Accounts protected because they are or have been staff are excluded, and granting a staff role purges their retained observations. A temporary painting pause stops using and exposing its separate exact-address copy at its end; an early or staff-protection end clears it immediately, and scheduled cleanup removes it within about one hour after natural expiry. The remaining non-address action record includes the source report and target, address family, duration, staff actor and role snapshot, times, and end state, and is retained with staff audits. The audit of which staff member used an IP-and-match lookup, including the report, target, role, and time but not a copied IP address or written reason, is also retained with staff audits.
• Current voxels remain until overpainted, erased, or removed through moderation. World edit history and canonical attribution, protected-attribution markers, retained removal evidence, reports and staff audits (including one-way staff-attribution actions, account-visible restriction reasons, private account warnings and acknowledgements, and replaced handles), economy history, gifts, and Showcase media, metadata, and reviews are currently retained for the life of the service. A protected staff author's canonical identity remains restricted rather than being deleted. Rejected, hidden, or withdrawn Showcase posts remain non-public moderation evidence.
• Payment and related financial, fraud, tax, and accounting records are kept as reasonably needed or required by law or provider rules.
• Non-public security, diagnostic, and operational logs are kept as reasonably needed for incidents, abuse prevention, and reliable infrastructure; timing varies by log and provider.
• Deleted live data may remain in backups. The longest current backup schedule is 89 days, unless a legal hold requires longer.

Your choices and rights

• You can add, replace, or remove your profile picture; restore the latest image from your sign-in provider when one is available; change your handle unless moderation has locked name changes; choose a Solid trail color; choose Full, Simple, or Off trail effects on your device; choose Named or Anonymous public presence; remove saved places and eligible hosted templates; withdraw Showcase posts from public display; sign out; control location permission; and clear browser data. Staff can additionally show or hide generic public staff status independently of unlimited staff painting, choose Hidden public presence, hide their alliance from public voxel attribution, and turn unlimited staff painting on or off without losing staff tools. Staff actions created while Anonymous or Hidden use Staff member public attribution; ordinary setting changes do not retroactively rewrite earlier actions. Moderators still receive canonical signed-in presence and actual staff status for live moderation.
• You may ask to access, correct, export, or delete personal information, or object to or restrict certain processing, by contacting us below. Available rights depend on where you live and why the information is processed.
• We may verify your identity. Some public world history or records needed for payments, moderation, security, backups, law, or legal claims may be retained or de-identified; we will explain any exception.
• You may complain to your privacy authority. You may also submit a verified request not to sell information, although 3place does not sell personal information.

International processing

Artist Alley is based in the United States. Information may be processed in the United States and other countries where our providers operate. Where required, we rely on applicable provider terms and lawful transfer safeguards.

Children and teenagers

3place is not directed to children under 13, and an account requires the user to be at least 13. Users under 18 must have permission from a parent or guardian. If you believe a child under 13 provided personal information, contact us so we can investigate and take appropriate action.

Security

We use technical and organizational safeguards, but no service can guarantee perfect security.

Changes to this policy

We will update the effective date and provide additional notice when a policy change is material.

Contact

Privacy questions and requests: 15@artistalley.org