Core app use
No Anchor account
Pairing, modes, selected apps and websites, schedules, and focus history are designed to remain on your device except for the limited iCloud backup described below.
Privacy policy
Core use of Anchor does not require an Anchor account. Most app data stays on your device; this policy explains the limited situations in which information leaves it.
Core app use
Pairing, modes, selected apps and websites, schedules, and focus history are designed to remain on your device except for the limited iCloud backup described below.
Our commitments
We do not sell personal information, run targeted advertising, or use your app selections, DNS requests, or focus history to build an advertising profile.
BNS Development Inc. (“BNS,” “Anchor,” “we,” “us,” or “our”) is an Alberta corporation and is responsible for personal information under our control. This policy applies when you use an Anchor mobile app or our website, buy or receive an Anchor, communicate with us, or make a privacy request.
The app may be downloaded worldwide. Our online store currently accepts orders for delivery in Canada. App-store operators, operating-system providers, communications providers, and other services may also process information for their own purposes under their own privacy notices when you use them.
This policy does not create an Anchor user account and a website purchase is not automatically linked to use of the mobile app. A purchaser may be buying a gift or a multi-pack for other people.
We use order and support contact details for transactional and service communications. Buying or downloading Anchor does not, by itself, subscribe you to general marketing. Optional marketing requires separate consent where required, and every marketing email includes a way to unsubscribe.
Anchor generates or accesses information needed to pair the physical Anchor, configure restrictions, run focus and Feet First sessions, display statistics, recover from interruptions, and honour your settings. Depending on the platform and the features you use, this may include a random local installation identifier, paired-tag identifier and verification information, mode names and settings, selected apps or app categories, selected website domains, active-session state, completed focus history and statistics, alarm schedules, chosen or imported sounds, appearance settings, and permission status.
Except for the iCloud backup and limited analytics described in this policy, this operational app information is designed to be stored and processed on your device. We do not operate a server that receives your paired-tag identifier, local installation identifier, selected apps or domains, custom mode names, active restrictions, imported sounds, or focus history.
Anchor uses Apple's Family Controls and Screen Time frameworks to let you choose and shield apps, categories, and websites. The app and its Screen Time extensions store Apple-provided opaque selection tokens in Anchor's private app-group storage. BNS does not receive the content of your messages, browsing content, photos, contacts, or the contents of shielded apps. Apple controls permission for Family Controls, NFC, Notifications, and Alarm features.
When the iCloud backup feature is available in the version you use and you are signed into iCloud, Anchor stores a backup in a private CloudKit database associated with your Apple account. The backup may contain inactive mode names and settings, completed focus sessions, Feet First schedule and completion information, onboarding status, appearance and strict-mode preferences, analytics preference, and remaining emergency-access count. It excludes the paired Anchor identifier, active sessions, selected apps, app categories, website domains and their opaque Screen Time tokens, and imported custom sounds. BNS does not receive your Apple ID or iCloud email address. Apple processes this backup as the iCloud provider.
Android operating-system cloud backup is disabled for the Anchor app. Android device manufacturers and Google may still process app installation, permissions, and store activity under their own policies.
When Aptabase is configured in the distributed app or website, we use it to understand broad product use and improve Anchor. App events are limited to app opening, setup completion, an Anchor being activated or seen during a day, and the start or end of a focus or Feet First session, with restricted trigger or completion-reason labels. Website events may include a permitted page path, starting or completing the product video, choosing a call to action or package, opening an FAQ, checking product availability, beginning checkout, or submitting the launch notification form. Those website events may also include a broad viewport class, the referring website's hostname, and sanitized campaign tags. We do not send full referrer URLs, page query strings, or campaign values containing an email address or URL. The email address entered in the launch form is not sent to Aptabase.
Aptabase events include an event time, a temporary session identifier, event name and permitted event properties, locale, operating system and version, app version and build, SDK version, debug status, and, on supported SDKs, device model. Like any internet service, Aptabase receives the source IP address and request information. Aptabase states that it creates a per-app daily identifier by hashing the IP address and user agent with an app-specific salt that is discarded every 24 hours. This is designed to prevent identification or correlation across days and apps, but applicable law may still treat some of this technical information as personal information.
Our Aptabase event schemas do not intentionally send names, email addresses, account identifiers, the local installation or paired-tag identifier, advertising identifiers, selected app or domain lists, custom mode names, imported sounds, message or app content, payment information, or precise location. We do not use Aptabase for advertising or cross-app tracking.
App versions configured with Microsoft Clarity also share masked interaction recordings to help us understand navigation and usability problems. Clarity reconstructs sessions from visual layout information and interactions such as taps and scrolling. We configure masking for app content and input fields, including dialogs, to hide text and images such as mode names, app selections, schedules, and usage details. Anchor does not send Clarity your local installation or paired-tag identifier, purchase details, or a custom user ID.
Clarity generates its own random user and session identifiers; its user identifier can persist across sessions. It also processes app, device, operating-system, network, and SDK performance information. Microsoft receives connection information including your IP address and may derive general location from it. These recordings are not anonymous aggregate events. We use them to improve Anchor, not to target ads.
When Google Analytics is configured for the Anchor website, we use it to measure website traffic, campaign performance, product interactions, and checkout starts. Google Analytics may use cookies or similar identifiers and receive browser and device information, page activity, referring information, permitted campaign tags, and IP-address-derived general location. We configure our website events not to send names, email addresses, payment information, support messages, or full referrer URLs and do not use this Google Analytics property to build advertising audiences or target advertising.
On the Anchor website, optional analytics loads only after you select Accept analytics. This includes Aptabase, Google Analytics, and Microsoft Clarity. Clarity records page layout, clicks, scrolling, and navigation to help us identify usability problems. Form inputs are masked; public page text and images can appear in recordings. Clarity uses cookies and generated identifiers to connect visits and receives device, browser, connection, and general-location information. We do not provide a custom customer identity or use these recordings for targeted advertising. You can reject optional analytics or change your choice using Cookie preferences in the website footer.
With website analytics enabled, sanitized campaign tags and a broad referral source (such as Instagram or ChatGPT) are also attached to the Shopify cart so an order can retain its acquisition source. We do not attach your email address, full referring URL, or Clarity user/session identifier. Checkout is hosted by Shopify and has its own privacy controls; leaving our website is not recorded as a completed purchase.
Analytics is enabled by default in the mobile apps and can be disabled at any time under Settings → Usage Analytics (called Anonymous Analytics in older versions). This one setting controls both Aptabase events and Clarity recordings when included in the app. Disabling it stops new collection; information already collected may still be processed or retained by the providers. It does not delete past analytics.
Aptabase processes Anchor analytics in Virginia, United States, and states that it retains app analytics for up to five years. Because the events are not tied to an Anchor account and the daily identifier rotates, BNS and Aptabase generally cannot identify and isolate a particular person's historical events for access or deletion.
Microsoft processes Clarity data in its Azure cloud service. Clarity retention and deletion follow Microsoft's service terms and the project settings. We do not link its generated identifiers to an Anchor account or to your orders. Contact our privacy lead with requests about previously collected data.
Read the Aptabase privacy policy , the Microsoft Privacy Statement , and the Clarity terms . You can also review Google's Privacy Policy and its Analytics opt-out browser add-on .
Our website is hosted and delivered using Vercel. The host and security services may process standard request and security information such as IP address, browser and device type, requested URL, referring page when supplied, timestamps, network and error data, and signals used to prevent abuse and keep the website available.
Product availability and checkout use Shopify. When you view live product availability or open checkout, your browser communicates with Shopify. Shopify and Shopify Payments may process contact, delivery, order, payment, device, interaction, and fraud-prevention information. Optional Shop Pay or other payment methods are governed by the terms and privacy notices shown for those services. BNS is the seller for purchases from our store; Shopify also processes some information for its own stated purposes.
Email providers and communications services process the information needed to deliver support, order, return, warranty, and privacy-request messages. Delivery carriers receive the contact, address, shipment, and customs information needed to deliver and administer an order.
Our contact form uses Formspree to process submissions and deliver them to our support inbox. When you submit the form, Formspree receives your name, email address, topic, message, and any optional order or device details you include.
The Anchor website uses optional Microsoft Clarity session replay as described above. It does not use advertising pixels, cross-site behavioural advertising, or a separate crash-reporting service.
Depending on the law and context, we rely on performing a contract or taking requested pre-contract steps, your consent, compliance with legal obligations, and our legitimate interests in operating, securing, improving, and protecting Anchor. Where we rely on legitimate interests, we consider the information's sensitivity, our limited use, and the available controls. You may withdraw consent or object where applicable, but this does not affect processing already lawfully completed.
We disclose information only as reasonably necessary for the purposes above, including to:
We may transfer information in connection with a proposed or completed financing, merger, reorganization, sale, or transfer of all or part of the business, subject to appropriate confidentiality and use restrictions and applicable law.
BNS is based in Alberta, Canada. Aptabase analytics is processed in the United States. Apple, Google, Microsoft, Shopify, Shopify Payments,Vercel, communications providers, and their subprocessors may process information in Canada, the United States, and other countries where they operate. Those countries may have privacy laws that differ from the laws where you live, and information there may be accessible to courts, law enforcement, or regulators under local law.
Where required, we use contractual terms and other recognized safeguards for international transfers. You may contact our privacy lead for more information about providers, countries, or applicable safeguards.
When information is no longer required, we delete, anonymize, or securely dispose of it as appropriate. Limited copies may remain temporarily in protected backups or logs until they rotate, or longer when retention is required by law or needed for legal claims.
You can review or revoke system permissions in iOS or Android settings. A related Anchor feature may stop working if its permission is unavailable. You can disable mobile-app analytics in Anchor settings. The app's Reset All Data control removes the app data identified in its confirmation and requests deletion of the private iCloud backup where enabled. You may also uninstall the app and use Apple, Google, Shopify, and payment-provider controls for information those services hold.
Depending on where you live, you may have rights to know whether we process personal information about you; request access, correction, deletion, or portability; withdraw consent; object to or restrict certain processing; and appeal or complain to a regulator. You will not be discriminated against for exercising an applicable privacy right. We may need to verify identity, clarify the request, charge a legally permitted fee, or retain information where law permits or requires it.
Much of Anchor's app data stays only on your device and is not available to BNS. Aptabase events are not connected to an Anchor account and generally cannot be isolated by person. We will explain these limitations if they affect a request.
We do not sell or rent personal information. We do not share personal information for cross-context behavioural advertising or use it for targeted advertising. We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects. Shopify or payment providers may independently use automated tools for fraud and payment decisions under their notices.
Anchor is intended for people aged 13 and older and is not directed to children under 13. We do not knowingly collect personal information from a child under 13. A parent or legal guardian may configure Anchor on a child's device and should manage the device permissions and settings. Purchases must be made by an adult or with the involvement of a parent or legal guardian where required.
If you believe a child under 13 has sent personal information to BNS, contact our privacy lead so we can review and delete it where appropriate. We will obtain parental authorization or apply additional protections if a law requires them for a particular user or use.
We use administrative, technical, contractual, and physical safeguards appropriate to the sensitivity and amount of information, including access limitation, secure platform storage, encryption provided by the operating system and service providers, and data minimization. No transmission or storage system is completely secure. If a breach occurs, we will assess it and notify affected people and regulators when required by applicable law.
We may update this policy when our products, providers, practices, or legal obligations change. The revised version will be posted here with a new effective date. If a change is material, we will provide additional notice or request consent where required. The policy in effect when we collected information continues to govern that processing unless law permits or you agree to a change.
Send privacy questions, rights requests, or complaints to the person accountable for privacy at BNS Development Inc.. Please write “Privacy Request” in the subject line. We will respond within the time required by applicable law.
Email info@bnsdevelopments.com