CrossPin Privacy Policy
Publication date: 14 October 2026 Effective date: 14 October 2026 Version: 1.0
1. Who is responsible
CrossPin is provided under the registered business name CrossDevApps, an Ontario, Canada sole proprietorship (“we” or “us”). This policy covers the mobile/desktop apps, connection and purchase services, and support. Visits to crosspin.app are covered by our Website Privacy Notice.
Contact our Privacy Officer at support@crosspin.app, +1 639-307-5156, or at our business correspondence address: 6-2160 Highway 7, Suite 107, Vaughan, ON L4K 1W6, Canada. Use “Privacy request” or “Privacy complaint” as the email subject.
2. What stays on your devices and what uses the network
Pins, text, drawings, history and attachments are primarily stored on your devices. Pin-content transfers are encrypted between authorised paired devices; connection services forward encrypted traffic. The services can read device, routing, group, network and purchase metadata. Not all service information is end-to-end encrypted against the operator.
CrossPin has no required login account, but uses installation, device, pairing and purchase identifiers, which can be personal information. CrossPin provides no cloud-backup recovery service. Device/OS backups may separately include app content. Local files rely on device protections, and paired devices may retain, export or capture copies.
3. Information and purposes
| Information and source | Purpose and handling |
|---|---|
| Content and attachments you create, paste, select or photograph | Save and display locally; share encrypted content with authorised paired devices. Files may retain names, dates, location or other embedded metadata. |
| Device names, installation identifiers, public keys and pairing/group/membership records generated by the app or pairing | Establish, recover and manage connections, deliver changes and enforce authorised membership. Connection services process readable metadata and some encrypted connection records. |
| IP addresses, request details, connection times, traffic sizes, app/platform versions and operational errors from service requests | Route traffic, deliver compatible services, secure the service, prevent abuse and investigate failures. |
| Product, store, transaction, subscription/expiry/refund status and pseudonymous customer/device/group or recovery records from the app, stores and RevenueCat | Verify, deliver and restore Premium and prevent fraud or duplicate ownership claims. We do not receive full payment-card details through ordinary store checkout. |
| Update requests, including app/project/runtime/update details, operating system and a random installation identifier | Expo/EAS Update delivers mobile software updates. Enabled desktop update checks also send network/app-version information to the update host. |
| Email address, message details and attachments you send to support | Answer requests, resolve problems and handle privacy/security or purchase matters. Ordinary support email is readable by its recipients and is not covered by Pin-transfer encryption. |
We do not sell personal information, use it for cross-company targeted advertising, or integrate advertising, session-replay or general behavioural-analytics SDKs in the CrossPin apps. Purchase/subscription analytics, update delivery and operational/platform records remain part of the services described here.
4. Permissions and choices
Camera access supports QR scanning and taking photo attachments. Photo/file access supports selected attachments; local-network access supports nearby connections. Clipboard reads occur when you choose Paste; Copy writes the selected content to the system clipboard. Manage permissions in device settings; denying one can prevent its feature from working.
Mobile apps automatically contact Expo for update checks and can initialise RevenueCat/store offering requests on launch, before pairing or purchase. Using CrossPin without pairing does not disable those contacts or clear an existing remembered group. There is currently no in-app switch disabling these SDK requests. Desktop update behaviour depends on the distributed build. OS/store update and backup controls operate separately.
5. Service providers and other recipients
Information is disclosed as needed to:
- Your authorised paired devices and their users.
- Cloudflare, for connection/purchase infrastructure and related storage, and OpenAI Sites with Cloudflare for website hosting/delivery/security as explained in the Website Privacy Notice.
- RevenueCat, for store integration, purchase verification, entitlement records and subscription analytics.
- Expo, for mobile update hosting/delivery and technical requests; desktop download/update hosts handle the corresponding file and update requests.
- Apple or Google, for store/payment/subscription/refund and platform services, including their independent activities.
- Spacemail (Spaceship, Inc.), for support/privacy email hosting, messages and attachments, with US processing and automated security screening that may use AI.
Provider information: Cloudflare, RevenueCat, Expo, OpenAI, Apple, Google and Spacemail.
We may also disclose information to meet a valid legal requirement, protect people, establish or defend claims, or complete a lawful business transfer with appropriate protections. We cannot provide plaintext Pins that we do not possess or decrypt server-side.
6. International processing and legal grounds
We operate from Canada. Providers and their subprocessors may process information in the United States and other service locations, rather than only in Canada or your country.
For covered EEA/UK transfers, Cloudflare and RevenueCat provide European standard contractual clauses and UK Addendum safeguards. Cloudflare and Expo also participate in applicable Data Privacy Framework arrangements. Spacemail's standard terms include European standard contractual clauses for covered transfers. OpenAI's applicable Sites hosting terms provide European and UK safeguards for website visitor data. These mechanisms have defined scopes; they are not a claim that European clauses satisfy every country's rules. Contact the Privacy Officer for information about the safeguards applicable to your data and how to obtain a copy, subject to necessary redactions.
For EEA/UK processing, the grounds are contract for requested connections/Premium; legitimate interests in delivering compatible updates and accurate store offerings, securing services, preventing fraud, handling ordinary support and legal claims; applicable legal obligations; and consent where required. Essential technical or purchase information is needed for its feature. In other locations, the applicable consent or other lawful-authority requirements apply. Terms acceptance is not blanket privacy consent; processing or device storage/access that requires consent needs its own valid choice.
7. Retention, reset and deletion
Local content remains until deleted by you, relevant sync/timer actions, or the app/device storage lifecycle. Offline devices, exports and backups may retain copies. Removing a device does not remotely wipe information already received.
Reset removes local content/settings but may retain installation/security identities, purchase-restoration or anti-replay records and pending departure-delivery information. It does not cancel subscriptions, erase store history or automatically delete all service/provider records.
- Connection/membership, encrypted delivery and security-control records are retained to maintain connections, reconcile pending changes and prevent removed devices or replayed requests from regaining access. Some records are replaced, acknowledged or removed as those processes complete; others, including some encrypted mailbox/introduction records, currently have no automatic expiry. You can request review and deletion of identifiable records, subject to continuing service/security needs and legal requirements. A record becoming invalid does not itself erase its stored copy.
- Purchase/ownership and recovery information is retained while needed to verify or restore purchased access, handle renewals/refunds/disputes, prevent fraudulent ownership claims and meet applicable legal obligations. Lifetime restoration can require long-term ownership records. Separate short-lived event cleanup does not erase that underlying purchase proof.
- We generally delete ordinary support correspondence and attachments 12 months after case closure or our last substantive contact, whichever is later. We may retain the minimum necessary information longer for a specific dispute, security incident or legal obligation. Privacy-rights/complaint and purchase-restoration records have their separate necessary retention purposes.
- Technical and security records support service delivery, fault diagnosis and abuse investigation. Provider operational logs have separate service-specific windows; Cloudflare's Security Events dataset has a 31-day window, while persistent Workers Logs and Traces are disabled on the purchase-verification service. We keep any separately preserved incident evidence only while needed for the identified investigation, dispute or legal obligation. Purchase-verification event cleanup is separate from long-term ownership records needed for restoration.
- Provider backups and historical copies follow their recovery/deletion cycles and lawful preservation requirements. Spacemail describes daily email backups retained for up to four weeks, separately from ordinary mailbox retention.
We explain applicable retention exceptions and material restoration consequences when handling deletion requests. Deletion does not promise forensic erasure from every device, export or backup.
8. Requests, complaints and regional rights
Email the Privacy Officer to request access, correction, deletion or other rights. We use proportionate verification; do not send passwords, full card details, private keys or pairing codes.
Depending on applicable law, rights include access/copies, correction, deletion, portability, restriction, consent withdrawal, appeals and review of relevant automated decisions. Some rights have lawful exceptions, which we explain. Consent withdrawal does not invalidate earlier lawful processing, and we do not penalise lawful rights requests.
You may object to processing based on legitimate interests. Contact the Privacy Officer to exercise this right.
Canadian access requests ordinarily have a 30-calendar-day response period; EEA/UK rights requests ordinarily have one calendar month, with permitted exceptions/extensions and required notices. UK privacy complaints are acknowledged within 30 days and investigated with progress/outcome communicated without undue delay. Other applicable local deadlines and appeal rights remain.
You may complain to the Canadian Privacy Commissioner, competent EEA authority, UK ICO or another competent regulator without first giving up other remedies. Automated purchase/security checks can affect access; contact support to challenge an incorrect result.
For applicable US state rights, we honour required appeals and recognised opt-out signals where relevant. We do not sell information or share it for cross-context behavioural advertising. Browser Do Not Track signals do not currently change necessary service processing.
9. Children
CrossPin is intended for people aged 13 or older, subject to any higher local age, capacity or guardian-permission requirement. Under-13s should not use it. Contact the Privacy Officer about suspected unlawful child-data processing or for parent/guardian assistance.
10. Policy changes
We identify the date/version, retain material previous versions and provide appropriate notice of material changes. We obtain any consent required before new processing begins. Policy changes do not reduce statutory privacy rights.