Optional connections require authorization. AI features can send relevant information to a processing provider. Employee Telegram messages are stored for the owner's workspace. Private workspaces are not public. You can disconnect services and request deletion.
AI consultant
On the public AI consultant page, conversation text and live microphone audio are sent to the configured AI provider to answer you. Text history is held only as a short-lived public session and is not joined to private company memory. If you submit the consultation form, the contact and business details you review are stored as a sales request. With your separate WhatsApp consent, an approved WhatsApp Business template may be submitted for delivery; provider acceptance is not proof that you read it. A requested meeting is not confirmed until our team contacts you.
1. Who we are and what this notice covers
MAAD is an AI-assisted business workspace developed by Aron Fund. This Privacy Policy explains how information is handled on farazly.com and in MAAD workspaces and enabled integrations.
MAAD is currently being developed and used in controlled deployments. A public product website does not make a workspace public or create an account for its visitors. Future business deployments may be configured for a particular customer; their service agreement and any applicable data-processing terms will identify the operator, responsibilities, hosting arrangements and additional requirements.
For information submitted through this public website or directly to us, Aron Fund is responsible for handling the information. Where an organization supplies employee, customer or other business information to a MAAD workspace, that organization determines its business purposes and authorized users. Its own privacy notices also apply. Contact that organization or contact us if you are unsure who handles your request.
2. Information MAAD handles
The information processed depends on the features you or your workspace administrator actually enable:
- Account and workspace information: user identifiers, names, login credentials in protected authentication form, membership, roles, preferences such as the chosen panel language, and authorization records.
- Conversations and business content: prompts, messages, responses, saved notes, task instructions, company knowledge, uploaded files and generated documents. Attachments may include images, document text or sampled video frames.
- Employee messages on Telegram: when an organization enables the company bot, messages, voice notes and files sent by approved employees, the employee's Telegram identifier and display name, the language they chose, automatic transcripts and file summaries, the owner's replies and their recorded send results.
- Voice interactions: microphone audio when you start a supported voice session or record a voice reply, and the transcripts, summaries or notes produced by enabled conversation features. Audio needed for a voice response or a transcript is transmitted to the configured voice-processing provider. Browser microphone permission remains under your control.
- Connected-service information: the selected account or channel, approved profile and content data, reports and metrics returned by the provider, permission scopes, connection timestamps and access or refresh tokens; supported business connections may also supply order summaries, staff reports and task records within their authorized scope.
- Operational and support information: task status, approvals, audit records, usage and cost records, support correspondence, and technical information such as IP address, browser type, request time and error details where collected by the website, hosting infrastructure or application.
Do not submit passwords, payment-card details, identity documents, health records or other highly sensitive information in chat unless a specifically agreed and suitable workflow requires it. Do not provide another person's information without authority and any required notice or consent.
3. How information is used
We use information to authenticate users; operate the selected workspace; respond to prompts; retrieve authorized knowledge and reports; generate requested content; prepare or carry out supported, authorized workflows; maintain conversation continuity; provide support; enforce permissions and usage limits; investigate errors or misuse; and meet applicable legal obligations.
Information from a connected account is used for the features explained during connection and within the permissions granted. A request to connect one account is not permission to access another account or use its data for unrelated purposes. Optional features may require a separate choice or authorization.
Where data-protection law requires a legal basis, we rely on the basis appropriate to the particular activity, such as providing a requested service, consent for an optional feature, legal obligations, or legitimate interests in operating and securing the service, subject to applicable rights and safeguards. An organization's processing of its business data may have a different legal basis.
4. Employee messaging through Telegram
An organization can enable a Telegram bot so that approved employees report to the owner. Each employee starts the bot, is approved by the owner and chooses a language; the bot never contacts anyone who was not approved. Messages, voice notes and files are stored in that organization's workspace so the owner can read, answer and follow up on them, and so drafts stay consistent with the conversation history.
Voice notes are transcribed automatically and files are summarized by the configured AI provider; transcripts are labelled as automatic and can be redone. On the owner's request, messages can be translated for the owner's reading only — using Google Cloud Translation with the owner's own key when configured, otherwise the AI provider. Sending an owner's reply requires confirmation. The result of each send attempt is recorded; provider acceptance is not evidence that the employee has read it.
Employees should use the bot for work communication only and follow their organization's guidance. The organization is responsible for informing its employees about this processing. Employee-facing bot messages follow the employee's chosen language; the owner's panel language does not change what employees receive.
6. AI processing and other recipients
MAAD uses external AI processing, including OpenAI in the current deployment. When an AI feature is used, relevant prompts, attachments or extracted content, voice audio, employee messages under review, conversation context and authorized tool results may be sent to that provider. Optional searches, translation and integrations send the query or data necessary for the requested feature to the corresponding service.
Current text-chat requests are configured not to create stored response objects at the AI provider. This is not a promise of zero provider retention: provider security, abuse-prevention and service rules may still apply. We do not use connected social-account data to train a general-purpose model. We do not sell personal information or use connected-account information to target advertising.
Information may also be available to authorized workspace administrators, personnel providing support, infrastructure and hosting providers, or a service you direct MAAD to use. We may disclose information when required by law, to protect rights and security, or in a business transfer subject to appropriate confidentiality and applicable legal requirements. We do not make private workspace information public merely because you visit this website.
A customer deployment can have its own approved providers and hosting configuration. Materially different processing should be explained before the affected feature is enabled, through an updated notice or the applicable deployment terms.
7. Storage, security and retention
Access controls, authenticated workspace boundaries, encrypted HTTPS connections and restricted server-side credential storage are used to protect information. No service can guarantee absolute security. Closing the browser or ending a call does not necessarily delete saved messages, attachments, notes, reports or audit records.
We retain information for the relevant service purpose, taking into account the workspace's ongoing use, the type of record, support and security needs, deletion requests, contractual requirements and applicable legal obligations. The current deployment does not apply one universal automatic deletion period to all records. Workspace content and history remain available until removed through an available control or a verified administrative deletion process.
Disconnecting a social service in MAAD removes that connection's active tokens and current cached snapshot from the application. It does not remove posts at the original provider or automatically erase historical excerpts already included in conversations, generated reports, logs or backups. You can request deletion of those related records too. Backup copies may remain until securely rotated or removed; any required exceptions or timing will be explained when your request is handled.
Provider-specific requirements and applicable law can require earlier deletion or refreshing of data. We assess deletion and retention requests against those requirements rather than treating revoked access as permission to keep using the data.
8. Your choices, access and deletion
You can decline an optional connection, stop a voice session, change browser permissions, or disconnect an integration through the controls available in your workspace. You can also revoke the application's authorization directly at the original provider. An employee can stop using the company bot at any time and ask the organization to remove their messages.
For Google and YouTube, you can revoke access through Google's third-party permissions settings. For other services, use their connected-app or business-integration settings. Revocation and deletion are related but distinct; use our data deletion instructions to request removal of stored MAAD data as well.
Subject to applicable law and the relevant organization's responsibilities, you may request access, correction, deletion, a copy of your information, restriction of processing or an objection to certain uses. You can withdraw consent for consent-based processing without changing the lawfulness of earlier processing. You may also contact a competent data-protection authority where those rights apply.
Send requests to info@aronfund.com. We may ask for limited information to verify your identity and authority, but never ask you to send a password, access token or one-time login code. If your employer or another organization controls the records, we may refer the request to it or coordinate with it.
10. International processing and business deployments
Hosting, support and AI providers may process information in countries other than your own. The applicable locations and contractual safeguards depend on the deployment and providers in use. Contact us before sending data that must remain in a specified country or requires sector-specific protection. A general website notice is not a data-residency, certification or regulatory-compliance guarantee.
Before a customer deployment handling regulated or employee data, the parties should agree the roles, access model, providers, retention and any required data-processing terms. A customized deployment does not automatically include every integration or permission.
11. Children, updates and contact
MAAD is intended for authorized adult business users, not as a service directed to children. Contact us if you believe a child has submitted personal information without appropriate authorization.
We may revise this policy as the product or processing changes. The current version and its date will appear here; material changes will be communicated through an appropriate channel and additional consent requested where required. For privacy questions or complaints, contact info@aronfund.com.
MAAD · An Aron Fund product · 18 September 2026
5. Social accounts and provider permissions
You connect supported accounts through the provider's official authorization process. MAAD does not ask for your TikTok, Google, Facebook or Instagram password in its own connection forms. Access tokens are held on the server for the authorized connection, including renewal where the provider permits it; they are not intended to appear in chat responses.
Current social connectors are read-only. They do not enable posting, advertising, sending social messages or deleting provider content. Any future write capability requires a supported implementation, the necessary provider permissions and an appropriate user authorization flow. Listing an integration is not a claim that the provider has approved every deployment.
Reports may be partial or cached and show the time of collection. These integrations retrieve metadata and metrics; this is not a claim that MAAD watches complete videos. When you request AI-assisted analysis or enable company context, relevant saved account information and excerpts may be supplied to the configured AI provider to answer your request.