Privacy Policy

Roles & Responsibility

NearField is the data controller for builder account data (organization details, billing, support history). For data captured from visitors on a published Experience (names, emails, ratings, choices, donations), NearField acts as a data processor and the Experience owner is the controller. Visitors who want to access or delete data they entered into a specific Experience should contact that Experience's owner first; we will assist on request.

Information We Collect

Builder account information

When you create an account, we collect your email address and any optional profile information you provide: organization name, contact name, phone number, website URL, and brand colors.

Payment information

Subscription, hardware, and donation payments are processed by Stripe. We never see or store full card numbers. When you agree at Marker checkout to save your card for your NearField plan, Stripe stores the card, and we keep only its brand and last four digits (for example "Visa ending 4242") so we can show you which card your plan will use. We retain Stripe customer and subscription identifiers to manage your account. Plans bought in the iPhone app are paid through Apple, and we receive only the purchase status, not your payment details.

Experience analytics

When a visitor views a published Experience and grants analytics consent, we record: device type, browser type, view source (direct or via Marker), and a one-way SHA-256 hash of the visitor's IP address (truncated, salted). We do not store IP addresses or visitor identifiers in analytics.

Visitor profile data

Some Experience blocks ask visitors for input: name, email, phone, ratings, quick choices, custom fields, or geolocation check-ins. This is stored on behalf of the Experience owner only when the visitor grants Personalization consent. We never sell this data and we never share it with other Experience owners.

Website usage statistics

The getnearfield.com website uses Cloudflare Web Analytics to count page views and visits in aggregate. It records the page path, referrer, country, browser, operating system, device type, and how quickly the page loaded. It sets no cookies, uses no local storage, and does not identify or fingerprint visitors by IP address or browser. It is not part of the NearField iOS app.

With your permission, the NearField website and app also use Google Analytics to understand how people find and use them: pages viewed, the site that sent you, approximate location (city or country), device and browser, and steps such as starting a signup or a Marker checkout. Google Analytics stores its cookies only after you accept analytics in the cookie notice. Until you choose, or if you decline, it runs without cookies and Google receives only cookieless signals. Google's advertising features are off.

Measuring our ads (Meta)

We advertise NearField on Instagram and Facebook. To learn whether those ads work, the getnearfield.com website uses the Meta Pixel, but only after you accept the cookie notice. It records the pages you view on our marketing site and shop, and steps such as viewing a Marker design, adding to your cart, starting checkout, creating an account, buying Markers, or sending us a form. It never runs on Experience pages (what visitors see when they tap a Marker), in the NearField iOS app, or after you decline.

When one of those steps actually happens (an account is created, an order or plan is paid for, or a form is sent), our servers also tell Meta through its Conversions API, so the count is right even when a browser blocks the Pixel. We send your email address only in hashed form (scrambled so it cannot be read), your account ID in hashed form, your IP address and browser type, Meta's cookie IDs if they exist, and the order value. We don't send these if you declined in the cookie notice. Meta uses this to measure and improve our ads under its own privacy policy.

Inclusion Bar usage

We track aggregate usage of accessibility features (language changes, text-to-speech activations, contrast toggles) only when analytics consent has been granted. This data is not linked to individual visitors.

Cookies & Local Storage

NearField uses one advertising cookie, Meta's, and only with your consent (see "Measuring our ads" above). Otherwise we use the following categories of first-party storage:

• Essential: Supabase authentication session, PIN unlock state for locked Experiences, current language during a session. Always on; the platform cannot function without these.
• Personalization (visitor opt-in, per Experience owner): a random visitor token in localStorage so an Experience can remember what you typed, tapped, or rated and personalize content to you.
• Analytics (visitor opt-in, per Experience owner): counts of views, feature use, and language preference. Stored against a salted IP hash, not your identity.
• Website and app analytics (opt-in): Google Analytics cookies that count visits and pages on getnearfield.com and in the app, set only after you accept analytics in the cookie notice. Declining keeps them off.
• Advertising measurement (opt-in, website only): the Meta Pixel's cookies, set only after you accept the cookie notice on getnearfield.com. We also keep the ad campaign tags from the link that brought you to us (for example utm_source=meta) on your device for 30 days, so we can tell which campaign led to an account or an order.

The website's aggregate usage statistics (Cloudflare Web Analytics, described above) store nothing on your device.

People using the website and the app see a cookie notice where they can accept or decline analytics; essential cookies are always on. Visitors are presented with a consent banner on their first visit to any Experience for a given Experience owner. Both decisions are stored on your device and can be changed at any time: visitors via the accessibility menu (♿) on the Experience, builders by clearing site data.

Legal Bases (EEA / UK)

• Contract: to provide the platform you signed up for.
• Legitimate interest: to operate essential infrastructure, secure the platform, and prevent abuse.
• Consent: for visitor personalization and analytics on Experiences, for Google Analytics on the website and app, and for the Meta Pixel and Conversions API on the website.
• Legal obligation: to comply with tax and accounting requirements.

How We Use Your Information

• To provide, maintain, and improve the NearField platform
• To process payments and manage subscriptions
• To provide Experience owners with consented analytics and visitor data
• To send transactional emails (account confirmation, password reset, order updates)
• To respond to support requests

Data Sharing & Subprocessors

We do not sell personal information. We share data only with the service providers required to operate the platform:

• Supabase: database hosting, authentication, file storage
• Stripe: payment processing for subscriptions, hardware, and donations, and storing the card you save for your plan
• Google Cloud: text-to-speech for the Inclusion Bar; translation
• Google Analytics: website and app usage analytics, only with your consent
• Meta Platforms: measuring our Instagram and Facebook ads (Meta Pixel and Conversions API), never on Experience pages or in the iOS app, and not after you decline
• Anthropic: AI-assisted building (drafting and editing Experience content from what a builder types or the website they point to). Visitor data is not sent.
• OpenAI: AI-assisted building (drafting and editing Experience content from what a builder types or the website they point to) and AI design generation. Visitor data is not sent.
• RevenueCat: records plans bought in the iPhone app through the App Store (purchase status only)
• Cloudflare: transactional email delivery, and aggregate, cookieless usage statistics for the getnearfield.com website (Cloudflare Web Analytics)

Data Retention

Account data is retained for the duration of your account. If you delete your account, your profile, Experiences, and any visitor data captured by your Experiences will be removed. Anonymous analytics may be retained in aggregate. Visitors can request deletion of their own visitor profile from any Experience using the "Forget me" control in the accessibility menu. This is immediate and irreversible.

Visitor Rights

Visitors can:

• Decline analytics and personalization at any time using the cookie banner or the accessibility menu.
• Delete their visitor profile on a given Experience via "Forget me".
• Contact the Experience owner directly to access or correct data they entered.
• Contact us at hello@getnearfield.com if the owner is unreachable.

Builder Rights

Builders may access, update, or delete their account information at any time from the Account settings page. Subscription cancellations and data deletion can also be requested via support.

Security

We implement industry-standard security measures including encrypted data transmission (TLS), row-level security policies on all database tables, and secure server-side credential management. Service role keys never reach the browser.

International Transfers

Our infrastructure is hosted in the United States. If you access NearField from outside the US, you understand that information will be transferred to and processed in the US under standard contractual safeguards offered by our subprocessors.

Children's Privacy

NearField is not directed at children under 13. We do not knowingly collect personal information from children. Builders are prohibited from using capture blocks to collect personal data from children under 13 without verifiable parental consent.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. Material changes that affect visitor data will trigger a fresh consent prompt.

Contact

NearField
St. Petersburg, Florida
hello@getnearfield.com