Skip to legal content
PriceField.ai
PrivacyTerms

PriceField Privacy Policy

Effective date: 9 September 2026
Last updated: 9 September 2026

1. Who we are and what this policy covers

PriceField is operated by Pricefield, Inc., a Delaware corporation with Delaware file number 10406226, of 1111B S Governors Ave, STE 580, Dover, Delaware 19904, USA ("PriceField," "we," "us," or "our").

This policy explains how we handle personal information when you use:

  • the PriceField mobile application;
  • PriceField accounts, workspaces, social and messaging features, farm and market tools, and analytics features;
  • our public website at pricefield.ai; and
  • related support, email, and communications.

It does not govern an external website or service that has its own privacy notice, including an article publisher you choose to open from PriceField or an identity provider you choose for social sign-in.

2. At a glance

PriceField is a professional and agricultural platform. We use account, profile, workspace, farm, location, content, relationship, and technical information to provide the service. Some profile, workspace, post, comment, and interaction information is visible to other people according to the feature and your settings. Direct messages and private workspace material are intended for their selected recipients, but they are stored and processed by PriceField and are not represented as end-to-end encrypted.

The released app uses Microsoft Clarity and Sentry to understand use of the app, replay sessions, investigate errors, and improve performance. Those tools can be associated with your PriceField or authentication identifiers. Section 5 explains this in more detail.

The app also uses location for map, address, weather, and farm-analysis features. We do not continuously monitor background location; location is requested while you use the relevant feature.

3. Information we collect

We collect information from you, from other people who interact with you or invite you, automatically from your device and use of the service, and from service providers involved in authentication and delivery.

3.1 Account and authentication information

This can include:

  • name, email address, additional email addresses, and email-verification status;
  • password-enabled status and authentication credentials handled by our authentication provider (PriceField does not receive your plain-text password);
  • PriceField, Clerk, workspace, actor, session, passkey, and linked-account identifiers;
  • authentication method, sign-in and password-reset activity, session timestamps, and approximate city and country associated with sessions; and
  • if you choose Apple, Google, or Facebook sign-in, the provider-specific identifier and profile details the provider and you authorize, such as name, email address, or profile image. The exact information depends on the provider and permissions you approve.

Someone may also give us your email address, proposed role, and workspace information when inviting you to a PriceField workspace.

3.2 Profile, workspace, and professional information

This can include:

  • username or handle, display name, biography, country, professional role, profile image, and profile visibility and searchability choices;
  • business or workspace name, type, description, logo, website, founding year, business email, telephone number, and mobile number;
  • address, city, state or region, postal code, country, and geographic coordinates;
  • membership, job role, permissions, invitation status, and workspace relationships; and
  • business characteristics and interests for participants such as farmers, buyers, suppliers, consultants, investors, financial institutions, associations, academia, media, event organizers, and startups.

3.3 Farm, crop, market, and analytical information

Depending on the features you use, this can include farm size and status, operations, crops and products, establishment year, irrigation and water access, equipment, facility distances, photos, crop yields and units, cost categories and percentages, country and currency preferences, watched markets, climate-factor inputs and results, and market or price interests.

Some of this information may be commercially sensitive.

3.4 Location information

With device permission, the app can request your current foreground location to suggest or select an address or farm location. You can also search for a place or move a map pin. We may process:

  • precise latitude and longitude;
  • a derived or entered address, city, state or region, postal code, and country;
  • map position and interactions; and
  • coordinates and date or weather parameters used to provide current weather and climate analysis.

PriceField stores coordinates when you save a workspace, farm, or analytical profile. Mapbox receives information needed to render and operate maps and may receive SDK telemetry as described in its privacy materials and the settings made available for the map. For current weather and climate calculations, our servers send coordinates and relevant query parameters to Open-Meteo. Open-Meteo receives the request from PriceField's server rather than directly from the mobile app, but the request can contain the coordinates you supplied.

The app requests location while in use and does not use continuous or background-location monitoring. Your operating system may provide reverse-geocoding services when the app converts coordinates into an address; the provider can depend on the device and operating system.

3.5 Content, communications, and social activity

