Atlas privacy notice

Atlas by Driftwood collects account and project-enquiry information so you can use the workspace and discuss a project with Driftwood.

What we store

Accounts contain your name, email, a salted password hash, session records, monthly usage, any requested access plan and an unverified entry-point label. A requested plan is a preference, not a paid entitlement. Email verification and account recovery require an enabled transactional email service. The account screens show whether delivery is available; verification status is kept with the account. Enquiries contain the information you submit, your selected plan if provided, optional project role and site-control details, an unverified entry-point label, your contact consent and a reference number. When signed in to a regular Atlas account, saved sites, project assumptions and dated screening summaries are stored privately with that account so you can retrieve them on another device. Guests and private-preview visitors retain browser-only shortlists. Importing an older browser shortlist into an account is an explicit choice. Infrastructure queries and boundaries are stored to cache evidence and refresh it; do not enter confidential project boundaries or sensitive information during early access.

Browsing before signup

You can explore without creating an account. To limit automated requests, we store rolling 30-day site usage against a server-keyed hash of your network address; this feature does not store the raw address. Visitors sharing a network share an allowance. Hosting providers may keep their own connection logs. If you choose to create a report, your location, project settings and custom boundary can be held in this tab’s session storage for up to one hour so you can return after signup. This draft is removed after the report opens; an unused draft can remain until the tab closes or site data is cleared. Drafts are not analytics events. Automated screening currently uses connected public sources. Private records may be considered within a separately agreed, authorized review.

Taking a site to Driftwood

When you open the human-review offer on the map or a report, the selected location, profile and demand can be held in this tab’s session storage to prefill an enquiry for up to 24 hours. The prefill can also include a bounded, dated assessment brief: the assessment and source-snapshot identifiers, project assumptions, selected findings, unresolved questions and source references. A boundary fingerprint can identify the assessed footprint; the full custom geometry is not attached. You can inspect the brief and separately choose to attach it. Nothing is sent until you consent and submit the form. Attached evidence is retained as the submitted snapshot; a later source refresh does not silently replace it. It is customer-submitted screening context, not independent confirmation of its claims. An unused entry may remain until this tab closes or browser site data is cleared. Opening the offer does not create a lead, subscribe you or take payment.

Your saved shortlist

Account shortlists are private to the signed-in account. You can export your sites, import a saved export and remove individual entries in Atlas. Concurrent edits are checked so a stale browser cannot silently overwrite another device. A limited set of prior versions is retained on the same hosting volume for recovery; removing an entry also removes its stored versions. An exported file contains your site details and assumptions, so keep it somewhere appropriate. Shared public-source caches are separate and are not removed by deleting a shortlist entry.

Private previews

A private preview does not create an account or collect an email or password. We store a hashed access-link identifier, its expiry and withdrawal status, session records, and location usage. A secure session cookie keeps the preview open. The location allowance is shared across browsers using the same link and ends when the link expires or is withdrawn. Anyone with your link can use that allowance, so keep it private. The link secret is removed from the browser address when opened and is not stored in browser storage or discovery attribution. Site queries and boundaries use the same evidence cache described above.

How it is used

We use this information to operate Atlas, prevent abuse, answer your enquiry and assess the project scope. Enquiry consent covers contacting you about that enquiry. It does not subscribe you to unrelated marketing. Submitting an enquiry does not place an order or take payment.

Understanding how people find Atlas

Public pages keep a small first-party discovery note in this tab’s session storage, used for up to 24 hours: the first public Atlas pathname, the first external referring website’s hostname, and any supported campaign source, medium and campaign tags. We do not keep the full external referrer URL, its search query, arbitrary URL parameters or an advertising identifier. Invalid or overly long values are discarded. If browser storage is unavailable, only the current page’s in-memory context may be available.

This note is sent to Atlas only when you consent to and submit a project enquiry. It helps us understand which public content and discovery channels bring relevant enquiries. It is unverified browser context: missing referrers, privacy controls and editable campaign tags mean it does not prove an AI citation, a particular search engine or a person’s identity. This enquiry-attribution note creates no tracking cookies and is separate from the automatic aggregate product events described below. An unused entry can remain in the tab after 24 hours; it is replaced on a later public-page visit and can be removed through your browser’s site-data controls.

Hosting and outside services

The Atlas service and stored records are hosted on Railway. Railway infrastructure and public data providers may process data outside Canada. Map tiles, address search, fonts and infrastructure requests involve outside providers; their services receive the information needed for those requests, such as an IP address or query coordinates. We do not include advertising trackers in this release.

Access and removal

Contact Driftwood to request access, correction, account assistance or removal of your account or enquiry records. Include your Atlas reference where relevant. Shared public-source evidence is maintained separately from personal account records.

Contact Driftwood · Driftwood privacy policy

Enquiry receipts and engagement outcomes

When transactional delivery is configured, a submitted enquiry can receive a confirmation at the address supplied. Delivery is currently disabled; the on-screen reference confirms the enquiry was saved. Enquiries received while confirmations are disabled are not later sent as a backlog. Staff may record actual engagement outcomes, their baseline and measurement method, caveats and supporting references. These records remain private. Public case studies require recorded publication permission and supporting evidence; demonstrations are not customer outcomes.

Service improvement counts

Atlas automatically records a limited set of product events on its public website and workspace, such as page views, searches, profile changes, completed screens, reports opened or exported, saved-site and comparison actions, and requests for human help. These are stored as daily aggregate counts with allowlisted categories: broad page area, mobile or desktop viewport, coarse discovery channel, selected micro/small/large profile when provided, and grouped completion times. We do not include searched addresses, coordinates, customer or account IDs, email addresses, report contents, browser identifiers, full page URLs or full referring URLs in these events.

The browser may keep a coarse discovery category such as search, AI referral or direct in this tab’s session storage so a visit is counted consistently across public pages. It does not store an analytics identifier or create tracking cookies. Browser event collection honours Global Privacy Control and Do Not Track; those preferences prevent automatic event requests and storage of this aggregate discovery category. Successful account creation, saved enquiries, staff qualification and completed screening jobs also contribute aggregate server-side operational counts, without browser identifiers or private project details. These operational counts continue when browser analytics is blocked.

Only authorized Driftwood operators can view the aggregate dashboard. Counts are events, not unique people or measured conversion rates. They can be repeated or missing and do not establish that a person viewed a completed screen. Coarse referral categories cannot prove an AI citation. Daily aggregates are retained for service comparison; there is currently no fixed automatic deletion schedule for these non-identifying totals. Private operational alerts contain source and queue status, assigned staff and next actions. They do not copy customer enquiries into the alert stream or send alert emails. Contact Driftwood if you have questions about this collection.

Private review projects

Private review projects contain the reference details, permissions and review notes submitted for Driftwood review. They are scoped to your account and selected site; they are not added to the public map. Reference submission does not confirm a utility commitment. Documents are not uploaded through this reference form. Contact Driftwood to request removal of a review project.