# Alfera — full content export

> Your next hire is an AI coworker

Alfera is an AI employee for teams of every size, from startups to enterprise. It connects to the tools you already use, takes a plain-English request, and finishes the whole job — customer replies, follow-ups, scheduling, invoices, and reports.

# Home — https://www.alfera.ai/

## Hand off the busywork. Get back finished work.
Alfera plugs into your email, calendar, spreadsheets, and apps, takes a plain-English request, and does the whole job end to end — then hands you the finished result to approve.

## See what Alfera looks like in production.
Not a demo prompt — the real thing. Ask in one line; Alfera works across your tools and hands back a finished result you can act on.

## Welcome agents into your workplace.
Talk to Alfera right where you already work — Slack, email, WhatsApp, or Teams. Tag it, ask in plain English, and the job gets done. One coworker, not a team of bots to manage.

## Owners get their week back.

- 10+ hrs: of busywork off your plate each week
- 3,500+: tools and apps it can connect to
- 24/7: working, even while you sleep
- < 5 min: to connect your first tool and start

# Product — https://www.alfera.ai/product

Alfera is built for a non-technical owner: describe the result, connect the tools, approve anything sensitive, and inspect exactly what happened.

## Ask for outcomes
Start from the business result, not a node canvas or a prompt library.

- "Follow up on these leads"
- "Prepare this week’s report"
- "Clean up this customer list"

## Work across tools
It pulls context from your apps, files, and the browser before producing the output.

- Email and calendar
- CRM and spreadsheets
- Browser and file workflows

## Review every run
See what it read, drafted, changed, skipped, and what still needs your approval.

- Readable summaries
- Source-aware output
- Action-by-action record

# Integrations — https://www.alfera.ai/integrations

Alfera plugs into the accounts and tools your team already depends on. Search the catalog below — thousands of apps, plus controlled browser access when an app has no API.

## Office layer
Email, calendar, docs, and spreadsheets — where the day actually happens.

- Gmail and Outlook
- Google Calendar
- Sheets and Excel

## Revenue layer
Follow the customer trail across CRM, payments, scheduling, and your store.

- HubSpot and Salesforce
- Stripe and Square
- Shopify and Calendly

## Browser layer
When a vendor has no API, Alfera still helps through controlled browser work.

- Portal updates
- Vendor research
- Form preparation

# Security — https://www.alfera.ai/security

Alfera connects to your tools to get work done, then gets out of the way. We never share your data with third parties, never train AI models on it, and encrypt it at every step. You stay in control.

## Never shared, never sold
Your data is never shared with third parties and never used to train AI models. It is used only to do the work you ask for.

- No third-party sharing
- No training on your data
- Used only for your tasks

## Encrypted at rest and in transit
Everything we store is encrypted, and every connection is encrypted on the way. Your logins are stored securely and you can disconnect any tool anytime.

- Encrypted at rest
- Encrypted in transit
- Disconnect any tool anytime

## You approve anything sensitive
Alfera asks before it sends to a customer or changes important data. Nothing risky happens without your one-tap go-ahead.

- Review before send
- Approve sensitive changes
- Owner-controlled access

## A clear record of everything
Every run leaves a plain-English log of what Alfera read, changed, and sent — so you can always check the work.

- Plain-English run logs
- Every action recorded
- Easy to review and reverse

# About — https://www.alfera.ai/about

We build for the everyday operations of any business: customers, leads, invoices, scheduling, records, and reports.

## Practical by default
Every surface points at a real task and a real output. Less abstraction, more done.

- Real outputs
- Concrete examples
- Clear accountability

## Built for operators
The average owner should understand what Alfera does in under a minute.

- Plain language
- No AI jargon
- Fast to value

## Control is the product
Approvals, logs, and source context are the value, not compliance decoration.

- Human in the loop
- Inspectable runs
- Reversible work

# Contact & demo — https://www.alfera.ai/contact

The fastest way to evaluate an AI coworker is concrete: a real task, real tools, your approval rules, and a finished output you can inspect.

## A good demo task
Pick one job that happens every week and already has a clear definition of done.

- Chase old quotes
- Summarize the inbox
- Prepare a report

## What to bring
The tools involved, the source data, and the step that should need approval.

- Source apps
- Desired output
- Sensitive steps

## What you get
A straight read on whether Alfera saves you real time in your real operation.

- Workflow assessment
- Setup plan
- Next task list

# Pricing — https://www.alfera.ai/pricing

Try it on one workflow, expand when it saves you time, and keep control of spend. No annual contract required.

Start free, no credit card required.

## Pro — from $50 / month
Shared workspace credits: 5,000–3,000,000 credits monthly ($50–$30,000 / month).

## Enterprise — Custom
Tailored to your scale

Everything in Pro, plus:
- Custom data regions and residency
- Self-hosted and on-prem deployment
- Computer Use with custom configuration
- Security review, DPA, and SAML SSO
- SCIM provisioning and audit logs
- Annual invoicing and custom terms
- 99.9% uptime SLA and priority support
- Dedicated onboarding and a solutions engineer

## What your credits get you
Alfera runs on credits. You spend them only when a task runs, and bigger jobs use more. Here is what typical work costs.

One dollar is 100 credits, so the $50 plan is 5,000 credits a month.

### Simple task: 10–30 credits
Reply to a customer email. Read the thread, check the order, and draft a reply for you to approve. (Hundreds per month on the $50 plan.)

### Multi-step workflow: 200–600 credits
Triage a batch of inbound leads. Research each lead, enrich it, add it to your CRM, and draft a personalized first reply. (Roughly 8 to 25 per month on the $50 plan.)

### Long-running job: 5,000+ credits
Run outreach to 500 prospects. Research every prospect, write a tailored email, and follow up over days, all in one run. (A full month on the $50 plan, or scale up for more.)

**What is a credit?**
Credits are how you pay for the work Alfera does. One dollar is 100 credits, so the $50 plan gives you 5,000 credits a month. You spend them only when a task runs, never for seats, integrations, or sitting idle.

**What do credits pay for?**
The real work in a run: reading and searching your connected tools, reasoning through the task, drafting, and taking the actions you approve. A task that reads one email and replies costs a little; a job that researches hundreds of leads costs more.

