Terms of Service

The Agreement and available capabilities

You accept the version of these terms and the Privacy Policy offered when you create an account. Both documents show the same Agreement version. Joining a Workspace or Task, claiming recipient access, or continuing to use Miindy does not by itself accept a different version.

Capabilities are released in stages. Task access, public identity, named-recipient sharing, Standing and credentials, the audit log, and account deletion described here are currently restricted to designated test accounts. Security enforcement and its contest route can apply to any affected account. Accepting the Agreement does not make an unavailable capability available.

Current Task and sharing capabilities establish ownership, permissions, identity, and access records. Task content editing, discussion, revisions, branches, independent copies and change proposals, source processing, Personal libraries, and publication content, evidence, comments and downloads are unavailable in this release. Content-bearing visibility changes, ownership transfer, and Task deletion also await their complete lifecycle controls. Their audience and rights boundaries below do not promise those working features. Customer source processing requires its own qualified release.

Your account

You represent that you are at least 18 years old, or the age of majority where you live if higher, and have legal capacity to accept this Agreement. Ordinary participation requires no occupation, professional credential, client relationship, or Workspace. Adult students and practitioners in any field use the same account rules.

Each account belongs to one person. Keep your password and second-factor codes private, use your own account, and report suspected unauthorized use promptly. You are responsible for actions you authorize through your account. Verifying an email demonstrates control of that mailbox; it does not verify legal identity or professional qualifications.

Personal ownership and Workspace governance

A Task is owned by one person or one Workspace. The personal owner retains ultimate control when collaborators join. A Workspace is deliberately created for group ownership, including client engagements, project teams, research groups, and communities of practice. Workspace work stays with the Workspace when its Members change.

Workspace Owners have equal ultimate authority, including inspecting and editing every Task their Workspace owns, even a Task restricted from ordinary Members. A continuing Workspace must have at least one Owner. Members can create private Workspace Tasks under the Owners' creation policy and become their Task Admins. Membership alone does not open every private Task.

Ownership here describes control within Miindy. It supplies no missing copyright, source rights, confidentiality permission, publication authority, or authority to spend another person's funds. You must have authority for the material and uses you authorize, including access you give others.

Task roles and audiences

Task roles are separate from Workspace roles. Viewers have reading authority; Commenters can also discuss and propose changes; Editors can edit; Admins can also manage collaborators, including other Admins, and ordinary settings within owner policy. Visibility changes, ownership transfer, deletion, and publication require the ultimate owner or an explicit delegation of the particular power. Delegates cannot enlarge their own authority or remove the ultimate owner. A delegation alone grants no access to a private Task.

A private Task admits its owner, named collaborators, and any explicitly selected all-Workspace-members audience. Outside collaborators receive Task access without Workspace membership. A Task grant opens no membership directory, private email, unrelated Task, private affiliation, or Personal library. Access to two client Tasks does not authorize combining their private material.

A public Task admits anonymous readers and, subject to applicable restrictions, signed-in discussion and proposals. Direct editing requires an editing role or ownership. When content features are available, public Task work, discussion, Work products, and revisions share that public audience. Private drafting requires a separate private Task. Branches keep their Task's owner and audience; independently owned copies have their own audience and retain applicable source and attribution conditions. Public availability does not automatically publish a contribution to Miindy's public knowledge graph or supply a reuse licence.

One identity and permanent handles

You choose one account name and avatar for the contexts allowed to see you. Your name may be a pseudonym and may be changed. A Profile and handle reservation are created with the account without publishing a public Profile. Public participation and public Task ownership disclose the identity attached to that work; optional biography and self-described affiliation remain your publication choices.

People and Workspaces reserve handles from one shared namespace. Renames preserve stable ownership and authorship. A retired handle stays reserved to its holder permanently, including after deletion, and only that holder can readopt it where the account or Workspace remains eligible. Renames are limited to once every seven days. A retired address redirects to a public destination only by the holder's deliberate choice. Earlier names are not automatically listed as a history. Hosted attribution uses your current permitted name; previously downloaded copies retain their contents.

Named-recipient access

A named recipient signs in free to claim a share without creating a Workspace or receiving private Task access. A grant issued to an identified account is claimable only by that account; otherwise the claimant must control the addressed verified email. The valid link secret is also required. Forwarding a link does not authorize another account. Claimed access follows the same account through verified email changes; a new account using an old email inherits nothing.

Unclaimed grants expire after 30 days. Authorized publishers can revoke grants or reissue pending or expired grants, invalidating the earlier link. Claimed access is not ended by the unclaimed-link expiry. Revocation ends subsequent hosted access when it takes effect. The share's declared common audience sees recognizable names and relationships. Publication content and any commenting or downloading remain bounded by the particular share when those features are available. Hosted revocation cannot recall downloaded copies.

Leaving a Workspace

