Privacy Policy

The short version

Arialine is a Slack app for turning ideas into living, versioned diagrams. It can create, change, or answer about a board when you address Aria, Arialine, or @Arialine; use /arialine or a shortcut; apply a proposal; react with a pushpin to propose a change; or share a supported file while automatic rendering is enabled.

In channels where Arialine is invited, recent discussion text is buffered for up to 72 hours so a later explicit mention such as '@Arialine turn this discussion into a diagram' can include the discussion that came before it. Nothing from this buffer is sent to an AI provider until someone explicitly invokes Arialine. There is no ambient listening feature or per-channel context-disable setting. We do not sell your data or use Slack content to train AI models.

Arialine uses Featurebase for the public Help Center. Support happens by email. Featurebase is a documentation processor only; it does not decide your Slack permissions, workspace plan, subscription state, or billing authority.

What Arialine accesses in Slack

When you install Arialine, Slack sends us the installing workspace or organization ID and name, the installing user's Slack ID, the app installation details, and the bot access token required to operate the app. The token is stored on our server and is never shown on the website or sent to PostHog or Featurebase.

Slack sends Arialine message events only for channels it has been invited to. Recent channel text is kept in a rolling 72-hour context buffer so a later explicit address to Aria, Arialine, or @Arialine can resolve phrases such as 'this discussion'. The buffer is separate from board history. Nothing in it is sent to an AI provider until an explicit invocation.

After an explicit request, Arialine may use Slack Real-time Search to find older public-channel messages that Slack permits the requesting user to access, including messages that were not present in Arialine's recent-context buffer. Keyword search is the baseline. Slack may provide semantic search when the workspace includes Slack AI Search. Arialine does not persist the returned search results as a separate conversation archive. Private-channel and direct-message historical search is not currently supported.

For a diagram, we store the board name, workspace and channel IDs, Mermaid source, version history, change summaries, Slack user IDs, timestamps, and links back to the source Slack messages — the record needed to show the board's history and explain why each element exists.

Support and Help Center

Arialine uses Featurebase to host detailed documentation and Help Center search. Reading the Help Center does not send your Slack profile, workspace identity, verified account email, or Paddle billing email to Featurebase.

Support is handled by email at hi@arialine.app. When you email us, we receive your message, your email address and anything you choose to include, and keep that correspondence to answer you and to handle follow-ups.

The Contact support shortcut in Slack only opens the browser support page. Support replies are sent by email and are not routed through Arialine as Slack DMs.

Website and service analytics

The website uses PostHog to collect page views, the page path, anonymous website identifiers, language changes, Add to Slack clicks, blocked-install events, successful OAuth callbacks marked installed=1, browser errors, and general interaction events captured by the analytics library.

PostHog may also receive standard technical information such as browser and operating system, screen size, URL, and the IP address used to make the request. The website uses Slack sign-in for the account page. Paddle hosts checkout and payer-facing billing services; Arialine never receives card numbers. The browser may keep an anonymous analytics ID in local storage and cookies.

The Slack service sends PostHog operational metrics such as workspace ID, feature used, trigger, response time, success or failure, AI provider and model, fallback position, token counts when a provider reports them, and error type. We do not intentionally put Slack message text or Mermaid source into these analytics events.

How we use the data

We use Slack data to respond to your request, create and update diagrams, keep version history and decision ledgers, post files and canvases back into Slack, prevent duplicate event processing, troubleshoot failures, and measure which features and AI providers are working.

Rendered diagrams are uploaded as Slack files in your workspace. Decision ledgers are standalone Slack Canvases where supported, or messages in the board thread on Slack Free; Arialine leaves existing channel Canvas tabs untouched. Arialine also stores the diagram source and history in its PostgreSQL database so the board can be updated later and shown in the Home tab.

Support data is used to answer questions, investigate bugs, handle feature and billing-support requests, and respond to privacy/data requests. Product-update contact data and preferences are used only for the communication choices associated with that contact.

AI providers

For AI-assisted features, Arialine sends the relevant instruction, conversation context, and current diagram source to a configured model provider. The fallback chain can use DeepSeek's API, OpenAI's API, and Google's Gemini API. A request normally starts with the first configured provider and can reach a later provider if an earlier attempt fails. Provider availability and exact models can change. Valid Mermaid that you paste is rendered without sending it to an AI provider.