**How many credits does a task use?**
It scales with the work. A simple task is around 10 to 30 credits, a multi-step workflow around 200 to 600, and a long autonomous job can run into the thousands. The examples above show typical ranges.

**How do I keep control of spend?**
You choose your monthly credit package and can change it anytime. Every run has approval gates and a readable audit trail, and a live usage view shows exactly where your credits go.

**What happens if I run out of credits?**
Runs pause with a clear message and nothing is charged beyond your balance. Add credits or move up a package to pick up where you left off.

**Can I change how many credits I get?**
Yes. Pro scales from 5,000 credits a month up to 3,000,000, all self-serve. Beyond that, Enterprise adds custom volume and terms.

**Is there a free way to try it?**
Every new workspace starts with free credits and no credit card, so you can run real tasks before you pay.

# Customer support AI employee — https://www.alfera.ai/use-cases/customer-support

Your inbox stops running your mornings. Alfera triages, answers the routine questions, and surfaces only what needs you.

## Triage and answer
Sort the inbox, draft and send routine answers, and tag what is urgent.

- Inbox triage
- Reply drafts
- Urgent flags

## Confirm and schedule
Confirm appointments, reschedule, and keep the calendar clean.

- Appointment confirms
- Reschedules
- Reminders

## Summarize and escalate
Hand you a clean summary of issues and escalate the exceptions.

- Issue summaries
- Escalation rules
- Daily recap

# Sales follow-up AI employee — https://www.alfera.ai/use-cases/sales-follow-up

The money is in the follow-up you never get to. Alfera chases every lead and books the ones who are ready.

## Chase every lead
Find stale quotes and unreplied threads and write the right next step.

- Quote follow-up
- Re-engagement
- Next-step drafts

## Keep the CRM honest
Update records, log activity, and enrich contacts so the pipeline is real.

- CRM updates
- Activity logging
- Contact enrichment

## Book the meeting
Propose times, confirm calls, and prep you for the conversation.

- Meeting booking
- Confirmations
- Call prep

# Operations & admin AI employee — https://www.alfera.ai/use-cases/operations-admin

The unglamorous work that keeps the business running, handled — so you can run the business.

## Keep the data clean
Update spreadsheets, dedupe records, and reconcile lists across tools.

- Spreadsheet updates
- Record cleanup
- List reconciliation

## Prepare the report
Pull the numbers and build the owner summary you actually read.

- Weekly reports
- Owner summaries
- KPI roundups

## Close the loops
Chase missing inputs, nudge owners, and sync data on a schedule.

- Follow-up nudges
- Scheduled syncs
- Status tracking

# Bookkeeping & invoice AI employee — https://www.alfera.ai/use-cases/bookkeeping

Get paid faster without the awkward chasing. Alfera watches the receivables and follows up for you.

## Chase what is owed
Spot overdue invoices and send polite, on-brand reminders from live status.

- Overdue detection
- Payment reminders
- Escalation steps

## Reconcile and report
Match payments, flag mismatches, and summarize outstanding balances.

- Payment matching
- Mismatch flags
- Balance summaries

## Tee up the books
Organize receipts and documents so month-end is a review, not a scramble.

- Receipt capture
- Document sorting
- Month-end prep

# Scheduling AI employee — https://www.alfera.ai/use-cases/scheduling

Fewer no-shows, fewer phone-tag loops. Alfera runs the calendar so your day runs on time.

## Confirm and remind
Send confirmations and reminders that cut no-shows automatically.

- Confirmations
- Reminders
- No-show recovery

## Reschedule cleanly
Offer new times, update everyone, and avoid the back-and-forth.

- Reschedules
- Availability
- Conflict checks

## Keep the team in sync
Balance the schedule across people and keep the day organized.

- Team calendars
- Daily plan
- Handoffs

# Ecommerce support AI employee — https://www.alfera.ai/use-cases/ecommerce-support

Keep buyers happy without living in the support queue. Alfera answers, flags, and reports.

## Answer order questions
Look up orders, answer "where is it", and handle the routine asks.

- Order lookup
- Status replies
- Routine support

## Handle refunds and exceptions
Flag refund requests, prep the details, and escalate the edge cases.

- Refund prep
- Exception flags
- Policy checks

## Report the themes
Summarize what buyers are asking so you can fix the root cause.

- Support themes
- Trend alerts
- Weekly recap

# What if your business ran itself? — https://www.alfera.ai/blog/what-if-your-business-ran-itself
_2026-06-22 · 6 min read_

We are shipping the on-ramp to a business that handles its own busywork, and reports back when it is done.

Your business produces an enormous amount of [signals](/product) every day — a quote goes unanswered, an invoice ages past due, a customer asks the same question for the tenth time. Today you find out about most of them late, if at all.

**The busywork loop today:** something needs doing, and you notice it later — when you open your inbox, scan your CRM, or a customer chases *you*. If it is not urgent it becomes a sticky note. Hours or days later, you finally sit down, do the task, and update the record.

We think that is far too slow.

**What we want instead:** a signal fires from your tools, and rather than waiting for you to spot it, an [AI coworker](/product) goes and works it out. Once it has, it hands you a finished result to approve. So instead of ever opening your inbox, your CRM, or your books, you wake up to work sitting ready for a quick yes.

We're shipping the on-ramp to that reality.

![The Alfera inbox of finished work](/blog/figures/finished-work-inbox.svg "Finally, an inbox you look forward to opening.")

## How the operating loop works

We ingest a lot of signals, group them into actual jobs, run an agent over each one, decide whether it is worth doing, do the work if it is, and keep going until the job is genuinely done — then report back.

I'll walk through each step, and flag the things that turned out to be hard along the way.

### 1. Ingesting signals

Alfera connects to the tools you already use and watches for the moments that matter: a new lead, an unreplied thread, an overdue invoice. Each becomes a small, structured signal:

```ts
type Signal = {
  source: 'inbox' | 'crm' | 'accounting';
  kind: 'lead.new' | 'thread.unreplied' | 'invoice.overdue';
  subjectId: string;
  observedAt: string;
};
```

### 2. Deciding what is worth doing