This can include:

  • posts, comments, replies, reactions, shares, photos, attachments, and client-generated content identifiers;
  • direct-message content, conversation participants, timestamps, and read status;
  • follows, professional connection requests, workspace relationships, topic and market watches, blocks, mutes, saved items, and article interactions;
  • reports, report reasons and notes, moderation status, and hidden content;
  • in-app notifications, read status, and notification preferences; and
  • media and files, including original file name, file type, byte size, checksum, storage metadata, and the uploaded contents.

Do not include information in a public post, profile, or workspace field that you do not want its intended audience to see. Current post creation uses a public "everyone" audience. Profile and cover images may be returned with public profiles even when other profile fields are restricted.

3.6 Search, preferences, and information stored on your device

Search terms are sent to PriceField when you search the service. The app also keeps up to eight recent search terms on your device, together with theme and language preferences. These local recent searches currently remain on the device after sign-out unless app storage is cleared. Our servers and operational logging can also process request paths and query strings; this can include search text or coordinates until the logging configuration is changed or the data is deleted under the applicable schedule.

Authentication tokens are stored using the device's secure-storage facility. The app can read device language and app or operating-system information needed for localization, updates, security, and compatibility.

3.7 Device, network, usage, replay, and diagnostic information

We and our service providers can process:

  • IP address, user agent, device and operating-system type and version, app version, language, network and protocol information, and per-install or device identifiers;
  • screens visited, navigation, taps, swipes, feature use, custom product events and tags, search or interaction activity, session timestamps, and app-launch events;
  • request path, query string, response status, duration, request or event identifiers, and similar operational metadata;
  • crash and error information, stack traces, performance traces, logs, and update or download errors; and
  • session-replay data described in Section 5.

The public PriceField website has no active user-submission form or first-party analytics code. Its hosting provider may still process ordinary request and security data, such as IP address, requested URL, time, and browser information.

3.8 Support and administrative information

If you contact us, we process the content of the request and the contact details and records needed to respond. We can also keep records of consent, privacy requests, security events, legal notices, and administrator actions where implemented or required.

3.9 How information is linked

Most information sent to PriceField is linked or reasonably linkable to you because you submit it while signed in or because it carries a user, actor, workspace, device, installation, session, request, email, IP, or content identifier. Sentry is explicitly given an account identifier and may receive actor and workspace identifiers. PriceField attempts to give Clarity a Clerk account identifier; Clarity also uses its own persistent identifier. Expo uses a persistent per-install identifier. Open-Meteo receives coordinates and weather parameters from our server without a PriceField account identifier, although the coordinates remain linked to your farm or workspace inside PriceField. Calling information “masked,” “hashed,” “pseudonymous,” or “deidentified” does not necessarily make it anonymous.

3.10 Information from public and third-party sources

We receive news and related material through configured feeds and ingestion systems. This can include the source and article URLs, author or byline, title, summary, body, images, categories, tags, publication data, and source-provided metadata. We also receive reference catalog, market-price, geographic, weather, climate, and currency-rate data from third-party or public sources. We keep source and provenance information so that we can display, categorize, attribute, update, and troubleshoot that material. A chosen identity provider and other PriceField users can also provide information about you as described above.

4. Why we use information

We use information to:

  • create, secure, and administer accounts and sessions;
  • create profiles, workspaces, farms, invitations, memberships, and professional relationships;
  • publish and deliver content, messaging, notifications, maps, weather, market, crop, cost, yield, and climate features;
  • personalize feeds, suggestions, watched topics and markets, units, currency, and language;
  • enable search, saved items, follows, connections, blocks, mutes, and reports;
  • store and deliver photos, documents, and other media;
  • authenticate requests, prevent abuse, investigate fraud or security events, and enforce our Terms;
  • operate, debug, measure, maintain, and improve the service, including by using session replay and diagnostics;
  • send account, verification, invitation, security, and important service communications;
  • comply with law, respond to valid legal process, and protect users, PriceField, and others; and
  • establish, exercise, or defend legal claims and support a merger, financing, acquisition, reorganization, or sale, subject to applicable law.