Arialine does not use Slack data to train models, sell it, or share it with advertisers. Model providers process requests under their own service terms and data controls.

Provider documentation: OpenAI data controls, Gemini API abuse monitoring, DeepSeek privacy policy.

LLM data tenancy policy

Arialine scopes stored boards, versions, recent context, and settings to the verified Slack workspace. Operational and customer records use separate PostgreSQL databases. Model requests are sent to the selected provider's service for that request, including on fallback; Arialine does not provide a dedicated model instance or promise dedicated provider infrastructure for each customer. We send only the context needed for the invoked feature, and ordinary channel conversation is not sent to a model until Arialine is explicitly invoked.

LLM data residency policy

Arialine does not offer a customer-selected LLM processing region or guarantee that model inputs and outputs stay in a particular country. The provider that receives a request, its infrastructure, and any fallback determine where that request may be processed or retained. This applies separately from where Arialine stores its own operational records. If your organization requires a specific processing region, contact hi@arialine.app before sending that data to an AI-assisted feature.

LLM retention settings

Arialine does not maintain a separate permanent archive of model request and response transcripts. Relevant source and generated diagram content may remain in board history as described below. Provider-side retention is separate from Arialine's records and depends on the provider and API feature used. We do not promise zero data retention across the fallback chain.

OpenAI's published API controls say abuse-monitoring logs are generally retained for up to 30 days, with possible legal exceptions; its Responses API also stores application state for at least 30 days by default. Google's Gemini API documentation says it retains prompts, context, and outputs for 55 days for abuse monitoring. Other configured providers have their own terms and controls; a single retention period does not apply to all of them.

Billing and payment data

Paddle is Arialine's Merchant of Record for paid subscriptions. Paddle collects the payer's email, payment method, invoices, tax information, and other billing details. Arialine receives the Paddle customer/subscription identifiers and billing state needed to operate the Team plan, but it does not receive card numbers.

Arialine initializes Paddle.js on the public website so Paddle payment-recovery links can present their secure recovery flow. Paddle may use browser identifiers or cookies needed to connect that visit to its billing and recovery services.

The payer and the Slack workspace administrators are separate roles. Paying for Arialine does not grant Slack access. Workspace owners/admins may use Arialine's existing workspace-level subscription controls, while payer-specific financial information remains with Paddle.

What we do not collect

We do not collect Slack passwords, payment card numbers, Slack user tokens, or content from workspaces and channels that Arialine cannot access. We do not sell data, use it for advertising, or use it to train AI models.

Retention, access, transfer, and deletion

The recent-discussion context buffer expires after 72 hours, and an hourly cleanup removes expired rows. Workspace owners and admins can turn off saving pasted Mermaid (/arialine privacy save off, or the switch in App Home). Valid pasted Mermaid is then rendered once and posted to Slack without creating a board, version, decision or repair record, and Mermaid source is replaced by a placeholder in the discussion buffer. Diagrams created with AI, pasted Mermaid combined with an edit request, and existing boards are still stored so they can be edited. Real-time Search results remain request-scoped and are not written to the context buffer. Board source, versions, decisions, settings, and related metadata are kept while the app is installed so the service continues to work. Uninstalling Arialine stops new processing, but it does not automatically delete existing records yet. Operational records and analytics are kept according to the configured PostHog and service-retention settings.

Support correspondence is kept in our support mailbox, and earlier support conversations may still exist in Featurebase. A verified deletion or access request must therefore be handled across the relevant Arialine databases, product-activity records, PostHog, the support mailbox, Featurebase, and any enabled operational mirror, while Paddle may retain billing records where it is legally required to do so.

You can ask what data we have about you or your workspace, request a copy in a usable format, or request deletion by emailing hi@arialine.app. If GDPR or another privacy law applies to you, use that email for access, portability, correction, objection, or deletion. We may ask for enough information to verify the workspace and request before acting.

Contact

For privacy, GDPR, and data requests, email hi@arialine.app. For product and billing support, email the same address or use the Contact support shortcut in Slack.