Slack
The shared-team view. Work, corrections, questions, and approvals can remain visible to the people in the connected workspace.
Keep the work visible and the access narrow
Each fidelic agent works from customer-approved sources, carries checks and approvals with the result, and writes the work where the accountable team can inspect it. The procurement record below marks current evidence and every gap.
The exact route depends on the role and connected systems
A fidelic agent reads only the customer sources approved for the job, uses model, hosting, connection, and payment providers where the service requires them, and writes the result into the agreed work environment or customer system. The exact providers and permissions vary by agent; they are not replaced by a single inherited security claim.
- 01
Approved source
A customer account, file, message, record, or public source named for the work.
- 02
Scoped processing
The service and its providers process only what the approved work requires.
- 03
Checked result
Sources, acceptance checks, open questions, and approval state travel with the output.
- 04
Customer record
Work is written into Slack, WhatsApp, Teams, or the connected system agreed for the job.
Six controls built into the customer path
Verified customer identity
Customer data routes require a verified account. A setup-continuity cookie is not accepted as customer authentication.
Customer-scoped connections
The work uses the accounts and systems the customer approves for that agent. The customer can revoke provider access.
Credentials stay out of the browser
Slack bot tokens, Google credentials, partner codes, and provider secrets are not sent to browser code or written into customer-visible logs.
Owner approval before commitment
External, binding, irreversible, licensed, employment, spending, and public-record actions wait for the named owner or qualified professional.
Visible work record
The result, sources, open questions, and approval state are written into the agreed work environment or connected system.
Bounded service errors
Customer-facing errors do not include provider bodies, credentials, authorization codes, stack traces, or other secrets.
Procurement facts mark every published and missing document
A vendor claim, inherited cloud control, or role label is not evidence issued to FidelicAI. Every absent underlying document is marked as not published.
- Customer agreement
- Published
- Ownership, connected services, billing, cancellation, liability, and the delivery remedy are shown before payment.
- Security contact
- Available
- Security and procurement questions go to hello@fidelic.ai with the system, data class, and decision deadline.
- FidelicAI SOC 2 report
- Not claimed
- FidelicAI does not claim its own SOC 2 attestation. A provider report is not a FidelicAI report.
- Data processing addendum
- Not published
- A standard DPA is not published today. Do not send regulated or highly sensitive material under the public agreement.
- Subprocessor register
- Not published
- Provider categories are disclosed, but a vendor-by-vendor register and change-notice process are not yet public.
- Insurance certificate
- Not published
- FidelicAI does not publish a technology E&O, professional-liability, or cyber-insurance certificate today.
- Status and uptime history
- Not published
- There is no public status page or historical uptime record today, and no uninterrupted-availability claim.
Slack, WhatsApp, and Teams have different retention facts
A compact owner briefing and decision surface. Full work products stay in connected systems; ordinary participation in every group is not implied.
Microsoft Teams
The governed Microsoft 365 surface. The approved tenant, account owner, channel, and retention arrangement are stated before work begins.
Use the public agreement for ordinary business records
Do not send health records, payment card numbers, government identification numbers, or material covered by a confidentiality obligation you cannot extend to a vendor. Legal, finance, insurance, employment, compliance, and intellectual-property agents may prepare and maintain the factual record. The licensed decision, professional opinion, filing authority, and final sign-off remain with the relevant person.
If your procurement requires a FidelicAI SOC 2 report, a standard DPA, a published subprocessor register, a BAA, an insurance certificate, on-premises operation, or a historical uptime record today, the public service does not meet that requirement.
Public work proves owner visibility
New Street Studios shows fidelic agents posting work, naming blocked handoffs, and waiting for approval in Slack. It demonstrates an owner-visible work record. It does not verify isolation, data handling, insurance, or compliance.
Security questions answered plainly
Can I send regulated or highly sensitive data to a fidelic agent?
Not under the public agreement. Do not send health records, payment card numbers, government identification numbers, or material covered by obligations you cannot extend to a vendor.
Does FidelicAI have its own SOC 2 report?
FidelicAI does not claim its own SOC 2 attestation today. Buyers should not treat a model, hosting, connection, or payment provider’s report as a FidelicAI report.
What remains after cancellation?
Slack history and work written into customer systems remain there. WhatsApp and Teams retention depends on the account and channel arrangement. Internal agent instructions and evaluation cases are not exported.