PriceField will not offer paid plans, trials, in-app purchases, or other fees at launch, and the mobile app does not collect payment-card information or provide checkout at launch. If paid services are introduced later, this policy and the Terms will be updated before that processing begins.

At launch, PriceField will not send promotional marketing or weekly digest emails. If those communications are introduced later, we will update this policy and implement any consent, preference, and unsubscribe controls required by law before sending them.

5. Session replay, analytics, and diagnostics

Session replay creates a visual reconstruction of how the app was used. It can be more revealing than ordinary event analytics, so the following disclosures are important.

5.1 Microsoft Clarity

PriceField has selected Microsoft Clarity for launch. In released versions where Clarity is enabled, it can run across the app, including authentication, onboarding, profile, social, messaging, location, and analytical screens. It can collect rendered screen and interaction information, navigation, taps, input events, custom events and tags, device and app details, session timing, country or region derived by Microsoft, and persistent Clarity identifiers.

When you are signed in and have opted in, PriceField may associate Clarity activity with your Clerk account identifier. Clarity also uses its own persistent identifier. We do not use your email address as the custom Clarity identifier.

PriceField keeps Clarity off until you see a short explanation and affirmatively opt in. Refusing does not prevent you from using the Service. The Settings → Privacy → Session replay toggle shows whether replay is enabled; PriceField does not display a persistent badge on every screen. Turning the toggle off stops future Clarity capture immediately, and PriceField preserves that choice across future sessions and devices associated with your account. PriceField configures Clarity to exclude screens designed for private messages, relationship evidence, sign-in credentials, and other sensitive material, and applies appropriate masking before capture. Turning replay off does not delete information already sent to Microsoft. Microsoft's current Clarity tools may not permit deletion of one user's data without deleting the project; contact support@pricefield.ai about rights available to you.

Under the current Microsoft Clarity terms, PriceField and Microsoft each make independent decisions about certain Clarity processing, and Microsoft states that it may process Clarity data in connection with Microsoft Advertising. Microsoft requires this notice to explain that Microsoft collects personal information when Clarity is used. Read the Microsoft Privacy Statement for Microsoft's practices.

5.2 Sentry

In configured release builds, Sentry receives app errors, crashes, structured diagnostic logs, performance traces, and session replay. PriceField samples a portion of ordinary sessions and performance traces; sessions involving a reportable error may be captured at a higher rate. Sampling can change as we operate and protect the Service.

Sentry replay can include screen structure, navigation, taps and swipes, request metadata, console or app log context, device and release details, errors, and URLs. PriceField configures Sentry replay to mask text, images, and vectors, but masking reduces risk rather than guaranteeing that no personal information is captured. PriceField explicitly sends an account identifier to Sentry and can attach actor type, actor identifier, and workspace identifier. Turning off Sentry's default personal-information option does not remove identifiers PriceField sends explicitly.

Our server-side Sentry configuration is narrower: it is intended for error reporting and excludes request and response bodies, cookies, headers, query strings, IP addresses, user agents, email addresses, and Clerk identifiers, while it can include an internal PriceField user identifier and operational event or request identifiers. Selected Sentry alerts may be sent to a PriceField Slack workspace.

5.3 Expo app updates and launch measurement

The app uses Expo services to check for and download app updates. Update and Expo Insights requests can include a persistent random per-install EAS identifier, PriceField project identifier, app version, operating-system version, platform, launch event, and a prior fatal update-error message. The app can check for updates when it launches.

6. When we disclose information

We disclose information as described below.

6.1 Other users and workspace participants

We disclose profiles, workspace information, public posts and comments, relationship or interaction information, and other content to the audience for the feature. We disclose direct messages to conversation participants and workspace material to authorized workspace participants. Workspace owners or administrators may exercise the access and control rights shown for their roles in the Service. Blocking, muting, privacy, and searchability settings affect some disclosures but do not necessarily remove previously shared information.

6.2 Providers that help operate PriceField

Depending on the feature and production configuration, recipients include:

