Axles Privacy Policy
Updated November 14, 2026 · Development preview notice
Who handles your information
The operator of this Axles deployment runs the service. Your organization manages its workspace, memberships, permissions and organizational records. Their responsibilities depend on the applicable law and their agreement. Contact your workspace administrator for the operator’s identity, direct contact details, hosting locations and applicable data-processing terms. This preview is intended for evaluation with test data.
Information Axles processes
Axles stores account and profile details, password hashes for password-based accounts, session records, organization memberships and assigned roles. Features you use may store messages, attachments, documents, spreadsheets, presentations, calendar events, tasks, approvals and meeting information. People features may store employment details, attendance, leave requests, employee documents and location information submitted for attendance or geofencing. Audio and video features use the permissions you grant in your browser. Recording or transcription, when used, involves additional content and requires participants to follow applicable notice and consent rules.
Why information is used
Information is processed to authenticate users, apply permissions, save and share work, deliver messages and notifications, run requested workflows, provide integrations, investigate failures and protect the service. Operational logs can include request details, timestamps, IP addresses and error information. Administrators should enable only the features and access appropriate for their organization. This policy is a notice of processing; it is not blanket consent to unrelated monitoring or collection.
Google and email
Google sign-in shares identity information needed to link or create your Axles account. Connecting Gmail is a separate action in Settings → Integrations. It grants the permissions shown by Google, which can include reading, organizing and sending email. Axles stores the access credentials and mail data needed for those features. You can revoke Axles’s access in your Google account; revocation stops future authorized access but does not itself delete copies already stored in the workspace. System emails such as invitations and password resets use the operator’s configured sending service.
Calendar sync with Google Calendar or Microsoft Outlook is another separate consent, started from Calendar. It lets Axles read and change events in the provider calendar you choose. Axles stores encrypted provider credentials, copies of the synchronized events in your Axles calendar, and the identifiers that link them, and sends the events you organize in that calendar to the provider. Disconnecting deletes the credentials and stops synchronization; events already copied remain in both calendars until you delete them.
AI processing
When your organization enables AI, requests may include your prompt, relevant workspace content you can access and context needed for the requested task. This data is sent to the configured AI service; voice transcription and synthesis may also use an external provider. Conversation history and optional memory can be stored in Axles. Organization settings control AI and memory availability, and the interface provides memory controls. Disabling AI does not automatically delete previous conversations, memories or provider records. Ask your administrator which provider is configured and what retention and processing terms apply before submitting sensitive information.
When your organization also allows persistent memory, Axles sends documents, tasks, calendar events and messages from conversations whose owners opted in to the AI service in the background to create a semantic search index stored with your organization’s data. Search results are limited to what each person can currently access. Turning memory off removes this index. Axles records AI token usage per organization and requesting user so administrators can see usage and set limits.
Who can receive information
Information is available to authorized workspace members and administrators according to their roles, sharing settings and the features used. Public sharing links can expose the selected content to people outside the workspace. Configured infrastructure providers may process data for hosting, storage, traffic routing, email, meetings, diagnostics and AI. The current development deployment uses Cloudflare for traffic routing and Supabase for database and object storage; other services depend on operator configuration. Providers may process information in different countries. Ask the operator for its current provider list and any required transfer arrangements.
Business registration and payments
Business registration stores your company name, business email, industry, team size, selected plan and license status. Trial eligibility uses normalized company-name and email fingerprints. A browser-held registration token lets you resume signup in the same tab. Free and trial registration collect no card or billing address. For a paid subscription, Axles sends your email and selected subscription details to Stripe. Stripe collects payment information on its hosted checkout; Axles stores Stripe customer, checkout and subscription identifiers and payment status, but does not receive full card numbers. Stripe’s own privacy notice applies to its payment processing. Registration and billing records remain with the operator and may need to be retained separately from account records.
Cookies and browser storage
Axles uses cookies for authentication and browser storage for session-related interface state and preferences. Blocking these can prevent login or other features from working. The application does not include an advertising-cookie system. External services opened or embedded through integrations may use their own cookies under their own policies.
Retention and deletion
Workspace records remain until deleted through the relevant feature or managed by the operator under the organization’s retention requirements. There is no single automatic retention period for all workspace data. The account-deletion feature schedules personal-account removal after a 30-day grace period; signing in during that period cancels the request. Removal anonymizes or removes personal account details while organizational records, including shared work, may remain. Backups, audit records and external-provider copies have separate retention schedules. Ask the operator about those schedules, deletion scope and any legally required retention.
A company owner can delete the whole company workspace: its content and uploaded files are deleted and members lose access, while employer HR records, audit records and billing records are retained as required. A company administrator can erase a member’s personal data within that company only: access and private items are removed and shared work is shown as from a deleted member, while employer HR records are retained. Neither action deletes the person’s Axles account or their data in other companies.
Your choices and requests
You can update your profile, manage sessions, review available AI memory controls, revoke Google access and request account deletion through the available settings. Contact your administrator for access, correction, export, deletion, restriction or other privacy requests and to reach the operator directly. The rights available and any exceptions depend on applicable law; the operator may need to verify your identity and authority. Where applicable, you may complain to your data-protection regulator.
Security and updates
Axles applies authentication and role-based access controls, but no service can guarantee absolute security. Report suspected exposure to the operator promptly. Avoid uploading sensitive real-world records to the development preview. This notice will be updated as practices change, with the revision date shown above. See also the Terms of Service.