FIELDPOINT
Privacy Policy
Effective date: 9 September 2026
Last updated: 24 September 2026
Our privacy promise
FieldPoint is designed to be private by default. Core training, course, equipment and lawful field-use data is stored and processed on your iPhone and Apple Watch rather than in a FieldPoint-operated user-data cloud. The core app does not require a FieldPoint account. We do not sell your personal information, run an advertising data business, or use your health, fitness, location or session data for behavioural advertising or profiling.
1. Who we are and how to contact us
FieldPoint Sporting Technologies Limited ("FieldPoint", "we", "us" or "our") is a company incorporated in Scotland under company number SC900731. Our registered office is: Ord Bàn, 16 Macbean Road, Kincraig, Highland, United Kingdom, PH21 1AD.
Privacy contact: hello@fieldpointapp.com
Website: fieldpointapp.com
For UK and EEA data protection purposes, FieldPoint Sporting Technologies Limited is the controller of personal data that we receive and determine how to use. Some FieldPoint functionality also processes personal data locally on your device without that data being transmitted to or accessible by us; this policy explains that local processing as well as the personal data we actually receive.
2. Scope of this policy
This policy applies to:
· the FieldPoint iPhone and Apple Watch applications (the "App");
· our website at fieldpointapp.com and any FieldPoint pages that link to this policy (the "Website");
· FieldPoint beta testing, including TestFlight participation, beta enquiries, tester feedback and deliberately submitted diagnostic files;
· support, enquiries and other direct communications with us; and
· commercial and transaction information that Apple or another authorised service provider makes available to us in connection with the App.
This policy does not replace the privacy terms of Apple, Squarespace, social networks, email providers or other third-party services that you independently use. Their own privacy policies apply to their processing.
3. The most important distinction: on-device data and data FieldPoint receives
3.1 Core App data is local-first
FieldPoint is deliberately designed so that the ordinary operation of the core App does not require a FieldPoint-operated database of your private sessions. Subject to your device settings and the Apple services you choose to use, the following categories are intended to remain on your device or within Apple's platform architecture rather than being transmitted to FieldPoint:
· training and shooting session data, including detected shots, ends/stages, timing, cadence, hold and shot-cycle metrics, distances, scores and FieldPoint training calculations;
· bow, arrow, release, rest and other equipment information;
· course and Spot & Stalk / lawful field-use routes, GPS points, animal/shot/trail/recovery markers and precise shooting or hunting locations;
· target photographs, hunt photographs, notes, species information and permit/tag images or identifiers, unless you deliberately export or share them;
· Apple Health / HealthKit data such as heart-rate and workout information, except to the extent Apple processes that data under your Apple settings;
· raw motion and sensor data used for shot detection, which is intended to be processed transiently unless a user-visible feature or deliberate beta diagnostic export requires retention; and
· local FieldPoint history, archives and local personal shot profiles or calibration settings.
Important: Apple may process information through services such as HealthKit, device backup, Apple Maps/MapKit, WeatherKit, StoreKit, App Store Connect, TestFlight and Apple diagnostics under your Apple account and device settings. That is not a FieldPoint-operated user-data cloud.
3.2 Data we may actually receive
FieldPoint may receive personal data when you choose to interact with us or when a platform/service provider makes limited information available to us. This can include:
Contact and beta application data
Examples: Name, email address, country/region, Apple Watch and iPhone model, bow type, shooting discipline, messages and any information you choose to include in an enquiry or beta request.
Why we use it: Responding to you, selecting/inviting testers, administering the beta, understanding the range of devices, equipment and shooting contexts represented in the test group, and providing support. We do not use Beta application details to add you to a marketing mailing list unless you separately choose to receive marketing.
Beta/TestFlight information
Examples: Where Apple makes it available: invitation name/email, tester status, build/app version, device model, OS/watchOS version, sessions, crashes, screenshot feedback, comments and technical context supplied through TestFlight.
Why we use it: Administering beta access, understanding compatibility, investigating defects and improving the App.
Diagnostic or calibration material you deliberately provide
Examples: Technical logs, motion/calibration recordings, screenshots, exported files and, if specifically included, session, location or health-related metrics.
Why we use it: Troubleshooting a specific problem, detector validation and beta improvement. We do not require production users to contribute private motion/session data for model training.
Website technical data
Examples: Browser, network and device information, IP address, referrer, pages visited, clicks, scrolling, searches and timestamps, depending on Squarespace settings and your cookie choices.
Why we use it: Operating, securing and understanding use of the Website.
Commercial and transaction data
Examples: App Store/StoreKit transaction or subscription status, product/entitlement information and other commercial information Apple provides to us. We do not receive your full payment card details from Apple.
Why we use it: Providing purchased functionality, subscription administration, accounting, fraud prevention and legal compliance.
Communications and support records
Examples: Email correspondence, feedback, complaints and records of how we responded.
Why we use it: Customer support, product improvement, dispute handling and business records.
Social media interactions
Examples: Your public handle/profile information and messages if you contact or interact with FieldPoint through a social platform.
Why we use it: Responding to you and managing our public presence on the relevant platform.
4. Where personal data comes from
We obtain personal data from the following sources:
· directly from you, for example when you email us, apply for the beta, send feedback or deliberately send a diagnostic file;
· from your use of the App on your own device, where the App processes information locally to provide the feature you requested;
· from Apple, for example through App Store Connect, TestFlight, StoreKit, Apple developer diagnostics and other Apple platform services where Apple makes information available to developers;
· from Squarespace and our Website infrastructure when you visit the Website, subject to our site configuration and your cookie choices;
· from our email, hosting, support and professional service providers where they process information on our behalf; and
· from public social media or other public sources if you choose to engage with us there.
5. Purposes and legal bases (UK and EEA)
Where UK GDPR or EU GDPR applies, we must have a lawful basis for each use of personal data. The principal bases we expect to rely on are set out below. The precise basis can depend on the context.
Provide the App and requested features, including local processing on your device
Data: Session, equipment, motion, location and other feature data
UK/EEA legal basis: Performance of a contract / steps at your request; our legitimate interests in providing the requested service. Health data is addressed separately below.
Respond to enquiries and provide support
Data: Contact details, correspondence, support material
UK/EEA legal basis: Our legitimate interests in responding to users and operating the service; steps at your request before entering a contract where applicable.
Administer and improve the beta
Data: Beta application data, TestFlight information, feedback and technical information
UK/EEA legal basis: Our legitimate interests in testing and improving FieldPoint; performance of beta terms where applicable; consent where we specifically ask for optional material.
Process deliberately submitted diagnostics
Data: Technical logs, recordings, screenshots and exported files
UK/EEA legal basis: Consent and/or our legitimate interests in investigating the issue you asked us to investigate. If material contains special-category health data, we use an Article 9 condition such as explicit consent where required.
Operate and secure the Website
Data: Necessary cookies, IP/device/browser/security data
UK/EEA legal basis: Our legitimate interests in providing and securing the Website and preventing misuse.
Website analytics where non-essential cookies or similar technology are used
Data: Website usage and analytics data
UK/EEA legal basis: Consent where required by applicable e-privacy/cookie law; otherwise legitimate interests where lawful.
Manage purchases/subscriptions and business records
Data: Commercial/transaction information
UK/EEA legal basis: Performance of a contract, legal obligations, and legitimate interests in administering our business and preventing fraud.
Send direct marketing, if we introduce it
Data: Name, email and marketing preferences
UK/EEA legal basis: Consent where required; otherwise legitimate interests or another lawful basis where direct-marketing law permits. You can opt out at any time.
Protect legal rights and comply with law
Data: Relevant records and communications
UK/EEA legal basis: Legal obligation and/or legitimate interests in establishing, exercising or defending legal claims and protecting users, FieldPoint and others.
Is providing data mandatory? There is no general statutory requirement to give FieldPoint personal data in order to use the core App. If you do not grant an optional device permission, the feature that depends on it may be unavailable or reduced, while unrelated features should continue where technically practical. If you do not provide contact information, we may be unable to respond to you or invite you to a beta that requires an email invitation.
6. Health, fitness and special-category data
FieldPoint is a sport and training product, not a medical service. FieldPoint-derived workload, fatigue, heart-rate context and similar metrics are training estimates and are not diagnoses or medically validated measurements.
If you enable Apple Health / HealthKit features:
· HealthKit remains the system of record for Apple Health-derived information;
· the App requests only the HealthKit data types needed for the feature and Apple requires granular permission to read or write each relevant type;
· we do not use HealthKit, Motion & Fitness or related information for advertising, marketing audiences, behavioural profiling or data-broker activity;
· we do not operate a general cloud database containing your HealthKit history; and
· you can change Health permissions through Apple system settings. Removing a permission may disable or reduce the related FieldPoint feature.
Under UK/EU data protection law, health data can be special-category personal data. Where data protection law treats FieldPoint as processing health data and a separate Article 9 condition is required, we rely on an appropriate condition such as your explicit consent. Where we ask you to deliberately send us a diagnostic file that contains health information, we will require an express choice/consent appropriate to that submission and will use it only for the stated support or beta purpose unless another lawful basis applies.
7. Location, course and lawful field-use data
Precise shooting, course and hunting locations can be particularly sensitive. FieldPoint therefore applies heightened protection:
· precise course and Spot & Stalk / hunting locations are intended to remain in the local FieldPoint database unless you deliberately export or share them;
· FieldPoint does not automatically publish or upload hunting locations;
· when sharing features are available, precise GPS and health values are excluded by default and should require an affirmative choice to include;
· permit/tag images or identifiers remain local unless you explicitly export them; and
· where weather or map information is required, FieldPoint prefers direct device-to-platform services rather than routing exact locations through a FieldPoint backend.
8. Photos, notes, target data and documents
Target photographs, lawful field-use photographs, notes, equipment information, target/score data and permit/tag material are private by default and are intended to remain on your device. Future or current photo/scoring features may analyse images on-device. We will not upload this content to FieldPoint merely to provide a feature if the feature can reasonably be delivered locally. If a later feature requires external/cloud processing, we will update this policy and provide the required notice and choice before that processing begins.
9. Sharing and exports
Sharing is user-initiated. FieldPoint may help you create a Share Card, export, archive, CSV or other user-controlled output. When you choose to share:
· only the information you select for the particular share/export should leave the private App;
· sharing one session does not give the recipient access to your wider FieldPoint history;
· precise GPS is excluded by default and health metrics are excluded by default unless you deliberately choose to include them;
· the operating-system share sheet may be used so that you choose the destination; and
· once you send information to another person, social network, cloud drive or service, that recipient/service processes it under its own terms and privacy policy.
10. Beta testing, TestFlight and diagnostics
FieldPoint beta builds may contain additional diagnostic capability to help us validate shot detection and other functionality. This is separate from the intended production privacy model.
· If you join by email invitation, Apple can make your invited name/email, device/OS, build access, session/crash metrics and feedback available in App Store Connect. If you join using a TestFlight public link, Apple may present you to us as anonymous unless you choose to provide contact information in feedback.
· TestFlight feedback can include screenshots, written comments, crash reports and technical device context. Apple controls how this information is collected and made available to developers.
· FieldPoint may ask consenting testers to deliberately export a specific calibration, motion or diagnostic recording. We do not silently upload production users' private motion/session history for model training.
· Diagnostic files should be limited to what is needed for the test. If a requested file may include health, location or other sensitive content, we will tell you and request any consent required before you send it.
11. Website, cookies and analytics
Our Website is hosted using Squarespace. Squarespace and associated infrastructure necessarily process some technical information to serve pages, maintain security and operate the site. Depending on the Website settings in force and your cookie choices, Squarespace analytics can process information such as browser/network/device information, IP address, referrer, pages visited, clicks, scrolling, searches and timestamps.
We distinguish between:
· strictly necessary cookies or similar storage needed to provide and secure the Website; and
· non-essential analytics or other cookies, which we will restrict or seek consent for where applicable law requires it.
If the Website uses non-essential cookies, our cookie banner or cookie settings should let you accept, reject or change those choices. A separate Cookie Policy may provide the current cookie names, providers, purposes and durations because those details can change as Website configuration changes.
Third-party embeds and integrations. If we add embedded maps, videos, social widgets, Google Analytics, Meta technologies or other third-party integrations, those services may receive visitor information. We will update the Website notices and consent controls as required before enabling them.
12. Who we share personal data with
We do not sell your personal data. We disclose personal data only where needed for the purposes described in this policy, including to:
· Apple, when you use Apple platform services such as App Store, TestFlight, StoreKit, HealthKit, Maps/MapKit, WeatherKit or Apple developer diagnostics. In many cases Apple receives data directly from your device and FieldPoint does not receive the underlying content;
· Squarespace, which hosts and operates the Website and may provide Website analytics and security services;
· our email, hosting, IT/security and support service providers, including Google Workspace and Google Drive where used for FieldPoint email and Beta administration, to the extent necessary to deliver those services;
· professional advisers such as accountants, lawyers and insurers where reasonably necessary;
· a buyer, investor or successor in connection with a genuine corporate transaction, subject to appropriate confidentiality and data-protection safeguards; and
· regulators, courts, law enforcement or other authorities where disclosure is required by law or reasonably necessary to establish, exercise or defend legal rights.
We require processors acting on our behalf to handle personal data under appropriate contractual and security obligations. We do not authorise service providers to use FieldPoint-controlled personal data for their own advertising or behavioural profiling.
13. No sale, advertising data business or cross-context behavioural profiling
FieldPoint does not sell personal data. We do not share personal data for cross-context behavioural advertising, use HealthKit/session/location information to build advertising audiences, or provide private FieldPoint data to data brokers. The production App is intended not to include ad-tech, fingerprinting, cross-app tracking or behavioural-profiling SDKs.
We do not offer financial incentives in exchange for personal information and do not discriminate against you for exercising a privacy right.
14. International transfers
FieldPoint is established in the United Kingdom. Some service providers, including global technology providers, may process personal data in the United Kingdom, European Economic Area, United States or other countries.
Where UK or EU data protection law requires safeguards for a transfer to a country not recognised as providing adequate protection, we will use an available lawful transfer mechanism, such as an adequacy regulation/decision, the UK International Data Transfer Agreement or UK Addendum, EU Standard Contractual Clauses, or another approved safeguard used by the relevant provider. You may contact us for more information about the safeguards applicable to personal data we control.
15. Retention and deletion
We keep personal data only for as long as reasonably necessary for the purpose for which it was collected, taking into account legal, accounting, security, support and dispute-resolution requirements. Core App data that we do not receive is controlled through the App and your device rather than retained in a FieldPoint server.
General enquiries and support correspondence
Typical retention / criteria: Normally up to 24 months after the last meaningful contact, unless an ongoing relationship, legal issue or support need requires longer.
Beta applications and ordinary tester administration records
Typical retention / criteria: For the beta/testing relationship and normally up to 24 months afterwards, unless retained longer for legitimate product, legal or safety reasons.
Deliberately submitted diagnostic/calibration files
Typical retention / criteria: Only as long as reasonably needed to investigate, validate or reproduce the relevant issue; our target is normally no more than 12 months after the relevant test/issue is closed unless you agree to longer retention or a legal need applies.
TestFlight feedback/crash material
Typical retention / criteria: Subject to Apple's platform retention and our need to investigate the relevant build/issue. Apple states that certain TestFlight crash reports are available for limited periods.
Commercial/accounting/tax records
Typical retention / criteria: As required by applicable law, typically up to 6 or 7 years in the UK depending on the record and purpose.
Marketing preferences
Typical retention / criteria: Until you opt out or the contact is no longer needed; we may keep a minimal suppression record so we can respect an opt-out.
Website analytics/cookie data
Typical retention / criteria: According to the relevant Squarespace/cookie configuration and the retention period disclosed in our Cookie Policy or cookie settings.
We may retain information for longer where necessary to comply with law, resolve disputes, investigate security issues, establish or defend legal claims, or where you have asked us to retain information for an ongoing support matter. Information that has been genuinely anonymised so that it is no longer personal data may be retained for product/statistical purposes.
16. Security
We use technical and organisational measures appropriate to the nature and sensitivity of the personal data we control. Our privacy architecture reduces risk by keeping core private session data local rather than copying it into a developer-accessible cloud database. Measures may include platform/device encryption and access controls, least-privilege access to business systems, secure authentication, vendor due diligence, contractual protections, software updates and minimisation/redaction of diagnostic logs.
No system is completely secure. If we become aware of a personal-data breach affecting data we control, we will assess it and notify affected individuals and regulators where applicable law requires us to do so.
17. Children and young people
Archery is practised by adults and young people. The core App is designed to minimise data collection for all users: no core FieldPoint account is required, precise location is private by default, advertising/tracking is not part of the product model, and core private session data is intended to stay on the user's devices.
We do not knowingly use the Website or beta programme to collect personal information online from children under 13 in the United States without any parental consent required by law. If you are under 18, we recommend involving a parent or guardian before sending us personal information, applying for beta testing, submitting diagnostic files or contacting us about a matter that may involve health or precise-location data.
Where the UK Children's Code or similar child-privacy rules apply, we aim to apply high-privacy defaults, data minimisation, age-appropriate transparency and heightened protection for geolocation and profiling. A parent or guardian who believes a child has provided personal data to us inappropriately can contact us at hello@fieldpointapp.com.
18. Automated processing, shot detection and AI
FieldPoint uses algorithms to detect shots, calculate sport/training metrics, segment sessions and present analytics. Current and planned features may also use computer vision or AI to assist with tasks such as target scoring or explaining analytics. These functions are designed to support sporting decisions and user insight.
FieldPoint does not currently make decisions based solely on automated processing that produce legal effects or similarly significant effects on you. Where automated results can materially affect a sporting record, FieldPoint aims to provide appropriate confidence information and/or user correction where practical. If we later introduce an external/cloud AI service that receives personal data, we will conduct a privacy review, update this policy and provide any notice/choice required before launch.
19. Your controls and choices
· Device permissions: use iPhone/Apple Watch system settings to manage Health, Motion & Fitness, Photos, Location and other permissions. Removing a permission can disable the feature that requires it.
· Local FieldPoint data: use available App controls to edit, archive, export or delete local content. Because FieldPoint normally cannot see local private session data, we may not be able to delete that data remotely for you.
· Sharing: review a Share Card/export before sending it and choose the destination through the available share controls.
· Cookies: use the Website cookie banner/settings to manage non-essential cookies where available.
· Marketing: use the unsubscribe method in a marketing communication or contact us. Service/beta/support communications may still be necessary for a relationship you requested.
20. UK, EEA and Swiss privacy rights
If UK GDPR, EU GDPR, Swiss data-protection law or a similar law applies, you may have some or all of the following rights, subject to legal conditions and exceptions:
· access - to obtain confirmation of whether we process your personal data and a copy of data we hold about you;
· rectification - to correct inaccurate or incomplete personal data;
· erasure - to ask us to delete personal data in circumstances provided by law;
· restriction - to ask us to restrict certain processing;
· objection - to object to processing based on legitimate interests and to object at any time to direct marketing;
· data portability - to receive certain data you provided to us in a structured, commonly used and machine-readable format and/or have it transmitted to another controller where the law applies;
· withdraw consent - where we rely on consent, to withdraw it at any time without affecting processing already carried out lawfully before withdrawal; and
· rights relating to solely automated decisions - where applicable, to obtain safeguards concerning decisions based solely on automated processing that have legal or similarly significant effects.
To exercise a right in relation to personal data FieldPoint actually holds, email hello@fieldpointapp.com and describe your request. We may need to verify your identity proportionately before fulfilling a request. We will respond within the period required by applicable law.
For local App data that FieldPoint does not receive or have access to, the practical way to exercise control will normally be through the App, Apple Health or your device settings. Contact us if you need help locating the relevant controls.
21. Complaints in the UK and EEA
We would appreciate the opportunity to resolve a privacy concern directly. You also have the right to complain to a data-protection supervisory authority where applicable.
United Kingdom: Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF, United Kingdom. ico.org.uk
EEA/EU: You may complain to the data-protection authority in the country where you live or work, or where you believe an infringement occurred. If FieldPoint appoints an EEA representative because applicable law requires one, the representative's details will be published with this policy.
Switzerland: Where Swiss law applies, you may also have the right to contact the Federal Data Protection and Information Commissioner (FDPIC).
22. California privacy notice
This section supplements the rest of the policy for California residents where the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, "CCPA"), applies to FieldPoint. If FieldPoint is not a "business" subject to the CCPA in a particular period, we may still choose to honour comparable requests as a matter of policy where reasonably possible.
22.1 Notice at collection and categories of personal information
In the preceding 12 months, or since FieldPoint began operations if shorter, we may have collected/received the following CCPA categories in the limited circumstances described in this policy:
Identifiers
Examples: Name, email address, IP address, online identifiers made available by Website/platform providers.
Sources: You; Apple; Squarespace; service providers.
Purposes: Beta/support administration, Website operation/security, business records.
Internet or other electronic network activity
Examples: Website activity, TestFlight sessions/crashes/feedback metrics, device/browser/network context.
Sources: Squarespace; Apple; your use of the Website/beta.
Purposes: Website operation/analytics, beta testing, security and troubleshooting.
Commercial information
Examples: App Store product, purchase, subscription or entitlement information made available by Apple.
Sources: Apple.
Purposes: Providing paid functionality, accounting, subscription administration.
Geolocation information
Examples: Precise course/hunt location is normally local and not received by FieldPoint. We may receive location information only if you deliberately send a file/feedback containing it or if a service interaction specifically requires it.
Sources: You; platform/service provider where applicable.
Purposes: Support/testing requested by you; never behavioural advertising.
Sensory/technical data
Examples: Motion/calibration data, screenshots, photos or technical recordings only where deliberately submitted for beta/support.
Sources: You; TestFlight where feedback includes screenshots/technical material.
Purposes: Troubleshooting, beta validation and product improvement.
Professional/consumer profile or inferences
Examples: We do not build advertising profiles from your shooting or hunting behaviour. Sports/equipment preferences may be provided voluntarily in beta applications.
Sources: You.
Purposes: Selecting/understanding beta tester coverage and responding to you.
Sensitive personal information
Examples: Health-related data or precise geolocation only if deliberately submitted to FieldPoint in a diagnostic/support context; account credentials/payment card numbers are not required for the core App.
Sources: You; Apple/platform provider where applicable.
Purposes: Only the user-requested support/beta purpose, security/legal purposes and other permitted service purposes.
Contents of communications
Examples: Emails, feedback, support correspondence and attachments sent to FieldPoint.
Sources: You; email/TestFlight providers.
Purposes: Responding, support, beta administration, legal/business records.
Sale/share. FieldPoint does not sell personal information and does not share personal information for cross-context behavioural advertising as those terms are defined under California law. We therefore do not use a "Do Not Sell or Share My Personal Information" mechanism for a sale/share activity that we do not conduct. If our practices change, we will update the required notices and opt-out mechanisms before the change.
Sensitive personal information. We do not use sensitive personal information to infer characteristics about you or for purposes that would require a California "Limit the Use of My Sensitive Personal Information" link. Core precise-location and health data is designed to remain local/within Apple's health architecture, and any sensitive data deliberately sent to FieldPoint is used only for the requested support/test and other legally permitted purposes.
Direct marketing disclosures. We do not disclose personal information to third parties for their own direct-marketing purposes.
Financial incentives. We do not offer financial incentives or price/service differences in exchange for personal information.
22.2 California rights and requests
Where the CCPA applies, California residents may have the right to know/access, delete, correct and receive information about categories/sources/purposes/recipients, and to exercise applicable opt-out or limitation rights. You also have the right not to receive discriminatory treatment for exercising CCPA rights.
Submit a request by emailing hello@fieldpointapp.com with the subject "California Privacy Request". We may verify your identity using information proportionate to the request. You may use an authorised agent where California law permits; we may request proof of the agent's authority and may verify your identity directly. We do not charge for ordinary verified requests except where the law permits a fee.
23. Other United States state privacy rights
Residents of Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia and other U.S. states with comprehensive privacy laws may have rights where the relevant law applies to FieldPoint, including some combination of access, correction, deletion, data portability, and opt-outs of sale, targeted advertising or certain profiling.
FieldPoint does not sell personal information, use personal information for cross-context/targeted behavioural advertising, or conduct profiling that makes decisions with legal or similarly significant effects. To exercise an applicable state right, email hello@fieldpointapp.com with the subject "US State Privacy Request" and identify your state of residence. If applicable law gives you a right to appeal a denied request, you may appeal by replying to our decision or emailing the same address with the subject "Privacy Appeal". We will provide any additional complaint/Attorney General information required by your state law.
24. Canada privacy rights
Where Canadian privacy law such as PIPEDA or applicable provincial privacy legislation applies, FieldPoint is accountable for personal information under its control. We aim to identify the purposes for collection, limit collection to what is needed, obtain meaningful consent where required, limit use/disclosure/retention, use safeguards appropriate to sensitivity, and provide openness and access.
You may request access to personal information we hold about you and ask us to correct inaccurate information. Where processing is based on consent, you may withdraw consent subject to legal or contractual restrictions and reasonable notice; withdrawal may mean we cannot provide the affected feature or service. Contact hello@fieldpointapp.com with the subject "Canada Privacy Request".
If we cannot resolve a concern, you may have the right to complain to the Office of the Privacy Commissioner of Canada (OPC) or the relevant provincial privacy regulator. priv.gc.ca Quebec residents may also have rights under Quebec privacy law and may contact the Commission d’accès à l’information du Québec where applicable.
25. Other countries
FieldPoint may be available in countries whose privacy laws provide additional or different rights. Where those laws apply to FieldPoint, we will honour the rights and obligations required by that law. You can contact hello@fieldpointapp.com if you believe a local privacy rule applies to your use of FieldPoint and is not addressed here.
26. Changes to this policy
We may update this policy when FieldPoint functionality, service providers or legal requirements change. We will update the "Last updated" date and, where a change materially affects how we use personal data, provide additional notice or obtain consent where required before the new processing begins.
A new cloud service, account system, analytics/advertising SDK, external AI service, community/social layer or other architecture that would cause FieldPoint to receive private user content will be treated as a material privacy design decision and will require the relevant public disclosures to be updated before launch.
27. Contact us
FieldPoint Sporting Technologies Limited
Registered in Scotland: SC900731
Registered office: Ord Bàn, 16 Macbean Road, Kincraig, Highland, United Kingdom, PH21 1AD
Privacy email: hello@fieldpointapp.com
Website: fieldpointapp.com
If your question concerns beta participation rather than a privacy right, you may also contact beta@fieldpointapp.com.
Private by design
Your sessions belong to you. The core App is local-first, sharing is your choice, and FieldPoint is not building a business from your health, location or shooting history.