Longhand
Technical Leaders Inc.
Effective Date: May 12, 2026 | Last Updated: October 13, 2026
Longhand is a desktop app for Mac and Windows that runs AI assistants, reusable skills, and workflows, with connected web and team services. Personal connection secrets use an encrypted local vault; organization-managed credentials can be held on Longhand servers. AI requests can go directly to a selected Model Provider or through Longhand's trial or company AI proxy, and can include data read from connected Google services. We also collect product analytics via PostHog and provide support via Intercom. This Privacy Policy ("Policy") explains what data we collect, how we use it, and your rights. Section 4.5 describes Google data and permissions.
This Privacy Policy describes how Technical Leaders Inc., a Delaware corporation ("Company," "we," "us," or "our"), collects, uses, discloses, and protects your personal information when you install, access, or use Longhand and all related services (collectively, the "Service"). This Policy applies to all users worldwide and addresses specific regulatory requirements for users in the European Economic Area ("EEA"), United Kingdom ("UK"), California, Canada, Brazil, South Korea, and other jurisdictions with applicable data protection laws.
By installing, accessing, or using the Service, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with our practices, please do not use the Service. This Policy should be read in conjunction with our Terms of Service.
For the purposes of applicable data protection laws, the data controller is:
Entity: Technical Leaders Inc.
Address: 1062 E Oaks Manor Dr., Fayetteville, AR 72703
Email: privacy@technical-leaders.com
Data Protection Officer: dpo@technical-leaders.com
The Company does not maintain an establishment in the European Economic Area (EEA) and does not engage in large-scale monitoring of EEA data subjects or large-scale processing of special categories of personal data. Accordingly, the Company relies on the exemption under Article 27(2) of the GDPR and has not appointed an EU representative at this time. If the Company's processing activities change such that an EU representative is required, this Policy will be updated to reflect that appointment.
Personal provider keys and Google Workspace access and refresh tokens are stored in the desktop's encrypted local vault. Organization-managed credentials use a separate hosted vault and may be decrypted by authorized service paths for their intended use. These storage and processing paths have different access protections.
Our local-first architecture for API Keys operates as follows:
For personal credentials stored on your device:
We strongly recommend that you:
We collect information that you voluntarily provide when you:
Although Longhand is a desktop application with a local-first architecture for AI processing, the Service does collect certain analytics and operational data during normal use:
cdn.crabnebula.app). Update checks transmit the current app version, OS family, and architecture; no user-identifying data is included. Update artifacts are signed with Minisign (which uses Ed25519 internally) and verified on your device before installation.
cdn.getlonghand.com.
To be explicitly clear, we do NOT collect:
These exclusions do not cover organization-managed credentials, AI proxy requests, imported records, or content you publish or share through hosted services. Those paths process data as described in Sections 3, 4.5, and 6.
The desktop application uses PostHog for product analytics (as described in Section 4.2), which maintains a local identifier for usage tracking. The desktop application does not use traditional browser cookies. If you interact with our website or web-based account management portal, we use the following categories of cookies:
| Category | Purpose | Duration |
|---|---|---|
| Essential | Authentication, security, core functionality | Depends on the account service and session settings |
| Functional | Saved theme preference in browser storage | Until changed or browser storage is cleared |
| Analytics | PostHog usage identifiers and interaction tracking; initialized on page load | Depends on browser storage and PostHog settings |
| Marketing | Campaign attribution; the Kit waitlist form processes the name and email you submit | Depends on the provider and your subscription preferences |
You can clear site storage or block tracking through your browser settings. The website has no built-in analytics preference control. Fonts are requested from Google Fonts; embedded videos and booking links contact their respective providers when used.
Google sign-in: Sign-in requests openid, email, and profile. We receive your account identifier, email and verification status, name, and profile image when provided to create or link your account, authenticate you, and display your identity. Our account service stores profile and session records. The current account-link storage path removes Google access, refresh, and ID tokens before saving the link. Signing in does not itself grant Workspace access.
Desktop Google Workspace connection: A separate authorization requests identity permissions and the five service scopes below. Their full names start with https://www.googleapis.com/auth/. They permit access to existing content, not only files created by Longhand or selected in a file chooser. Your Google account permissions still apply.
drive): Search, read, download, and export file metadata and content for source material; create, copy, and update files for results. The grant allows broader file management than the current tools expose.spreadsheets): Read spreadsheet structure, values, and formulas; create spreadsheets and update, append, or clear data for analysis and workflow outputs.documents): Read document content and structure, and create or edit documents for requested reports and other outputs.gmail.modify): Read mailbox identity, headers, senders, recipients, subjects, bodies, labels, and drafts; create drafts, send messages, change labels, and move messages to trash for summaries and follow-ups. Current tools do not expose permanent message deletion.calendar): Read calendar and event identifiers, titles, descriptions, times, locations, attendees, and meeting links for schedules and meeting preparation; create, update, and delete events.Additional calendar-only accounts request identity and Calendar permissions without the other four service scopes. Connected tools run for your requests and configured workflows. Calendar sync and enabled scheduled or meeting-related workflows can read data in the background. Write operations follow approval controls and saved trust settings; an already-authorized tool may run without another prompt.
Web Sheet imports: The administration app separately uses drive.file and Google Picker. Your browser uses a short-lived Google access token to download or export the spreadsheet you choose, then sends workbook contents to Longhand servers for preview and, if you commit the import, storage in your organization's queue. The Picker token itself is not sent to the import API. Authorized workspace members can access imported records.
Personal Workspace tokens, expiry, scopes, and connected email are held in the encrypted local vault described in Section 3. Google content can be included in AI task context as described in Section 5.3. Section 7 explains retention, revocation, and deletion.
For users in the EEA, UK, and Switzerland, we process your personal data based on the following legal bases:
| Legal Basis | Processing Activity | GDPR Article |
|---|---|---|
| Contract Performance | Account management, service delivery, support | Art. 6(1)(b) |
| Legitimate Interest | Security, fraud prevention, service improvement | Art. 6(1)(f) |
| Consent | Marketing and optional crash reports where consent is requested | Art. 6(1)(a) |
| Legal Obligation | Tax records, regulatory compliance | Art. 6(1)(c) |
We use the information we collect to:
We do NOT use your personal data, Content, Agent configurations, Skill definitions, or workflow data to train our own machine learning models. To run your tasks, prompts, conversation history, tool results, and attachments can be sent to the selected Model Provider. This can include email text, document and spreadsheet content, calendar details, and results derived from Google data. Personal provider connections can send directly; trial and company AI can pass through Longhand servers. Local models process AI requests on your device, while Google connections and other network services still contact their providers. Provider retention and training terms depend on the account and settings; Longhand does not change those settings or promise zero retention for every provider. Google data is subject to the restrictions in Section 5.5.
The Service does not use automated decision-making technology to make significant decisions about Users (as defined under the CCPA/CPRA) without human oversight. The AI capabilities within the Service are tools that augment human decision-making; they do not autonomously make decisions that produce legal or similarly significant effects on Users.
Longhand's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google Workspace API data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models. This restriction applies to derived data and transfers to Model Providers. Use a provider connection whose terms and settings support these restrictions.
We do not sell Google user data or use it for advertising, creditworthiness, or lending eligibility. Transfers are limited to providing or improving appropriate user-facing features, your authorized actions, and the other exceptions allowed by Google's policy. Human access is limited to your affirmative permission for specific content, security investigations, legal obligations, or aggregated and anonymized internal operations as permitted by that policy. Broader provisions elsewhere in this Policy do not expand these uses of Google data.
We may share your personal information with the following categories of recipients:
We will never:
If we transfer your personal data outside of your jurisdiction, we will implement appropriate safeguards, including:
We retain your personal data only for as long as necessary to fulfill the purposes for which it was collected or as required by applicable law. No indefinite data retention is permitted under our policies. Our general retention periods are:
| Data Type | Retention Period | Basis |
|---|---|---|
| Account Data | Duration of account + 30 days | Contract |
| Crash Reports (opt-in) | 12 months | Consent |
| Support Records | 36 months from resolution | Legitimate Interest |
| Transaction Records | As required by tax law (typically 7 years) | Legal Obligation |
| Marketing Consent | Until consent is withdrawn | Consent |
| Security/Auth Logs | 12 months | Legitimate Interest |
Upon account deletion, we will delete or anonymize your personal data within thirty (30) days, except where retention is required by law. Request deletion of your account or Google-derived data at privacy@technical-leaders.com, identifying your account email and relevant organization or feature. Do not send passwords, tokens, or recovery codes. We verify requests and explain any legally retained records. Organization administrators may need to assist with shared data; backups and historical records may require separate handling.
Disconnecting Google in Longhand attempts to revoke the refresh token and clears the active token bundle. You can also remove Longhand in your Google Account connections to ensure access is revoked if the app cannot contact Google. Disconnecting does not erase earlier messages, calendar entries, imported rows, outputs, downloads, or evidence. Clearing a current record may leave historical entries in the app's event history.
The app does not apply a universal automatic expiry to Google-derived local work history. Hosted account deletion does not remotely erase local application data or exported copies. Remove saved outputs and exports you no longer need; contact us for guidance on removing an entire local profile and its history. Copies sent to Google, Model Providers, connected services, or recipients follow their own retention and deletion processes.
We implement industry-standard technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. These measures include:
In the event of a data breach affecting your personal data, we will notify affected users and relevant supervisory authorities within seventy-two (72) hours of becoming aware of the breach, in accordance with GDPR Article 33 and other applicable breach notification laws.
If you are located in the EEA, UK, or Switzerland, you have the following rights under the GDPR:
If you are a California resident, you have the following rights:
In compliance with the California Generative AI Training Data Transparency Act (AB 2013, effective January 1, 2026), we disclose that Longhand does not train or develop its own generative AI models. Longhand enables users to interact with third-party Model Providers (Anthropic, OpenAI, Google, xAI, and locally-hosted models) through personal, trial, or company connections. We do not use user data to train our own AI models. Review each provider's terms and settings; Google data remains subject to Section 5.5, including transfers to providers.
The Company complies with applicable state comprehensive privacy laws, including those in effect in Delaware, Indiana, Iowa, Kentucky, Minnesota, Nebraska, New Hampshire, New Jersey, Rhode Island, Tennessee, Colorado, Connecticut, Virginia, Utah, Montana, Oregon, Texas, and Maryland. If you are a resident of any of these states, you generally have rights to access, correct, delete, and port your personal data. Contact us to exercise these rights.
If you are located in Brazil, you have rights under the Lei Geral de Protecao de Dados (LGPD), including the right to access, correct, delete, anonymize, or port your personal data, and to be informed about the entities with which your data has been shared. International transfers of your data are governed by Brazilian Standard Contractual Clauses (effective August 23, 2025).
If you are located in Canada, you have rights under the Personal Information Protection and Electronic Documents Act (PIPEDA), including the right to access your personal information, challenge its accuracy, and withdraw consent.
If you are located in South Korea, the Basic AI Act (effective January 2026) provides additional transparency, risk assessment, and human oversight requirements for AI systems. As a platform that facilitates user interaction with AI models, we comply with applicable transparency and documentation obligations.
To exercise any of your privacy rights, please contact us at privacy@technical-leaders.com or dpo@technical-leaders.com. We will respond to all verifiable requests within the timeframes required by applicable law (generally within thirty (30) days for GDPR and forty-five (45) days for CCPA). We may request additional information to verify your identity before processing your request.
The Service is not directed to individuals under the age of 18 (or the applicable age of majority in your jurisdiction). We do not knowingly collect personal information from children. In compliance with the amended Children's Online Privacy Protection Act (COPPA, as amended April 22, 2025, compliance deadline April 22, 2026):
If we become aware that we have inadvertently collected personal data from a child, we will take steps to delete such information promptly. If you believe a child has provided us with personal information, please contact us at privacy@technical-leaders.com.
In compliance with the European Union Artificial Intelligence Act (EU AI Act), we provide the following transparency disclosures:
Longhand is an AI agent platform that enables users to build, configure, and run Agents, Skills, and workflows using third-party Model Providers (Anthropic, OpenAI, Google Gemini, xAI Grok) or local models. The desktop app is built with Tauri and supports Longhand's bundled llama-server runtime and configured compatible endpoints. Inference runs at the selected model endpoint. Trial and company AI requests can pass through Longhand's server-side proxy; account, team, and connected-service features also use the network, as described in Sections 3, 4.5, and 5.3.
As of the effective date of this Policy, the Service is classified as a general-purpose AI application tool (minimal risk) under the EU AI Act framework. The Service does not make autonomous decisions in high-risk domains (healthcare, law enforcement, critical infrastructure, etc.) without human oversight.
The Company provides documentation, training materials, and support resources to help Users understand the AI capabilities and limitations of the Service, in compliance with the AI literacy obligations under Article 4 of the EU AI Act.
In compliance with Article 50 of the EU AI Act (enforceable August 2, 2026):
The Service is designed to augment, not replace, human decision-making. Users maintain full control over whether to accept, modify, or reject AI-generated outputs. Agent outputs intended for customer-facing use should be subject to appropriate human review and quality assurance.
The website does not configure a separate Do Not Track ("DNT") handler; tracking behavior depends on browser restrictions and analytics-provider settings. Desktop analytics is separate and has session recording disabled, as described in Section 4.2. Some third-party services integrated into our website may not respond to DNT signals.
The Service may facilitate interactions with third-party services, including Model Providers. This Privacy Policy does not apply to those third-party services. We encourage you to review the privacy policies of any Model Provider or third-party service before providing them with your information. The Company is not responsible for the privacy practices of third-party services.
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. We will provide notice of material changes by posting the updated Policy on the Service and updating the "Last Updated" date. For significant changes, we will provide at least thirty (30) days' advance notice via email or in-app notification. Your continued use of the Service after the effective date constitutes acceptance of the updated Policy.
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
General Privacy Inquiries: privacy@technical-leaders.com
Data Protection Officer: dpo@technical-leaders.com
Legal Inquiries: legal@technical-leaders.com
Mailing Address: 1062 E Oaks Manor Dr., Fayetteville, AR 72703
EU Representative: Not applicable — see Section 2 for the Company's Article 27(2) exemption basis.
For GDPR-related inquiries, we will acknowledge receipt within forty-eight (48) hours and provide a substantive response within thirty (30) days. For CCPA-related requests, we will respond within forty-five (45) days as required by law.
By installing or using the Service, you acknowledge that you have read and understood this Privacy Policy.