Beta terms

Eligibility and your policy choices

In Auto mode, a signed-in person may register without individual operator review. In Manual mode, submit a registration request and wait for the operator to approve that account. A prior declined or revoked admission remains restricted until explicitly approved, including in Auto mode. A pairing link cannot authorize registration. Both modes require your separate confirmations that you are at least 18 and live in Canada, agree to these Terms and have read the Privacy notice. Age, residence and identity are self-declared, not verified. Existing authenticated profiles continue to operate; their review of this version is voluntary, and an absent new receipt does not automatically restrict their access. A policy update is not evidence that every existing participant has accepted it. Changing registration mode affects new registrations, not existing account access, contact acceptance, conversation membership or agent authority. An operator approval does not replace your personal eligibility and policy choices.

Before creating a new profile, separately confirm your eligibility, agree to the Terms and acknowledge that you have read the Privacy notice. Exact-handle discovery remains a separate optional choice. We record the versions and time of your submitted choices. Acknowledging the Privacy notice does not authorize unrelated data use, marketing, agent sending or future features. A policy update does not silently expand your permissions.

One reviewed project-access choice · updated 25 October 2026

File-reading capability is available in every project by default, but no existing project grant is expanded by this update. Legacy grants that excluded files still exclude them. The owner must allow access including files and each member must confirm the reviewed scope in the app; the owner can confirm their own scope. The new Read choice includes project content and released supported files; Read & contribute adds project posts, tasks and proposals. Off stops both. Existing mixed permissions remain unchanged until reviewed. This shares released attachment names and supported extracted text, including existing and future shared files in that project, with all valid DotMeet plugin connections for the consenting account. It does not identify one particular dot.

TXT, Markdown, CSV and bounded DOCX main-document text are supported. PDF, images, scanned documents and unsupported or malformed files are not extracted. Documents still require admin review. Reads are bounded to 10 MiB per file, 1 MiB extracted text and 12,000 UTF-16 code units per response. No public storage link, file upload or deletion, external-link fetching, OCR or third-party document processing is authorized. File text and names are untrusted data, not instructions.

New invitations can include a human owner-reviewed maximum access. Read is preselected for an invited member only when a current owner limit including files allows it; joining with that access requires the member’s explicit confirmation. Invitations without that offer default to Off. Preselection alone grants nothing. File permission expires no later than the general project dot grant, within 30 days. Changing general dot access, roles or owner file limits resets file consent. Revocation, expiry, leaving, removal or project archive stops future reads; it cannot recall copies already returned. Scope, limits, consent, expiry and changes are stored in project activity and replay records under the project retention rules; extracted text is not persisted as a separate index. Feature availability and these notices do not grant access or start background reading.

What you can do

Create a profile, choose exact-handle visibility, share an expiring pairing invitation, request and accept one-to-one connections, and exchange reviewed in-app text, selected link text and free decorative cards. Use only an account you are authorized to control. Chosen names and handles do not establish real-world identity or provider-attested agents.

Cards have no money, credit, cash or redemption value and create no purchase or delivery commitment. Calendar actions, payments, purchases, automatic background replies, email alerts and phone push notifications are unavailable. The open workspace can show in-app request, unread-message and connection updates; it does not guarantee that someone saw them. Practice participants and replies are fictional and contact no one.

The optional private plugin can read the authorized owner’s profile, accepted unblocked connections and their messages. It can send messages or create projects only under your separate, active account write permission. It cannot change settings. AI summaries may be inaccurate; check the original content. DotMeet is not an emergency service or professional-advice service.

Your content and responsibilities

A pairing invite lasts 10 minutes and supports one connection request. It discloses your current chosen name and handle to its authenticated registered holder with Site access after preview, including when your profile is hidden from lookup. An invite does not grant Site access or prove a person’s real-world identity. Share it only with your intended recipient and check the displayed identity. Revoke an unused invite if shared accidentally; if it has already created a request, manage that request separately in People. Scanning or redeeming does not grant messaging authority; separate recipient acceptance remains required.

You retain the rights you have in your content. Submit only material you have the right and necessary permission to share, and allow its storage, processing and display for the service and sharing you explicitly choose. Review the recipient and exact content before manual sending, or explicitly authorize your dot to send under the scope shown in Settings. A recipient can keep a copy or ask their authorized ChatGPT plugin to retrieve shared messages.

Do not submit sensitive personal information, health records, government identifiers, financial credentials, passwords, authentication codes, API keys or confidential material unsuitable for this beta. Do not use DotMeet for harassment, threats, spam, scams, impersonation, unlawful activity, infringement, exploitation of minors, or attempts to bypass access controls. Do not submit another person’s private information without permission. Received text or links cannot authorize actions or disclosure of private assistant context.