Provider or categoryWhat it helps us doInformation it can receive
ClerkAccounts, authentication, sessions, verification and authentication emailAccount and contact details, identifiers, session/security data, chosen sign-in provider data, tokens, and authentication events
Apple, Google, or Meta/FacebookOptional social sign-in selected by youAuthentication request, provider identifier, and the profile information and permissions you authorize; the provider also processes the sign-in under its own terms
Apple or Google operating-system location servicesDevice location permission and reverse geocodingDevice location, coordinates, address query/result, and ordinary device/network information according to your operating system and its settings
Microsoft ClaritySession replay and product analyticsThe Clarity data described in Section 5.1, including persistent identifiers and, when association succeeds, a Clerk account identifier
SentryMobile replay, errors, performance, structured logs, and backend error reportingThe Sentry data and PriceField identifiers described in Section 5.2
SlackSelected operational or error alerts from SentryAlert content configured by PriceField, potentially including identifiers and diagnostic details
MapboxMaps, map interaction, and related SDK servicesCoordinates and map or device usage and telemetry determined by the SDK and production settings
Open-MeteoCurrent weather and historical climate calculationsCoordinates, requested dates, weather variables, timezone parameters, and PriceField server request information
ExchangeRate-APIReference currency exchange ratesBase currency, requested date where applicable, PriceField server information, and an API credential; the request does not include a PriceField user, account, or location identifier
ExpoApp updates and launch measurement; push routing only if activatedPer-install EAS identifier, project/app/device metadata, update and launch information; if push is activated, push token and notification payload
Apple Push Notification service and Firebase Cloud MessagingDownstream mobile notification delivery, only if push is activatedApp/device delivery token and notification payload routed through Expo
ResendImplemented PriceField transactional invitation and verification email deliveryRecipient address, sender, subject, message content, delivery metadata, and—if enabled—open or link interaction data
Amazon Web ServicesImplemented cloud infrastructure and object/media storage pathsUploaded media and files, storage metadata, identifiers, and infrastructure/network data
Better StackCentralized operational logsError logs can include IP address, user agent, request path, identifiers, and error details. Where request logging is enabled, logs can also include query information, forwarding headers, status, and timing.
VercelHosting the public PriceField websiteIP address, user agent, request URL, timestamp, and hosting/security logs

Some providers handle information for PriceField under a service agreement; some, including chosen identity providers and Microsoft for parts of Clarity, also determine aspects of their own processing. A provider's precise legal role depends on the data, service, law, and operative contract. We do not label every recipient a “processor” or “service provider” without confirming those facts.

If promotional email, a weekly digest, or mobile push is activated, we will update this policy and the in-app controls with the actual delivery provider, content, and choices before sending those communications. At launch, the mobile app does not register for mobile push notifications.

6.3 Other disclosures

We may also disclose information:

  • to people or organizations you direct us to, including an external article publisher, browser destination, or share-sheet recipient;
  • to professional advisers, auditors, insurers, and financing parties under appropriate duties of confidentiality;
  • where reasonably necessary to investigate misuse, protect safety, security, rights, or property, or enforce our agreements;
  • when required by law or valid legal process, after assessing the request where permitted; or
  • in connection with a proposed or completed corporate transaction, with notice and protections required by applicable law.

7. Public and private information

Public profiles, workspace profiles, profile and cover images, posts, comments, reactions, and some relationship activity can be visible to other PriceField users or the public, depending on the feature. Public information can be copied or reshared by others outside our control.

The private profile setting limits some profile details, but it does not make prior posts or profile and cover images private. The connections_only setting does not prevent access through every direct profile route, and locality can still appear in network search. Turning off searchability removes a profile from discovery results but does not make a direct profile link inaccessible.

Direct messages, relationship-verification evidence, restricted workspace material, and private analytical records are not intended to be public. Conversation participants receive direct messages, and workspace participants can access workspace material according to their assigned roles. PriceField's systems and authorized providers process this information, and authorized personnel may access it when reasonably necessary for support, security, moderation, or legal compliance.

8. How long we keep information

We keep personal information only for as long as reasonably necessary for the purposes described in this policy, including providing the Service, maintaining security, resolving disputes, and meeting legal obligations. The main retention rules are:

InformationRetention approach
Account, profile, workspace, farm, market, and analytical recordsWe keep these records while the relevant account or workspace is active and for as long as needed to provide the requested features. Following a verified account-deletion request, information within the deletion scope will be deleted or appropriately de-identified from active systems within 30 days. Organization-owned workspace and farm records remain available to the organization, but the deleted user's identity will be removed or replaced unless needed for security, audit, or legal reasons. Personal-only drafts and records will be deleted.
Public posts, comments, reactions, reports, and moderation recordsPublic content and interactions are kept while they remain part of the Service. Following a verified account-deletion request, the user's public posts, comments, and media attached to that content will be deleted from active systems within 30 days. Copies made by other people may remain outside our control. Access-restricted abuse reports, moderation decisions, and related safety evidence are kept for 24 months after case closure or account deletion, then deleted or de-identified.
Direct messages and conversation metadataA conversation is kept while at least one participant has an active account and keeps it. If a participant deletes their account, copies needed for the other participants' conversation histories may remain, but the departed sender will be shown as “Deleted user.” After every participant deletes the conversation or their account, it will be deleted from active systems within 30 days.
Uploaded media and relationship evidenceMedia follows the retention of the content or record to which it is attached. Relationship-verification files are deleted within 30 days after the verification or rejection becomes final or any appeal ends. We may retain only the result and minimal audit metadata for 24 months.
Search terms and local app preferencesThe app keeps up to eight recent searches on your device until you clear app storage or remove the app. Server-side copies in ordinary operational logs follow the 90-day log rule below.
Application, request, error, and security logs, including Better StackOrdinary logs are kept for 90 days, then deleted or de-identified. A record relating to a specific incident may be isolated and kept longer for an active investigation, legal requirement, dispute, or valid legal hold.
Clarity replay and derived analyticsMicrosoft makes session-replay playback available for 30 days and can retain certain derived click, heatmap, labeled, or favorite data for up to nine months. Turning replay off stops future collection but does not automatically delete information already collected.
Sentry replay, error, log, and trace dataThese records are kept according to PriceField's Sentry account settings for only as long as reasonably needed to detect, investigate, reproduce, and resolve reliability or security issues.
Email content and delivery recordsThese records are kept for as long as reasonably needed to deliver and troubleshoot the communication, protect the Service, and maintain records required by law.
Event-delivery and processing recordsThese records are kept for as long as reasonably needed to deliver, reconcile, retry, and audit Service operations and to investigate failures or security incidents.
Backups and legal holdsDeleted personal information may remain in isolated, encrypted backups for up to 90 days before expiry or overwrite. It is not used for ordinary operations, and deletion is reapplied if a backup is restored.

We may keep limited information longer where necessary to comply with law, resolve disputes, prevent fraud or abuse, enforce agreements, preserve evidence, or comply with a valid legal hold. When a provider holds information for us, deletion may take additional time under its backup and deletion processes.

9. Legal bases

Depending on the applicable law and the purpose of processing, the legal basis may be one or more of the following:

  • performing a contract with you, such as creating an account and providing features you request;
  • our or another person's legitimate interests, such as protecting the Service, maintaining reliability, preventing abuse, and improving features, where those interests are not overridden by your rights;
  • your consent, where required, such as for device location, non-essential replay or analytics, or certain communications; and
  • compliance with a legal obligation or protection of vital interests.

The legal basis depends on the feature, purpose, information, and law that applies to you. Device permission is not necessarily the same as privacy-law consent. Withdrawing consent does not affect earlier lawful processing, and we may still process information where another lawful basis applies.

PriceField relies on your affirmative consent for Microsoft Clarity session replay. Clarity remains off until you opt in, and you may withdraw that consent at any time through Settings → Privacy → Session replay. You can withdraw operating-system permissions, including location permission, through your device settings.

10. Your choices and privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or a copy of personal information; object to certain processing; withdraw consent; opt out of certain sale, sharing, targeted advertising, or profiling; and appeal a denied request. You may also complain to an applicable data-protection authority.