Not every signal deserves action. A reply that already went out, an invoice that just cleared — those get dropped. What is left is a short list of jobs that are real, [forgiving enough to act on](/blog/what-to-automate-first-small-business), and clearly defined.

### 3. Finishing the job, then reporting back

For each job the coworker drafts the work, runs the safe internal steps on its own, and pauses for your approval on anything customer-facing. When the job is done it files the record and writes you a one-line summary.

> The goal is not a smarter dashboard. It is finished work you can trust — and a morning you actually look forward to.

That is the loop. Your job shifts from doing the busywork to reading a short summary and approving the few things that need your judgment.

# How to build a lead follow-up system that runs itself — https://www.alfera.ai/blog/follow-up-system-that-runs-itself
_2026-05-28 · 7 min read_

The money is in the follow-up you never get to. Here is how to make it automatic.

Most small businesses lose more revenue to missed follow-up than to lost deals. The quote went out, the customer got busy, and nobody circled back. A follow-up system fixes that, and it does not need to be complicated to work.

## Define the trigger and the cadence

Decide what starts a follow-up and how often it repeats. A common pattern: if a quote has no reply after two business days, send a friendly check-in; after five, send a final nudge with a clear next step. Write it down in one sentence so anyone, human or AI, can run it.

## Connect the source of truth

Your follow-up is only as good as your data. Point the system at where quotes actually live, your inbox and your CRM, so it knows who got a quote, who replied, and who went quiet. An AI coworker can read both and keep them in sync.

## Let it run, review the summary

- It finds quotes with no reply and drafts the right message for each.
- You approve the batch, or let trusted, internal steps run automatically.
- It books the calls, updates the CRM, and reports who is ready to buy.

Once it is running, your job changes from doing the follow-up to reading a short summary and approving the few that need your judgment. That is a system that runs itself.

# AI employee vs. ChatGPT: what is the difference? — https://www.alfera.ai/blog/ai-employee-vs-chatgpt
_2026-05-20 · 5 min read_

A chatbot answers. An AI employee does the work and reports back.

General chatbots are great at one thing: producing text when you ask for it. That is genuinely useful. But for a business owner, it stops one step short. You still have to take the draft, open the right tool, do the action, and update the record. The chatbot gave you a starting point; you finished the job.

## The gap is "the last mile of work"

An AI employee is built to close that gap. Instead of returning advice, it connects to your tools, reads the real data, takes the action, and hands you the finished output. The difference shows up in the verbs:

- A chatbot drafts a reply. An AI employee sends it and files the thread.
- A chatbot explains how to chase invoices. An AI employee chases them and reconciles what came in.
- A chatbot gives you a report template. An AI employee pulls the numbers and sends the report.

## Why control matters more, not less

Because an AI employee acts, the guardrails matter. Approvals before anything sensitive, a plain-English summary of every run, and a full audit trail are what make acting safe. The goal is finished work you can trust, not work you have to redo.

# What to automate first in a small business — https://www.alfera.ai/blog/what-to-automate-first-small-business
_2026-05-12 · 6 min read_

You do not automate everything on day one. You start with the job that is slipping right now.

Most owners stall on automation because they try to picture the whole business running itself. That is the wrong starting point. The right one is much smaller: pick a single job that happens every week, already has a clear definition of done, and is easy to check. Get that one finished by an [AI coworker](/product), then add the next.

## Start with high-frequency, low-risk work

The best first task is repetitive, valuable, and forgiving. If a mistake is easy to catch and easy to reverse, you can build trust quickly. These three usually qualify:

- **Lead follow-up:** chasing quotes and unreplied threads is pure recovered revenue.
- **Inbox triage:** sorting and drafting routine replies frees your mornings.
- **Invoice reminders:** polite, on-time nudges get you paid faster without the awkward calls.

## Keep yourself in the loop, on purpose

Delegation does not mean blind trust. Turn on approvals for anything customer-facing, read the summary after each run, and let the easy, internal work run on its own. As your confidence grows, you move more tasks from "approve first" to "just do it."

## Measure the payoff in hours

After two weeks, ask one question: how many hours did this take off my plate, and what did I do with them instead? If the answer is real, expand. If it is not, pick a different first job. The point is operating capacity you can feel, not a dashboard.

# Privacy Policy — https://www.alfera.ai/privacy

> **At a glance**
>
> - Alfera is built for business workspaces. Your organization controls the workspace data submitted to Alfera.
> - We process Slack, connected-app, file, browser, sandbox, billing, analytics, and AI-agent data only to provide, secure, support, bill, and improve the service.
> - We do not sell Customer Data for money, and we do not use Slack Customer Data or Customer Data to train foundation models.
> - You can revoke integrations at the source. Revocation stops new collection, but stored workspace data must be deleted through an authorized deletion request.

## Contents

