AfieldConnected accounts and your instructions
Connect only accounts you own or are authorized to use. Check the permissions displayed during authorization and the destination selected for a task. You can disconnect an account or revoke access through the connected service.
The Privacy Policy describes what is retained for each connected workflow. Disconnecting a service and deleting all existing workspace content are different requests; use the policy and contact route when you need account deletion.
How requested content is processed
AI-assisted tasks may require the text, files or connected content needed for that task to be processed by service providers acting on Afield’s behalf. The policy describes this processing and the sharing needed to operate the service. Afield states that it does not sell or rent personal information.
Some desktop features store information locally. Account synchronization, authorization callbacks and cloud processing use Afield’s hosted environment for the information they require. Review the policy against the particular workflow you intend to run.
Analytics and optional content review
The current policy describes Basic product analytics and masked session replay for signed-in users. Basic analytics excludes input text, visible page text, URL parameters, credentials, contact content and file contents. Product events are retained for up to 90 days; masked replay may be retained for up to 30 days.
Optional content review is off by default and has a separate consent. You can turn Basic analytics and replay off in Settings. See the full policy for what is removed when those choices change, rather than assuming every type of data follows the same retention rule.
Review the actual external action
When sending, publishing or updating content, check the final version and destination using the applicable product controls. After an action, inspect its result. A prepared draft and a completed external action are different records.
If an action times out, inspect the destination before retrying. This helps avoid duplicate sends or posts. The channel-action guide explains the practical checks.
Report a security or privacy concern
Email contact@afieldai.io with the affected feature, approximate time and a description of the problem. Include a safe-to-share task identifier when available. Do not send passwords, access tokens, verification codes or full payment details.
For access, correction or deletion requests, use the same contact route and describe the request. This page summarizes the published policy; the Privacy Policy and Terms of Service contain the full current text.