At a glance
- We use information to run your workspace, process agent requests, and support you.
- Organizations control the data they bring to MAAP and the agents they deploy.
- We do not sell personal information. You can contact us to exercise applicable privacy rights.
A quick guide. The full policy below provides the details.
Who we are and when this policy applies
MAAP (Managed AI Agents Platform), operated by Prisiops, LLC, a Texas limited liability company, provides tools to build, deploy, and manage AI agents. This policy explains how we handle personal information through maap.dev, our dashboard, APIs, embedded widgets, hosted agent pages, demonstrations, and communications with us. “We,” “us,” and “our” refer to Prisiops, LLC. MAAP is our service name.
For account administration, billing, website operations, and direct communications, we determine how information is used. When an organization uses MAAP to process its documents, connected-service data, or conversations, we generally process that information on its behalf and under its instructions. That organization determines the purpose of its agent and is responsible for its own privacy notice and lawful use of the information.
If you use an agent on another organization’s website, read that organization’s privacy notice too. This policy does not replace the privacy policies of customer websites or independent third-party services.
Information we collect
The information involved depends on how you use MAAP and the features an organization enables.
- Account and workspace information: name, email address, authentication information, profile details, organization membership, role, invitations, and account preferences. Signing in through a provider such as Google shares the profile information authorized for that sign-in.
- Billing records: billing contact information, payment-provider identifiers, purchases, credit balances, usage charges, and transaction history. Stripe processes payment details; MAAP does not need your full payment card number to operate your credit balance.
- Customer content: agent instructions and configurations, uploaded files and enabled attachments (including images, audio, or video and their metadata), crawled website content, extracted text and embeddings, prompts, conversation messages, AI responses, and tool inputs and outputs.
- Widget information: messages, session and browser identifiers, the website or hosted agent page where a chat is used, and contact details submitted through an enabled lead-capture form. An organization may associate a conversation with a name or email address it provides.
- Integration information: connection settings, authorization tokens or API credentials, and information retrieved from services you connect. The information accessed depends on the granted permissions and enabled tools.
- Technical and usage information: IP addresses, request identifiers, browser and device information, error and security logs, timestamps, feature usage, model usage, and referral or campaign parameters.
- Communications: sign-ups for product updates, support requests, and feedback, including your self-selected user type, category, optional contact details, workspace or website context, and message.
Where information comes from
We receive information directly from you, automatically when you interact with the service, and from organizations that invite you or operate an agent you use. We also receive information from authentication providers, payment processors, authorized integrations, and websites an organization instructs us to crawl.
Only upload or connect information you are authorized to share. Publicly accessible information may still contain personal information and may be subject to privacy, intellectual property, or other restrictions.
How and why we use information
We use information to deliver the service, administer our relationship with you, and operate the platform responsibly.
- Create accounts, authenticate users, manage organization access, and maintain preferences.
- Run agents, retrieve relevant knowledge, maintain conversations, execute configured tools, and support human review and approval workflows.
- Calculate usage, maintain credit balances, process payments, and resolve billing questions.
- Troubleshoot errors, evaluate service performance, respond to feedback, and improve product functionality.
- Detect abuse, protect accounts and infrastructure, investigate incidents, enforce our terms, and meet legal obligations.
- Send operational notices and respond to requests. Where permitted, send product updates, with an option to unsubscribe from marketing messages.
SMS notifications and mobile numbers
MAAP offers optional SMS notifications to dashboard users who add and verify a US mobile number and then opt in for a workspace. If you do, we collect your mobile number, its verification status, the notification categories you chose, and the time, source, and disclosure version of your consent. We use this information only to send the verification code you request, to send the account notifications you enabled, and to honor opt-outs.
We do not sell mobile numbers or SMS consent information, and we do not share them with third parties or affiliates for their own marketing or promotional purposes. Mobile numbers are shared only with the messaging providers that deliver texts on our behalf, and only for that purpose.
Message frequency varies with workspace activity. Message and data rates may apply. Consent to SMS is not a condition of purchase. You can turn categories off or remove your number in Settings, or reply STOP to any message to stop texts and HELP for help. Turning off SMS does not affect essential account, billing, or security email.
AI processing and human access
An agent request may include your message, relevant conversation history, agent instructions, retrieved document excerpts, and tool results. We transmit that context to the configured model service to generate a response. Depending on the selected model and enabled features, inference is provided through Amazon Bedrock or directly by OpenAI, Anthropic, or Google Gemini. Amazon Bedrock also provides embeddings. The provider receives the context needed for that request; choosing another model can change the recipient of subsequent requests.
Knowledge-base ingestion may send documents or website content to storage, extraction, crawling, embedding, and search services. Connected tools may send selected information to external services or perform actions there. Review an agent’s configuration and integration permissions before supplying confidential information.
Authorized workspace users can access conversations and other content permitted by their roles, and may participate in a conversation or review an action. Authorized MAAP personnel may access information when needed for support, security, or operations. Do not assume a chat is visible only to an AI model.
Generating responses and embeddings is distinct from training a general-purpose model. Our content license does not authorize training general-purpose models on customer content. Provider retention and permitted use depend on the applicable service agreement and account settings; do not assume zero retention or that all providers have identical terms. Contact privacy@maap.dev for the arrangements relevant to your workspace before sending information subject to special restrictions.
AI responses can be inaccurate and can include personal information supplied in a conversation or source document. Do not use an AI response as the sole basis for a decision with legal or similarly significant effects on a person.
Cookies, browser storage, and preferences
MAAP uses essential cookies and browser storage to keep you signed in, protect your account, and continue a chat. Optional storage for preferences and campaign attribution stays off until you turn it on in the cookie banner or Cookie settings, and you can withdraw at any time. We use no advertising or analytics vendors on our sites.
Our sites do not currently change their behavior in response to the legacy Do Not Track browser setting. We do not sell personal information or share it for cross-context behavioral advertising, so there is no such activity to opt out of on our sites. Where applicable law requires recognition of an opt-out preference signal, that obligation still applies. Use Cookie settings for optional storage preferences. An organization operating its own website may use separate tracking tools and is responsible for its own disclosures and choices.
The cookie notice lists every item we store, who receives it, how long it lasts, how to change your choice, and how the chat widget behaves on other websites. Clearing your browser storage does not delete information already stored by MAAP or the organization operating an agent.
Connected accounts and Google user data
Connecting an account can give MAAP access to the data and actions shown on its authorization screen. For example, enabled Google integrations can access Gmail messages and metadata, Calendar events, or Drive files and metadata, and perform the permitted actions you configure. Retrieved content can become part of a conversation, knowledge source, or model request. Connect only accounts you are authorized to use and review who can use the connection in your workspace.
MAAP’s use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google Workspace data is used for the user-facing features you authorize. It may not be used for advertising, sold, or used to train general-purpose AI models. Transfers and human access are limited by those requirements, including the applicable consent, security, legal, and service-delivery exceptions.
You can revoke access through the connected provider’s account permissions and remove the connection in MAAP. Revocation stops future access through that authorization; it does not automatically delete information previously imported into a conversation, knowledge source, backup, or external service. For deletion, use available workspace controls or contact privacy@maap.dev; customer-controlled data requests are handled with the responsible organization.
Instant website demos
The no-account instant demo reads public pages from the website you provide and stores the messages you send so the demo can answer you. The demo expires after five minutes. Automated cleanup deletes its temporary agent, access key, conversation messages, conversation history, and cached replies, normally within the next few minutes. If cleanup fails, it is retried; expiration and deletion are separate steps.
We do not retain instant-demo conversations for quality review after cleanup. Public-page scrape results may remain cached for up to one hour. Operational and security records, backups, and data processed by external providers follow the retention criteria described in this policy. Avoid entering confidential or sensitive information into a public demo.
Retention and deletion
Retention depends on the type of information, the customer’s instructions, active service needs, and legal requirements. Account information and customer content are retained as needed to operate the account and configured features. Billing, security, and dispute records may need to be kept longer for accounting, fraud prevention, or legal obligations.
Some operational records, sessions, and conversations use expiration settings. Expiration is not a promise that all copies disappear immediately: database cleanup, caches, backups, legal holds, and connected services may follow different schedules. New feedback submissions are scheduled for expiration after one year; information copied into a support or legal matter follows that matter’s retention needs.
You may request deletion by contacting privacy@maap.dev. If the information belongs to a customer-controlled workspace or agent, contact that organization first; we can assist it with requests where appropriate. Removing an integration does not automatically remove data already transferred to that provider.
How we protect information
We use technical and organizational safeguards intended to protect information, including authentication, role-based access, protected credential storage, and access controls around infrastructure. Safeguards depend on the feature and service involved; no system or transmission method is completely secure.
Protect your account credentials and API keys, grant integrations only the permissions needed, and review workspace membership. Report suspected vulnerabilities or unauthorized access to security@maap.dev. Do not include passwords, access tokens, or sensitive customer records in a general feedback report.
Your privacy choices and requests
Depending on your location and applicable law, you may have rights to know whether we process your information; access or receive a portable copy; correct inaccuracies; request deletion; restrict or object to processing; withdraw consent; and opt out of certain sales, targeted advertising, or profiling. These rights may have exceptions. We do not use personal information for the sale or advertising-sharing activities described above.
Email privacy@maap.dev with the request, your relationship to MAAP, and enough context to locate the information. Do not send identity documents or sensitive records unless requested through an appropriate channel. We may need to verify your identity or an authorized agent’s authority before acting. We will respond within the period required by applicable law and explain any applicable extension or refusal.
Where a right to appeal applies, reply with “Privacy request appeal” and the reason you disagree. We will review the decision and explain the outcome and available complaint options. You may also complain to your state attorney general or relevant data protection authority. We will not unlawfully discriminate against you for exercising a privacy right.
Workspace members can ask their administrator to update organization-managed details. Widget users should identify the website and approximate conversation date when requesting help from its operator. Unsubscribe links control marketing email; essential account, billing, and security communications may still be sent.
Additional regional information
For California residents, the information categories described above include identifiers, commercial information, internet or network activity, customer communications and content, professional information, and sensitive personal information such as account access credentials or sensitive details you choose to submit. The sources, purposes, recipient categories, and retention criteria for those categories are described in the corresponding sections above. Content can contain additional categories depending on what you or your organization provide.
We use sensitive information to provide requested features, secure the service, and fulfill legal obligations, rather than to infer personal characteristics. We do not sell personal information or share it for cross-context behavioral advertising, including information about people we know are under 16. Where the California Consumer Privacy Act applies to our processing, you may exercise its access, correction, deletion, portability, and applicable limitation and opt-out rights using privacy@maap.dev. Authorized agents may submit requests; we may require proof of authorization and identity verification where permitted.
Other US state privacy laws may provide similar rights, including an appeal of a refused request and an opt-out of specified profiling. To appeal, email privacy@maap.dev with “Privacy request appeal.” If an appeal is denied, we will provide the complaint method required by applicable law. For EEA and UK residents, rights may also include restriction of processing, objection to processing based on legitimate interests, and a complaint to the supervisory authority where you live, work, or believe an infringement occurred.
International users and legal bases
MAAP operates from the United States. Information may be processed in the United States and other locations where our providers operate, which may have different privacy laws from your location. Where required, international transfers must use a lawful transfer mechanism and appropriate safeguards. Contact us for information about safeguards relevant to your use.
Where European Economic Area, United Kingdom, or similar laws apply, our legal basis depends on the activity: performing a contract for account and service delivery; legitimate interests in operating, securing, and improving the service, balanced against your rights; legal obligations for required records and disclosures; or consent where required. You can withdraw consent without affecting processing that was lawful before withdrawal. For customer-controlled information, the customer determines the applicable legal basis.
Children and sensitive information
MAAP accounts are intended for adults and business users. Our services are not directed to children under 13 or a higher age requiring parental consent under applicable law, and we do not knowingly collect their personal information for our own purposes. If you believe a child has provided information, contact privacy@maap.dev so we can investigate and take appropriate action.
Customers must assess their audience and must not deploy MAAP for children under 13 or knowingly submit their personal information without our prior written agreement and all legally required safeguards. For other minors, customers must provide required notices and obtain any required parental or other consent. Do not submit health records, government identification numbers, financial account credentials, or other highly sensitive information unless the use is authorized and appropriate safeguards and agreements are in place.
Policy updates and contact
We may update this policy as our services or obligations change. The date at the top identifies the current version. For material changes, we will provide additional notice where required, such as a service notice or email. We will not treat a policy update as permission to use previously collected information in a materially incompatible way. We will provide any required notice and obtain any legally required consent before a new use. Reading this policy or using the service does not itself constitute consent to every processing activity.
For privacy questions, requests, or information about the organization responsible for your data, contact Prisiops, LLC / MAAP at privacy@maap.dev. For general assistance, contact support@maap.dev.