Useful together. Safer by design.

Be deliberate about what you share

Onact actions are lightweight collaboration pages. Public actions can appear in Explore. Unlisted actions stay out of that directory, but their URLs can be forwarded. Neither setting should be used as a vault for sensitive data.

Understand the money boundary

A bill split estimates shares. A pledge records a non-binding intention. A product vote records a preference. None of those actions collect participant funds, buy products, guarantee discounts or verify a seller. Any external transaction requires separate checks and an agreed payment method.

Names and scores are not identity checks

Participants choose display names. Guest browser cookies help the tool remember a response; they do not verify who a person is. Challenge scores are self-reported and should not be treated as independently verified rankings.

Report content that crosses the line

Use the report control on an action to flag harassment, scams, personal information, unlawful material or misleading requests. Explain the issue so an administrator can review it. Reporting does not promise immediate removal or an emergency response.

Keep your account secure

Use a unique password. Keep recovery links private. Check that you are on the correct domain before signing in. Do not send account credentials through a group action or support message. If you suspect unauthorized access, reset your password and contact support.

Read our acceptable use rules and privacy notice. For a concern about an action or your account, contact the team.

Permissions belong on the server

Workspace access, ownership, role checks, plan features and quotas are enforced when a request reaches the backend. Hiding a button is not the only control. Private actions require membership, recipient-bound invitations expire, and a member’s personal plan does not grant permission to edit someone else’s workspace. Review roles when people join, leave or change responsibilities.

Guest ownership uses a browser identity rather than a display name. That supports casual participation but is not verified legal identity. A browser cookie can be lost or a session can be compromised. Use individual accounts, strong passwords and an authenticator for work that needs a stable identity, and avoid shared administrator credentials.

Data minimization in practical features

Receipt capture validates and canonicalizes accepted images. Optional retained copies are encrypted outside the public media library and expire after 24 hours; retention is off by default. Recognized text remains part of the browser review until you deliberately apply selected items to a bill. Public brand logos are a different media path and must never contain private documents.

Operational analytics avoids raw participant messages and raw IP storage. Optional public visits require consent and do not represent every visitor. The help assistant retrieves public source text without an external model. None of those design choices removes the need for an operator’s privacy policy, secure hosting and appropriate provider configuration.

Clear limits are part of a trustworthy request

A pledge is non-binding, a bill is a calculation, a product decision is a preference and a challenge score is self-reported. A calendar file does not reserve a venue. A paid-plan order is a separate transaction through the configured provider. Check claims that confuse those boundaries, particularly if someone asks you to transfer money or reveal account credentials.

Use the report control for inappropriate content or Contact for a case-specific safety concern. Give the page URL and observable issue without repeating private data. The platform is not an emergency channel, identity-verification service or guarantee of a merchant’s legitimacy. Real-world financial, legal and safety decisions need their own appropriate evidence.

Your next useful step

Read the product guides · Compare current plans · Contact Onact