MaShop is provided under the trade name EDEVERSE. In this policy, “Edeverse” and “we” refer to the operator of the service. Contact: contact@edeverse.com.
This policy explains how personal information is handled when you visit our sites, use the workspace, create applications or use agents and connected tools. For questions or privacy requests, contact contact@edeverse.com.
1. Our role and the scope of this policy
Edeverse determines the purposes of processing needed to run MaShop accounts, billing, security and customer support. When you use MaShop to process information about other people for your own project or organisation, you determine the purposes of that work. You must have a lawful basis for it and provide the notices required for the people concerned. Where we act on your instructions as a processor, the relevant contractual and legal requirements also apply.
This policy concerns MaShop. It does not replace the privacy policy of an application you build or of GitHub, a hosting provider, WhatsApp, an MCP server or another service you choose to connect. Those services may also process information under their own policies.
2. Information we process
Account and contact information. This includes your name, email address, profile information, sign-in identifiers, account settings and communications with support. An identity provider may supply information needed to sign you in.
Project and AI content. This includes prompts, conversations, uploaded files, code and configuration needed for an operation, generated output, tool inputs and results, project references and execution history. Agent instructions, skills, saved memories, schedules and triggers may form part of that content. If you place personal information in these materials, that information is processed with the task.
Connections and permissions. We process connection identifiers, the accounts and resources you authorise, permission settings and the credentials or tokens needed to operate a connection. Avoid placing secrets in a chat or source file when a dedicated connection or secret field is available.
WhatsApp information. When you connect your account, the gateway processes the session information needed to maintain that connection. The service can record incoming and outgoing message text, message identifiers, contact identifiers or phone numbers, contact names when provided, and dates. Enabled agents can use that information to read conversations, respond and react to incoming messages. The current connection links a WhatsApp session; it is not represented as Meta's official Cloud API integration.
Billing and usage. This includes your plan, credit balance and ledger, purchases, payment and subscription references, billing status and the usage needed to calculate consumption. Payment details are handled through Whop's payment process. Do not send payment-card details through chat or support.
Technical information. Service requests and diagnostics can include IP addresses, timestamps, browser or device information, approximate country, requested routes, errors, performance information and security events. An anti-abuse device identifier may be used to detect repeated claims for complimentary usage. Cookies and similar storage are explained in the Cookie Policy.
3. Why we process information
We use the information necessary to create and authenticate accounts, perform requested tasks, run previews, manage connected services, save relevant project and agent context, take payments, meter usage, provide support and communicate about the service. These uses support performance of our agreement with you or steps you ask us to take before that agreement.
We also use proportionate technical and account information to prevent fraud and abuse, enforce permissions, investigate incidents, diagnose errors and maintain the service. Depending on applicable law, these activities rely on our legitimate interests in operating a secure service, legal obligations, or another applicable legal basis. We consider the effect on the people concerned and do not treat these interests as unlimited permission to use their information.
Where optional analytics or other tracking requires consent, your choice applies as explained in the Cookie Policy. You can withdraw consent without affecting processing that was lawful before withdrawal. Accepting the Terms of Service is not, by itself, consent to optional tracking.
We may retain or disclose information to comply with a lawful request, meet accounting obligations, establish or defend a legal claim, or protect people against a credible threat. We assess such requests and limit the information disclosed to what is appropriate and legally required.
4. AI processing and external actions
To answer a request, MaShop sends the relevant context to the model provider used for that operation. This can include your prompt, recent conversation, selected code or files, agent instructions and memories, and results returned by tools. The context can contain information about you or other people. Limit it to what the task needs.
MaShop uses Fireworks for supported model requests; some Code configurations also support Anthropic. Models, routing and available providers may change. A model's brand and the company operating its inference endpoint are not necessarily the same. The use of an agent SDK does not mean that every request is sent to that SDK publisher's model service.
Provider terms and account settings affect how submitted information is retained and used. Do not assume that every model or connected service offers zero retention, processing in a particular country, or identical training restrictions. Contact us before submitting information that requires a particular processing arrangement.
When an agent calls a connected tool, the required inputs pass to that service and its response returns to MaShop and, where needed, the model. A tool can transmit information outside MaShop or change a resource. Check the connection, tool and autonomy settings. An approval requirement depends on the operation and configuration; there is not necessarily a separate prompt before every action.
5. Who receives information
Access is limited to the people and services involved in the relevant purpose, including authorised personnel providing operations or support and the following types of recipients:
| Recipient | Purpose and information involved |
|---|---|
| Supabase | Authentication, database and storage used for account information, project context, conversations, permissions and execution records. |
| Netlify | Hosting and delivery of MaShop sites and application endpoints, including requests and technical logs. |
| Fly.io | Environments that run project code and previews, with the files, configuration and runtime information needed for them. |
| Fireworks and, where configured, Anthropic | AI inference using the context needed for the requested operation. |
| Whop | Checkout, subscriptions, purchases and payment records. |
| Resend | Service emails, including the recipient's address and the content needed for the notification. |
| Sentry | Error and performance diagnostics where enabled. |
| Google Analytics | Audience measurement on configured sites, subject to the choices explained in the Cookie Policy. |
| Services you connect or ask an agent to use | Relevant account, resource, task and tool data; for example GitHub, a database, a publishing provider, an MCP service or WhatsApp. |
These services do not all receive the same information and are not all involved in every request. Providers involved in a payment or a connection may also act independently for their own account, security and legal obligations.
We do not sell your personal information. Sharing information needed to perform a requested tool operation is part of that operation, rather than a sale of your information.
6. Project visibility and collaboration
People with access to a project may see its shared resources and the information available under their role. Code and Agents conversations are distinct, but an authorised task may use resources from the same project or connected account. Some connections, including the WhatsApp account connection, operate at owner-account level. Do not assume a project is an isolated copy of every external account connected to its owner.
A public repository, published application, shared link or externally sent message can make information available to others. Removing it from MaShop does not remove copies held by recipients, search engines or another provider. Review what you publish or share.
7. Retention and deletion
We retain account and project information for the purposes described in this policy, taking into account the life of the account, the feature involved, legal obligations, security needs and unresolved disputes. Different records have different lifecycles; deleting a conversation is not the same as deleting all project, billing, agent memory or external-service records.
The workspace's conversation-cleanup rule selects conversations that have not been updated for more than seven days, while preserving the most recent conversation for each user, project, mode and archived-or-active group. This is not a promise that every message, execution log, backup or connected-service record is erased after seven days. Save information you need independently of chat history.
You can request access or deletion through the contact address below. We may need to verify your identity or authority over an organisation's data. A request may require separate action at a connected provider. Some information must be retained for legal obligations, security investigations or the establishment and defence of claims; where a request cannot be fully fulfilled, we will explain the applicable reason. Backup rotation and records held by other providers can affect when deletion is complete.
8. International processing and security
Providers and connected services may process information outside your country. MaShop does not promise that all processing takes place in a single country. When a transfer is subject to specific legal requirements, the required safeguards must apply. Contact us for information about the arrangements relevant to your use; do not infer a particular transfer certification or contractual mechanism from the name of a provider.
We use access controls, authenticated service connections and other technical measures to protect information. No online service can guarantee absolute security. Your own permissions, devices, shared projects and connected accounts also affect protection. Report a suspected exposure promptly and revoke any affected credentials through the relevant provider.
9. Your rights and choices
Depending on applicable law, you may have rights to obtain information and a copy of your data, correct it, request deletion, restrict processing, object to certain uses, receive portable data and withdraw consent. These rights can have legal exceptions. You may also complain to the competent data-protection authority.
In Senegal, the Commission de Protection des Données Personnelles (CDP) provides information about individuals' rights. Its published contact address is contact.cdp@cdp.sn. Depending on your circumstances and applicable law, you may also contact the competent authority in your own country.
Send requests to contact@edeverse.com, preferably from the email address associated with your account. Identify the account and the request, without sending passwords or unnecessary identity documents. We will respond within the time required by applicable law. If the data concerns a customer's application or messaging activity, that customer may be the appropriate party to answer the request; we can help identify the relevant responsibility.
You can also review account settings, restrict or revoke connections, stop automations and manage browser storage. Revoking access does not retract information already sent or undo an action already performed.
10. Children and policy changes
MaShop is intended for adults. Do not create an account for a child or submit children's information without a lawful basis and the safeguards required for that processing. Contact us if you believe a child has provided information unlawfully.
We update this policy when practices or requirements change. Material changes will be communicated through the service or account contact details. Where a new purpose requires consent, an updated policy alone does not provide that consent.