Leaving or being removed ends Workspace authority and access inherited from all-members Task audiences. Direct working grants on that Workspace's Tasks end by default. An Owner removing another Member can deliberately retain selected Tasks at selected outside-collaborator roles in the same action; this retains neither Workspace ownership authority nor removed delegations. Voluntary departure ends working grants; a remaining Owner can separately grant outside access.

Recipient grants survive departure by default and appear separately in the preview. An Owner removing another Member may keep them, revoke selected grants, or revoke all applicable recipient grants from that Workspace in the same action. Voluntary departure keeps recipient grants. Other owners' grants remain outside this action.

Readmission uses current audiences and new admission authority without silently reviving ended direct Task grants. Departure leaves personal Tasks, other owners' work, permitted independent copies, public identity, and unrelated public participation governed by their own rules. Public reading and lawful historical attribution retain their existing conditions.

Attribution, Standing, and credentials

You can grant standing permission for truthful attribution broadly or for a Workspace or Task, including outside collaboration. Applicable denials and narrower choices limit that permission. Covered uses reuse it; missing permission requires your own identity choice. Another owner cannot supply that choice for you. Attribution permission supplies no editorial role or material rights. Narrowing, denying, or revoking permission applies to future uses; earlier authorized uses retain their evidence and remain subject to erasure and applicable obligations.

Standing statements are optional, scoped claims with a recorded basis and retained versions. Credential records distinguish your claim, correspondence with an issuer's record, association with your account, and stated currency. Recording a credential leaves its association with you unconfirmed. Issuer correspondence checking is unavailable in this release; supplying a reference performs no check. Expiry, withdrawal, and unavailable evidence have distinct meanings. Miindy grants no expert status, reputation score, role, or access merely because a credential or statement is recorded.

Authority to process and disclose

For available capabilities, you authorize Miindy to store, process, and display information you submit as needed to carry out your intentional actions within their permitted scope. Routine covered work reuses this Agreement and saved permissions. Your authorization extends only to uses you have authority to permit; known source restrictions, confidentiality duties, and others' rights remain effective. Ownership and collaboration alone do not authorize disclosure beyond the selected audience.

A processing use requiring additional coverage is offered within its first affected action, with its purpose, scope, version, and text. You affirmatively accept that offered version with the action; acceptance is reused for covered actions in that scope. Declining leaves unrelated covered work available. Credential evidence has such a separate offer. Accepting these terms alone does not accept that offer.

Private source material, inputs, and outputs are not licensed by ordinary use for training Miindy's or providers' models or for Miindy's evaluation corpus. An evaluation contribution requires a separate intentional, authorized selection and applicable terms. Material processing, copying, publication, and removal features must enforce their source and audience conditions before release.

Enforcement and contest

A public suspension restricts the specified publication or review rights while preserving otherwise authorized private work and recipient access. A separate security hold ends sessions and blocks sign-in and ordinary access until lifted. Enforcement has a recorded reason and a contest route, including an email-based route to contest a hold without an ordinary session.

Restoration records the change; affected review eligibility requires explicit reassessment. It does not silently restore ended grants or rewrite historical assessments. A report, erasure request, or account deletion is not itself a finding of misconduct or a judgment about the correctness of someone's work.

Erasure, deletion, and recovery

Attribution erasure permanently unlinks public identity, removes published details and existing identifying Standing and credential records, including private records and their versions, and retires handles without redirects. Lawful remaining references display neutral attribution. Your login and private account identity, Memberships, Tasks, and grants remain. You may later record private Standing or credentials, but cannot reestablish public identity. Necessary permission and assent evidence follows the restricted retention in the Privacy Policy. Erasure does not delete another owner's work or revoke rights in independently authorized copies.

Account deletion previews its effects and refuses completion while you own personal Tasks requiring disposition or are the final Owner of a continuing Workspace. Another Member can be promoted to Owner, or a Workspace can be deleted where governed deletion is available. Disposition of personal Tasks is unavailable in this release, so owning one prevents account deletion until supported transfer or deletion is available.

Once responsibilities are resolved, deletion ends sessions and credentials, Memberships, Task grants, and claimed recipient grants, applies erasure, and replaces account identity fields with a deletion record. Stable references and permanent handle reservations remain. A new account at the former email inherits no ownership, access, or attribution. Workspace work remains under current Owners. Recovery must reapply recorded erasure, deletion, and current restrictions before restored data is served. Deletion does not recall downloads or complete unavailable Task or Personal library content-removal operations.

Changes to the Agreement

A material change receives a new version, which Miindy asks you to review and explicitly accept. We record the version actually offered and your acceptance time. If the offer changes before acceptance, you must review the current version. Unrelated work covered by your existing Agreement remains available; an uncovered processing use waits for its applicable acceptance. Merely visiting, continuing work, or joining a Task or Workspace records no new acceptance.