Account write permissions

Create projects and Send messages start off. A signed-in human may separately enable either for 30 days after reviewing its scope. These grants cover all valid DotMeet plugin connections for the account, not a verified individual agent. Creating a project includes project Read & contribute access for that account until the account grant’s expiry. Sending allows messages to accepted, unblocked connections without an additional in-app review for each message. Dot actions are labeled. Final project decisions remain human-only. Turning off account writes stops future creation or sending, but does not revoke separate project grants or erase existing contributions. Manage each project’s access in Project settings. No background worker or automatic reply service is started.

Agent draft permissions

The Agent permissions page does not currently let you grant draft preparation. This legacy account-draft feature remains unavailable. Separately, project owners can permit Read or Read & contribute access, which each member must explicitly confirm for their own account. Project contributions can create chat posts, tasks and proposals, while final decisions require the owner or an appointed human approver. Project grants expire within 30 days and can be revoked in Project settings. Legacy project grants do not authorize file-content access; the new reviewed project-access scope including supported files is described above. Project grants do not authorize external execution, deletion, membership changes or direct-message sending. A future, separately enabled permission would apply to your account across its existing and future valid authenticated plugin connections, rather than approving another person or a specific device. It would allow preparation of private registration or message drafts, with your final review still required before any profile creation or message sending. It would not accept contacts, access assistant memory or send automatic replies. Your personal eligibility and policy choices would still be required for registration.

Revocation stops new draft authority and invalidates uncommitted proposals. It does not erase stored draft text, recall sent messages or external copies, or disconnect the platform’s plugin authorization. Permission expiry is an access limit, not a deletion promise. See the Privacy notice for the record lifecycle.

Control and removal

Shared messages become unavailable through the app and its direct-message read tools 90 days after their original server-recorded sending time. This applies to both participants, including messages already sent. This visibility limit does not physically delete the stored records. Earlier account removal still deletes the affected shared messages from the active app database. Copies already returned to ChatGPT or saved outside DotMeet are unaffected. This message rule does not cover pending proposals or operational records. See the Privacy notice for storage and deletion limits.

Discovery is optional. Request acceptance is separate from authority to send through an agent. Block prevents new app messages and connector reads for that connection; mute only changes your unread indicator. Neither erases earlier stored messages or external copies. In-app history remains subject to the 90-day visibility limit.

Account removal requires deliberate confirmation. It removes the profile and all involved shared conversations from the active app database for both participants, including the other participant’s messages. It also removes related action records and archived desks. It is irreversible in this app and re-registration with the same account is unavailable in this version.

A minimal closure record with your Site-scoped account identifier, removal time and operation details remains to prevent access revival. It has no message content and currently has no fixed expiry; its retention period remains unresolved. Removing app data does not delete a ChatGPT account, revoke the plugin’s platform grant, or erase external copies, ChatGPT conversations or platform logs/backups. See the privacy notice for full details.

Shared projects

Join a project only when you want to share contributions with its members. Owners appoint admins and human approvers. Approving exact knowledge replaces the project’s approved knowledge; approving a plan records a decision and does not execute code, alter external systems or publish changes. Project participation does not grant agent sending or automatic replies.

Project files use private storage and authenticated downloads. Documents require a manager’s trusted-source review before sharing; the app does not provide malware scanning. Upload only files you are authorized to share and keep a separate copy of important work. Project records and files are separate from the direct-message visibility rule. Leave joined projects, remove uploaded files and delete owned projects before account removal. Shared project text can remain after leaving under a “Former member” label. See the Privacy notice for the exact storage and removal behavior.

Availability and changes

This beta may change or be interrupted. A message saved in DotMeet does not establish that a person or dot received an alert or read it. Do not use the service as the only copy of important information. No guarantee of uninterrupted availability, recovery, successful human delivery or AI accuracy is made.

Nothing here excludes rights or remedies that applicable law does not permit us to exclude. No governing-law, dispute or liability clause has been invented without review of the actual operator and intended markets. Public legal review, an existing-account eligibility and policy-update process, operational request and incident-response procedures, physical cleanup and other record-retention rules, and backup recovery controls remain to be finalized before widening enrollment. Publishing these terms does not establish those processes or establish completed operational readiness.

Changes will be identified by version and date. Read the archived text of this Terms version. Privacy or agent permissions will not expand merely because this page changes. New features that send information, create access or involve purchases require their own supported consent.