You can use available profile, visibility, searchability, notification, block, mute, and operating-system location controls. You can turn Microsoft Clarity replay on or off through Settings → Privacy → Session replay. Switching it off stops future Clarity capture immediately and preserves the choice across future sessions and devices associated with your account; it does not automatically erase data already sent to Microsoft. This control does not turn off Sentry diagnostics or Mapbox telemetry.

To exercise a privacy right, contact support@pricefield.ai. Account deletion is also available through Settings → Security → Delete account. We may need to verify your identity and authority. Authorized agents may submit requests where applicable. We will respond within the period required by applicable law and explain any lawful exception.

To delete your account, use Settings → Security → Delete account, complete identity verification, and confirm the request. If you cannot access the app, contact support@pricefield.ai. Following a verified request, PriceField deletes or appropriately de-identifies information within the account-deletion scope from active systems within 30 days, except where retention is legally required or subject to a valid legal hold. Deleted personal information may remain in isolated, encrypted backups for up to 90 days; it is not used for ordinary operations, and deletion is reapplied if a backup is restored.

PriceField deletes the user's public posts, comments, media attached to that public content, and personal-only drafts and records. Organization-owned workspace and farm records remain available to the organization, but the deleted user's identity is removed or replaced unless needed for security, audit, or legal reasons. Direct-message conversations may remain while another active participant keeps them, but the departed sender is shown as “Deleted user.” After every participant deletes the conversation or their account, PriceField deletes it from active systems within 30 days.

11. Advertising, tracking, and regional opt-outs

PriceField does not display third-party advertising in the Service and does not use an advertising SDK.

Microsoft's Clarity terms state that Microsoft may process information collected through Clarity in connection with Microsoft Advertising. Depending on the applicable law, disclosing information for that type of processing may be treated as “sale,” “sharing,” targeted advertising, cross-context behavioral advertising, or tracking even when no money changes hands. For that reason, PriceField keeps Clarity off until you affirmatively opt in. You may stop future Clarity collection at any time through Settings → Privacy → Session replay and may contact support@pricefield.ai about rights available where you live.

Browser “Do Not Track” signals are not a uniform legal mechanism. The PriceField website does not use first-party analytics or advertising tracking at launch, so such a signal does not alter a website tracking feature.

12. International transfers

PriceField is based in the United States, and PriceField and its providers may process information outside your country. Where applicable law requires a transfer safeguard, PriceField will identify and put an appropriate lawful mechanism in place before making the transfer. Depending on the countries and provider arrangement involved, this may include an adequacy decision, standard contractual clauses, a UK addendum, or another lawful transfer mechanism.

Contact support@pricefield.ai to request information about safeguards that apply to your information, subject to lawful redactions.

13. Children

PriceField is intended only for people aged 18 or older. Because the Service is intended for adults, it does not offer a parental-consent route for children. If we learn that an account belongs to someone under 18, we may suspend or delete the account and take appropriate steps regarding the information, subject to applicable law. Contact support@pricefield.ai if you believe an under-age person is using the Service.

14. Security

Technical controls in the Service include authenticated requests, device-provided secure token storage, authorization controls, restricted media-upload mechanisms, and limits on server-side diagnostic capture. No system is completely secure.

If you believe your account or information is at risk, contact support@pricefield.ai.

15. Changes to this policy

We may update this policy as the service, providers, or law changes. We will post the updated version and change the “Last updated” date. For a material change, we will provide at least 30 days’ advance notice by email, a prominent in-app notice, or both. A change may take effect sooner when reasonably necessary to comply with law or address an urgent security or safety issue; where practicable, we will explain the reason and provide notice as soon as reasonably possible. Where the law requires consent, we will obtain it before the affected processing begins.

16. Language

This policy is written in English. If we provide a translation, it is for convenience, and the English version controls unless mandatory local law requires otherwise.

17. Contact us

For privacy questions or requests:

Pricefield, Inc.
1111B S Governors Ave, STE 580, Dover, Delaware 19904, USA
support@pricefield.ai

© 2026 PriceField.ai. All rights reserved.
PrivacyTermsBack to top