- [1. Who this policy covers](#1-who-this-policy-covers)
- [2. Key definitions](#2-key-definitions)
- [3. Data we collect](#3-data-we-collect)
- [4. How we use data](#4-how-we-use-data)
- [5. AI processing and model providers](#5-ai-processing-and-model-providers)
- [6. Sharing and subprocessors](#6-sharing-and-subprocessors)
- [7. Security, storage, and transfer](#7-security-storage-and-transfer)
- [8. Retention and deletion](#8-retention-and-deletion)
- [9. Rights and choices](#9-rights-and-choices)
- [10. Cookies and attribution](#10-cookies-and-attribution)
- [11. Slack-specific commitments](#11-slack-specific-commitments)
- [12. Changes and contact](#12-changes-and-contact)

## 1. Who this policy covers

This Privacy Policy explains how Alfera Inc. ("Alfera", "we", "us", or "our") collects, uses, shares, and protects information when you visit `alfera.ai`, use `app.alfera.ai`, install the Alfera Slack app, connect business tools, run AI agents, use scheduled tasks, book a demo, or contact us.

Alfera is designed for organizations. If you use Alfera through a company, team, Slack workspace, or other organization, that organization controls the workspace and the Customer Data submitted to it. Workspace administrators may manage members, connected apps, Slack access, billing, retention requests, and deletion requests for workspace-level data.

## 2. Key definitions

| Term | Meaning |
| --- | --- |
| **Customer Data** | Data submitted to, generated in, or processed by Alfera on behalf of a customer workspace. This includes prompts, Slack content, connected-app data, uploaded files, generated artifacts, agent outputs, tool inputs and outputs, workspace memory, approvals, scheduled tasks, credentials, billing records, and service logs. |
| **Personal Data** | Information that identifies or can reasonably be linked to an individual, such as name, email address, account identifiers, workspace membership, IP address, support communications, usage records, or content that contains personal information. |
| **Workspace administrator** | A user authorized by the customer organization to manage workspace settings, members, billing, integrations, retention requests, or deletion requests. |
| **Connected app** | A third-party account, API, MCP server, custom HTTP endpoint, or automation provider that you authorize Alfera to use. |

## 3. Data we collect

| Category | Examples | Why we collect it |
| --- | --- | --- |
| **Account, workspace, and authentication data** | Name, email, avatar, user id, workspace id, workspace name, workspace role, organization membership, authentication provider identifiers, session state, and security metadata. | To authenticate users, provision workspaces, manage teams, enforce permissions, and secure accounts. Alfera uses WorkOS AuthKit and WorkOS widgets for sign-in, profile, organization, and team-management features. |
| **Slack data** | Slack workspace ids, installer/admin metadata, Slack user ids, names, email addresses if provided by Slack, channel ids, channel membership metadata, direct-message ids, events, thread ids, messages, files, and file metadata. | To operate the Alfera Slack app in conversations where Alfera is invited, mentioned, messaged, or configured to operate. |
| **Conversations, files, artifacts, and memory** | Chat sessions, prompts, model-visible context, assistant responses, run messages, tool calls, tool outputs, uploaded files, generated documents, spreadsheets, presentations, PDFs, screenshots, context summaries, inspector records, workspace facts, embeddings where configured, and keyword indexes. | To provide continuity, complete agent work, resume runs, debug failures, and make workspace-shared memory available to authorized users. |
| **Connected-app credentials and tool data** | OAuth setup state, access tokens, refresh tokens, expiration times, scopes, external account ids, account names, provider metadata, connection health, and tool execution records. | To set up, run, monitor, revoke, and debug connected tools. Stored credentials use an AES-256-GCM encrypted credential envelope when the production credential encryption key is configured. |
| **Runtime, sandbox, and browser data** | Sandbox ids, runtime environment ids, workspace mount keys, preview metadata, command inputs and outputs, logs, files, screenshots, downloads, browser outputs, generated artifacts, and temporary workspace state. | To run code, browser tasks, file operations, previews, and other agent work in local, Docker, or E2B remote sandbox environments. |
| **Billing and payment data** | Plan, subscription status, credit balance, credit grants, usage records, Stripe customer id, Stripe subscription id, checkout and portal metadata, invoices, payment-intent metadata, and tax or transaction metadata returned by Stripe. | To process subscriptions, credits, invoices, tax, usage, checkout, portal sessions, and billing support. Stripe handles full payment card numbers. |
| **Website, analytics, attribution, and demo data** | Pages viewed, product interactions, browser/device metadata, referrer, IP-derived metadata, error reports, analytics events, demo form fields, and attribution identifiers such as `gclid`, `gbraid`, `wbraid`, and `fbclid`. | To operate the site, improve the product, debug errors, measure advertising, and follow up on demo or purchase interest. |
| **Communications with us** | Name, email, company, role, message content, meeting information, diagnostic details, attachments, and security reports. | To respond to support, security, sales, privacy, and billing requests. |

### Slack events we process

When the Alfera Slack app is installed, we may process app mentions, direct messages, public-channel messages where the bot is present, private-channel messages where the bot is invited, multi-party direct messages, app uninstall events, and token revocation events. Alfera verifies Slack event signatures when a Slack signing secret is configured and uses Slack OAuth scopes only to provide the Slack features you authorize.

### Sensitive data and children

Alfera is not intended for children under 18 or the age of majority in their jurisdiction, and we do not knowingly collect child data. Alfera is also not designed for regulated sensitive-data workloads such as protected health information, payment-card storage, government classified information, or other high-risk regulated data unless we have a separate written agreement covering that use.

## 4. How we use data

| Purpose | What that means in Alfera |
| --- | --- |
| **Provide the service** | Run AI agents, stream responses, execute tools, generate artifacts, build model context, maintain workspace memory, and resume or debug runs. |
| **Manage access** | Authenticate users, provision workspaces, manage teams, enforce workspace roles, and operate Slack and connected-app authorization. |
| **Run workflows** | Create, update, pause, delete, and execute scheduled tasks and trigger-based workflows. |
| **Bill customers** | Process subscriptions, credits, invoices, checkout sessions, customer portal sessions, payment webhooks, tax metadata, and usage records. |
| **Communicate** | Send service, security, billing, onboarding, and support communications through email or Slack where appropriate. |
| **Improve and secure Alfera** | Measure website and product usage, debug errors, monitor reliability, prevent fraud and abuse, improve product quality, and understand advertising attribution. |
| **Comply and enforce** | Comply with law, enforce our Terms, protect rights and safety, and respond to valid legal process. |

## 5. AI processing and model providers

Alfera uses AI systems to generate responses, analyze context, run tools, draft documents, create summaries, classify information, search memory, and perform requested work. Relevant portions of Customer Data may be sent to AI providers only as needed to provide the requested service.

| AI data type | Examples |
| --- | --- |
| **Inputs** | Prompts, conversation history, files, images, tool schemas, workspace memory, and connected-app context. |
| **Outputs** | Assistant responses, summaries, classifications, tool-call arguments, generated artifacts, and draft content. |
| **Operational metadata** | Model name, provider route, usage metadata, request metadata, errors, and safety or abuse-monitoring metadata where applicable. |

Current model routes may include Anthropic, OpenAI, and Vercel AI Gateway depending on the configured environment, selected model, and availability. OpenAI-compatible APIs may also be used for embeddings and memory extraction where configured.

We do not use Customer Data to train our own foundation models. We do not knowingly opt Customer Data into third-party foundation model training. AI providers may temporarily retain API inputs and outputs according to their own API, enterprise, security, abuse-monitoring, and zero-retention terms. If you require stricter AI data-retention terms, contact us before submitting sensitive production data.

## 6. Sharing and subprocessors

We do not sell Customer Data for money. We share information only as needed to provide, secure, support, bill, analyze, and improve Alfera, or as legally required.

Some analytics, advertising attribution, and conversion-measurement activities may be considered a sale, sharing, or targeted advertising under certain U.S. state privacy laws. You may contact us to exercise any applicable opt-out rights.

| Provider or category | Purpose | Data involved |
| --- | --- | --- |
| **Vercel** | Hosting, previews, and serverless infrastructure for the marketing site and app. | Website, app, deployment, and operational data. |
| **Google Cloud Platform** | Cloud Run API hosting, Artifact Registry, Cloud Scheduler where configured, Secret Manager, logs, and related infrastructure. | API, logs, secrets, scheduling, and infrastructure data. |
| **Managed PostgreSQL hosting** | Database storage depending on the configured `DATABASE_URL`. | Users, workspaces, sessions, runs, messages, events, connections, billing state, memory, and artifacts. |
| **WorkOS** | Authentication, organization management, profile widgets, team widgets, and sessions. | Identity, account, workspace, and session data. |
| **Slack** | OAuth, messaging, event delivery, workspace communication, file upload/read features, and app installation management. | Slack workspace, user, channel, event, message, and file data. |
| **Pipedream** | Hosted connection setup, app catalog, proxy execution, and connected-app tool execution where configured. | Connected-app setup, credentials, scopes, provider metadata, and tool data. |
| **Zapier** | Offline ad conversion delivery to Google Ads and Meta, and optional automation or connected-app actions where configured. | Attribution, conversion, automation, and connected-app data. |
| **Stripe** | Checkout, subscriptions, invoices, customer portal, payment processing, payment webhooks, and billing metadata. | Billing, payment metadata, subscription, invoice, tax, and customer records. |
| **PostHog** | Product and website analytics where configured. | Usage events, user identification after sign-in, browser/device metadata, and analytics properties. |
| **Sentry** | Error monitoring, performance traces where enabled, release diagnostics, and operational logs with default PII disabled. | Error, diagnostic, and operational telemetry. |
| **Resend** | Transactional and lifecycle email delivery where configured. | Email address, message metadata, and email content. |
| **E2B** | Remote sandbox compute, file operations, previews, browser tasks, and command execution. | Runtime files, commands, logs, screenshots, previews, and sandbox metadata. |
| **OpenAI** | Model inference, embeddings, memory extraction, or OpenAI-compatible API calls where configured. | Prompts, outputs, files, images, context, embeddings, and usage metadata. |
| **Anthropic** | Model inference for agent runs or related AI features where configured. | Prompts, outputs, files, images, context, and usage metadata. |
| **Vercel AI Gateway** | Model routing and API gateway services where configured. | AI request, response, routing, and usage metadata. |
| **AWS** | EventBridge Scheduler, relay Lambda, and related scheduling infrastructure where enabled. | Scheduled-task and infrastructure metadata. |
| **Cal.com** | Demo booking embed and meeting scheduling on the marketing site. | Booking, contact, company, and meeting metadata. |
| **Google Ads and Meta** | Advertising attribution and offline conversion reporting where configured. | Ad click ids, landing URL, landing time, checkout/demo conversion metadata, and related attribution data. |
| **Customer-authorized connected apps** | Any third-party app, API, MCP server, or custom HTTP endpoint that you connect or ask Alfera to use. | Data and actions authorized by your scopes, account settings, and instructions. |

We may also disclose information when required by law, legal process, security investigation, fraud prevention, enforcement of our Terms, protection of rights and safety, or as part of a merger, acquisition, financing, corporate reorganization, bankruptcy, or sale of assets, subject to appropriate confidentiality protections.

## 7. Security, storage, and transfer

We use administrative, technical, and organizational safeguards appropriate to the nature of the service.

| Safeguard | Current approach |
| --- | --- |
| **Transport security** | TLS in transit. |
| **Storage security** | Cloud-provider encryption at rest where supported. |
| **Credentials** | AES-256-GCM encrypted credential envelopes when the production credential encryption key is configured. |
| **Access control** | Least-privilege access controls, authentication controls, and workspace permissions. |
| **Webhooks** | Signature verification where supported and configured. |
| **Observability** | Audit logs, run events, service logs, and monitoring for reliability and abuse prevention. |

No system is perfectly secure. You are responsible for managing access inside your Slack workspace, source systems, and connected third-party accounts.

Production infrastructure is primarily hosted in the United States unless otherwise stated in a separate agreement. Customer Data may be processed in the United States and other regions where our subprocessors operate.

## 8. Retention and deletion

| Data category | Typical retention approach |
| --- | --- |
| **Workspace content and agent records** | Retained while needed to provide Alfera, maintain workspace continuity, debug runs, satisfy contractual obligations, and support customer requests. |
| **Connected-app credentials** | Retained while the connection remains active or as needed to revoke, audit, or resolve issues. |
| **Billing records** | Retained as required for tax, accounting, payment, dispute, fraud prevention, and legal obligations. |
| **Logs and diagnostics** | Retained for reliability, security, fraud prevention, debugging, and operational needs. |
| **Backups** | May persist until backups expire in the ordinary course. |

If a workspace is closed or we receive a validated deletion request from an authorized administrator, we will delete or de-identify relevant Customer Data from active production systems within a commercially reasonable period, unless retention is required by law, security, fraud prevention, billing, dispute resolution, or legitimate business needs.

Revoking a connected app, uninstalling Slack, or disconnecting an integration stops new collection from that source but does not by itself delete previously stored Customer Data. You may contact us to request deletion.

## 9. Rights and choices

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data, and to opt out of certain processing such as sale, sharing, targeted advertising, or certain profiling.

To exercise rights, contact [hello@alfera.ai](mailto:hello@alfera.ai). We may need to verify your identity and authority, especially for workspace-level data controlled by an organization.

If you are in the EEA, UK, or another jurisdiction with similar rules, our legal bases may include performance of a contract, legitimate interests, consent, and compliance with legal obligations. Where required for international transfers, we use appropriate safeguards such as Standard Contractual Clauses or applicable data-transfer mechanisms.

## 10. Cookies and attribution

We use cookies and similar technologies for sign-in, session security, app routing, product analytics, error diagnostics, and advertising attribution.

| Cookie or technology | Purpose |
| --- | --- |
| **WorkOS session cookies** | Authentication and session security. |
| **`alfera_authed` hint cookie** | Lets the marketing site show app navigation when a user has signed in. |
| **PostHog analytics where configured** | Product and website analytics. |
| **Sentry diagnostics where configured** | Error diagnostics and operational monitoring. |
| **`alfera_attribution` first-party cookie** | Stores ad click identifiers such as `gclid`, `gbraid`, `wbraid`, `fbclid`, the landing URL, and landing time for up to 90 days. |

If you book a demo or purchase through Stripe, attribution data may be passed through our API and Stripe metadata so we can report offline conversions to Google Ads and Meta through Zapier where configured.

You can control cookies through your browser settings. Some cookies are necessary for authentication, security, routing, or billing flows and disabling them may break parts of Alfera.

## 11. Slack-specific commitments

- We use Slack data only to provide, secure, and support Alfera.
- We do not sell Slack data.
- We do not use Slack message content for advertising.
- We do not use Slack APIs to develop, improve, or train generalized AI or ML models.
- We do not train our own or third-party foundation models on Slack Customer Data.

## 12. Changes and contact

We may update this Privacy Policy from time to time. If we make material changes, we will notify customers through reasonable means, such as posting the updated policy, emailing administrators, or notifying users in the app. The "Last updated" date above shows when this policy was last revised.

For privacy requests, support, or questions, contact [hello@alfera.ai](mailto:hello@alfera.ai). For security reports, contact [security@alfera.ai](mailto:security@alfera.ai).

# Terms and Conditions — https://www.alfera.ai/terms

> **At a glance**
>
> - Alfera is an AI coworker that can read business context, use connected tools, generate files, post to Slack, run browser/code tasks, and execute scheduled workflows.
> - You are responsible for your workspace, connected accounts, Slack permissions, approvals, and any actions you authorize or pre-authorize.
> - Do not connect accounts or submit data unless you have the right to do so.
> - AI outputs can be wrong. Review important outputs and use qualified professionals for legal, financial, medical, tax, employment, compliance, or safety decisions.

## Contents

- [1. Acceptance and authority](#1-acceptance-and-authority)
- [2. The service](#2-the-service)
- [3. Accounts, workspaces, and administrators](#3-accounts-workspaces-and-administrators)
- [4. Slack and connected apps](#4-slack-and-connected-apps)
- [5. AI agents, autonomy, and approvals](#5-ai-agents-autonomy-and-approvals)
- [6. Customer Data and privacy](#6-customer-data-and-privacy)
- [7. Acceptable use](#7-acceptable-use)
- [8. Billing, credits, and cancellation](#8-billing-credits-and-cancellation)
- [9. Third-party services](#9-third-party-services)
- [10. Intellectual property](#10-intellectual-property)
- [11. Confidentiality](#11-confidentiality)
- [12. Disclaimers and liability](#12-disclaimers-and-liability)
- [13. Indemnification](#13-indemnification)
- [14. Suspension and termination](#14-suspension-and-termination)
- [15. Changes](#15-changes)
- [16. Governing law and disputes](#16-governing-law-and-disputes)
- [17. Miscellaneous and contact](#17-miscellaneous-and-contact)

## 1. Acceptance and authority

These Terms and Conditions ("Terms") govern your access to and use of Alfera, including `alfera.ai`, `app.alfera.ai`, the Alfera Slack app, AI agents, connected-app integrations, scheduled tasks, sandbox and browser features, billing, support, and related services (the "Service"). The Service is provided by Alfera Inc. ("Alfera", "we", "us", or "our").

By creating an account, installing the Slack app, connecting an integration, subscribing, or otherwise using the Service, you agree to these Terms.

If you use the Service for an organization, you represent that you are authorized to bind that organization to these Terms. You must be at least 18 years old, or the age of majority in your jurisdiction if higher.

## 2. The service

Alfera is an AI coworker for business work. It can answer questions, draft and edit content, search and summarize information, generate files, use browser and coding environments, create artifacts, run scheduled tasks, post to Slack, and use connected apps and APIs at your direction or according to workspace configuration.

| Surface | What it may include |
| --- | --- |
| **Marketing site** | Public pages, demo booking, contact forms, analytics, and attribution. |
| **Authenticated app** | Workspace dashboard, sessions, agents, files, artifacts, memory, settings, and billing surfaces. |
| **API** | Hono API routes that power product operations, billing, events, integrations, and runtime work. |
| **Slack app** | Channel and direct-message experiences, app mentions, slash commands, events, message posting, file handling, and installation management. |
| **Connected apps** | Native tools, Pipedream or Zapier-powered connections, MCP tools, custom HTTP tools, and app-catalog integrations. |
| **Runtime environments** | E2B, Docker, local, browser, or sandboxed environments for code, file, preview, and web tasks. |
| **AI providers** | Model providers and routing layers used to perform AI work, including Anthropic, OpenAI, and Vercel AI Gateway where configured. |

## 3. Accounts, workspaces, and administrators

You are responsible for maintaining the confidentiality and security of your account, organization workspace, Slack workspace, and connected third-party accounts.

| Role or actor | Responsibility |
| --- | --- |
| **Organization administrators** | Invite and remove users, manage roles, connect or revoke integrations, manage Slack access, configure scheduled tasks, manage billing, and request deletion or export of workspace-level data. |
| **Workspace users** | Use Alfera according to workspace permissions, these Terms, source-system rules, and any internal policies set by the organization. |
| **Slack users** | Interact with Alfera only in channels, threads, direct messages, or contexts where the workspace has enabled or invited Alfera. |
| **AI agents** | Act under user instructions, approvals, pre-authorized workflow settings, and available tool permissions. |

You are responsible for all activity in your workspace, including activity by users you invite, Slack users who interact with Alfera where it is enabled, and AI agents acting under instructions, approvals, or pre-authorized workflow settings.

## 4. Slack and connected apps

If you install the Alfera Slack app, you authorize Alfera to use the Slack scopes granted during installation.

| Permission area | Examples |
| --- | --- |
| **Slack reading** | Channels where the bot is present, direct messages to the bot, user and email metadata where available, files where authorized, app mentions, slash commands, and Slack events. |
| **Slack writing** | Sending messages, replying in threads, joining public channels where authorized, and uploading files. |
| **Connected apps** | Accessing and using third-party accounts according to the scopes, credentials, settings, and account permissions you grant. |
| **Workspace-shared connections** | Authorized workspace members and agents may use shared connections through Alfera, and actions may execute using the connected account permissions. |

You represent that you have authority to connect each account and to permit Alfera to access the relevant data and perform the relevant actions. You are responsible for maintaining appropriate permissions in source systems, including Slack channel membership, connected-app roles, billing access, and API scopes.

## 5. AI agents, autonomy, and approvals

Alfera uses AI systems to generate content, make recommendations, run tools, write files, browse sites, operate connected apps, create scheduled tasks, and perform other work. AI outputs may be inaccurate, incomplete, stale, or unsuitable for your use case. You are responsible for reviewing outputs and deciding whether to rely on them.

| Action type | Approval model |
| --- | --- |
| **Read-only or low-risk work** | May run without per-action approval, depending on product behavior and workspace configuration. |
| **Drafting and file generation** | May create drafts, summaries, documents, spreadsheets, PDFs, presentations, screenshots, or artifacts for review. |
| **Slack responses and workflow updates** | May post or update content when requested, approved, or pre-authorized by workspace settings. |
| **Connected-app actions** | May require explicit approval or may run under pre-authorized settings depending on the tool, workspace configuration, and product behavior. |
| **Scheduled tasks** | May run repeatedly according to the schedule, trigger, instructions, and approval model configured by the workspace. |

Approval by an authorized user, or pre-authorization through settings, authorizes Alfera to attempt the action. You are responsible for the consequences of approved, pre-authorized, or configured autonomous actions, including Slack messages, file uploads, connected-app changes, API requests, scheduled task runs, billing actions you initiate, and business decisions made from AI outputs.

## 6. Customer Data and privacy

You retain ownership of Customer Data. You grant Alfera the rights needed to host, process, transmit, display, create, modify, analyze, and otherwise use Customer Data solely to provide, secure, support, bill, and improve the Service, and as otherwise described in our [Privacy Policy](/privacy).

You are responsible for ensuring that you have all rights, consents, notices, and permissions needed to submit Customer Data to Alfera and to authorize Alfera to process data from Slack and connected apps. Do not submit regulated sensitive data unless you have a separate written agreement with us covering that data.

## 7. Acceptable use

You may not use the Service, or allow anyone else to use the Service, to:

| Restriction | Examples |
| --- | --- |
| **Break the law or third-party rules** | Violate applicable law, sanctions, export controls, privacy rules, third-party rights, or the terms and technical limits of Slack or any connected platform. |
| **Access data without authority** | Access, scrape, exfiltrate, alter, or destroy data without authorization. |
| **Abuse communications or automation** | Send spam, phishing, deceptive messages, malware, harmful code, or abusive automation. |
| **Mislead people** | Impersonate others, misrepresent affiliation, or generate deceptive content without proper disclosure. |
| **Facilitate serious harm** | Create or facilitate unlawful surveillance, weapons development, exploitation of minors, harassment, discrimination, or other harmful activity. |
| **Use Alfera in high-risk contexts** | Use the Service where failure could cause death, personal injury, severe environmental damage, critical infrastructure failure, or significant property damage. |
| **Attack the service** | Reverse engineer, interfere with, overload, scan, disrupt, or bypass any security, approval, rate-limit, billing, or access-control system. |
| **Replace professional judgment** | Use outputs as professional legal, financial, tax, medical, employment, insurance, safety, or compliance advice without review by a qualified professional. |

## 8. Billing, credits, and cancellation

Paid features may be billed through Stripe as subscriptions, prepaid credits, top-ups, usage-based fees, or other plans shown at checkout or in an order form. Prices are in U.S. dollars unless stated otherwise. You authorize Alfera and Stripe to charge the payment method you provide for fees and applicable taxes.

| Billing item | Terms |
| --- | --- |
| **Subscriptions** | Renew automatically unless cancelled before the renewal date. |
| **Stripe Customer Portal** | May be used to manage payment methods, invoices, and cancellation where available. |
| **Credits, grants, promotions, or trials** | May expire, may be limited to eligible uses, and may not be transferred or redeemed for cash. |
| **Refunds** | Fees are non-refundable except where required by law or stated in a separate written agreement. |
| **Pricing changes** | We may change pricing, plans, included credits, limits, or billing structure. For material changes to paid plans, we will provide reasonable notice where required by law or contract. |

## 9. Third-party services

The Service depends on third-party services, including hosting, authentication, Slack, Stripe, connected app providers, AI providers, Pipedream, Zapier, E2B, analytics, monitoring, email, scheduling infrastructure, and other subprocessors described in the Privacy Policy. Your use of third-party services is subject to their own terms and policies.

Alfera is not responsible for third-party services, platform outages, account suspensions, API changes, scope changes, rate limits, incorrect third-party data, unavailable integrations, or actions taken by third-party providers. If a third-party service changes or withdraws access, the affected Alfera feature may stop working.

## 10. Intellectual property

Alfera and its licensors own the Service, including software, designs, interfaces, workflows, prompts, agent runtime, infrastructure, models of operation, documentation, and related intellectual property. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable right to use the Service for your internal business purposes.

| Item | Ownership and rights |
| --- | --- |
| **Customer Data** | You retain ownership, subject to the processing rights needed to provide the Service. |
| **AI-generated outputs and artifacts** | You may use outputs produced for your workspace for your business purposes, subject to these Terms, third-party rights, connected-app terms, and applicable law. |
| **Alfera materials** | Alfera retains ownership of the Service, software, product design, workflows, runtime, infrastructure, documentation, and related intellectual property. |
| **Feedback** | If you give us feedback, suggestions, bug reports, or ideas, you grant us a perpetual, irrevocable, worldwide, royalty-free right to use that feedback without restriction or compensation. |

You are responsible for reviewing outputs before using or publishing them.

## 11. Confidentiality

Each party may receive non-public information from the other that is marked or reasonably should be understood as confidential. The receiving party will use reasonable care to protect confidential information and will use it only for the purposes of the Service and the business relationship, except as allowed by law, required by legal process, or permitted in writing.

## 12. Disclaimers and liability

The Service is provided "as is" and "as available". To the maximum extent permitted by law, Alfera disclaims all warranties, express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, availability, reliability, and security.

We do not warrant that the Service will be uninterrupted, error-free, secure, or compatible with every system, or that AI outputs will be correct, complete, current, safe, lawful, or suitable for your intended use. We do not provide professional legal, tax, financial, medical, employment, security, or compliance advice.

To the maximum extent permitted by law, Alfera and its officers, directors, employees, contractors, agents, affiliates, and licensors will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, business interruption, reputational harm, or cost of substitute services, even if advised of the possibility of those damages.

To the maximum extent permitted by law, our total liability for all claims relating to the Service will not exceed the greater of the amount you paid to Alfera for the Service in the twelve months before the event giving rise to the claim or $100.

## 13. Indemnification

You will defend, indemnify, and hold harmless Alfera and its officers, directors, employees, contractors, agents, affiliates, and licensors from and against claims, damages, liabilities, losses, costs, and expenses, including reasonable attorney fees, arising from or related to:

- Your use of the Service or Customer Data.
- Your violation of these Terms, applicable law, or third-party rights.
- Your Slack workspace, connected apps, credentials, permissions, automations, or approval settings.
- Actions approved, configured, requested, or pre-authorized by you or your workspace users.
- Content, outputs, messages, files, or artifacts created, submitted, sent, uploaded, or published through the Service.
- Your violation of Slack, Stripe, Pipedream, Zapier, connected app, or other third-party platform terms.

## 14. Suspension and termination

You may stop using the Service at any time. You can revoke integrations, uninstall the Slack app, cancel paid plans where available, or contact us to request account or workspace deletion. Revoking an integration stops new collection from that source but does not automatically delete previously stored Customer Data.

We may suspend or terminate access to the Service, disable features, limit usage, or revoke integrations if we believe you violated these Terms, your use creates security, legal, operational, platform, or billing risk, a third-party provider requires it, payment fails, or we discontinue the Service. Upon termination, your right to use the Service ends, but provisions that by nature should survive will survive.

## 15. Changes

We may modify, add, remove, suspend, or discontinue features at any time. We may update these Terms from time to time. If changes are material, we will provide reasonable notice, such as by posting the updated Terms, emailing administrators, or notifying users in the app.

Continued use after changes become effective means you accept the updated Terms.

## 16. Governing law and disputes

These Terms are governed by the laws of the State of Delaware, excluding conflict-of-law rules.

To the maximum extent permitted by law, you and Alfera agree to resolve disputes through final and binding arbitration administered by the American Arbitration Association, except that either party may bring an individual action in small claims court or seek injunctive or equitable relief in court for unauthorized access, intellectual property misuse, or confidentiality violations.

Before starting arbitration, the party bringing a dispute must provide written notice and allow at least 30 days for good-faith informal resolution. Arbitration may proceed remotely unless the parties agree otherwise. Claims may be brought only on an individual basis and not as a class, collective, representative, or private attorney general action. Each party waives any right to a jury trial to the maximum extent permitted by law.

## 17. Miscellaneous and contact

These Terms, together with the Privacy Policy and any applicable order form or written agreement, are the entire agreement between you and Alfera for the Service. If any provision is unenforceable, the rest remains in effect. Our failure to enforce a provision is not a waiver. You may not assign these Terms without our consent. We may assign these Terms as part of a merger, acquisition, financing, reorganization, sale of assets, or by operation of law.

Questions about these Terms or the Service can be sent to [hello@alfera.ai](mailto:hello@alfera.ai). Security reports can be sent to [security@alfera.ai](mailto:security@alfera.ai).

# Frequently asked questions — https://www.alfera.ai/faq

Straight answers about what an AI coworker actually does, and how you stay in control.

## What is Alfera, exactly?
Alfera is an AI employee for your business. It connects to the tools you already use, understands a plain-English request, and does the whole job — then hands you the finished result. It is not a chatbot that gives advice; it does the work.

## How is it different from ChatGPT?
ChatGPT writes you a draft and a to-do list. Alfera reads your real data, takes the action across your tools, and reports back with the finished output. It closes the loop instead of handing it back to you.

## Do I need to be technical to use it?
No. If you can describe the job to a new employee, you can assign it to Alfera. There is no code, no workflow builder, and no IT project.

## What tools does it connect to?
Email and calendar (Gmail, Outlook), messaging (Slack), CRM (HubSpot, Salesforce), accounting and payments (QuickBooks, Stripe, Square), spreadsheets, scheduling, your store, and thousands more. When an app has no connection, it can use a controlled browser.

## Will it send things to my customers without asking?
Only if you let it. Anything customer-facing or sensitive waits for your one-tap approval by default. You decide what runs automatically and what needs a review.

## How do I know what it actually did?
Every run ends with a plain-English summary: what it read, what it changed, what it sent, and what it skipped. You can inspect each action and its sources.

## Is my business data secure?
Connections use secure sign-in and are scoped to only what a task needs. Credentials are encrypted, access is owner-controlled, and you can disconnect any tool at any time.

## Can it make mistakes?
Yes, like any worker. That is exactly why approvals, summaries, and a full audit trail are built in — so mistakes are caught before they reach a customer and are easy to reverse.

## What happens if it cannot do something?
It tells you plainly, explains what it needs, and asks for a decision instead of guessing. It will not silently produce wrong work.

## How long does setup take?
A few minutes. Connect your first tool, assign one real job, and review the result. Most owners see something useful on day one.

## How much does it cost?
You can start free with no credit card. Paid plans start at $50/month when Alfera is handling recurring work, and you can cancel anytime.

## Can my team use it too?
Yes. On team plans, everyone can assign work, and you get shared run history and seat-level controls.

## What should I have it do first?
Pick the repetitive job that is slipping right now: chasing quotes, triaging the inbox, sending invoice reminders, or building a weekly report. Start there and expand.

## Can I cancel anytime?
Yes. There is no annual contract required. Upgrade, downgrade, or cancel whenever you like.