Policies
Generic Alpha drafts · v0.25.1 · Updated 7 October 2026. These documents require the operator's identity, contact details, hosting locations, applicable business terms and legal review before public launch. They do not certify compliance or create a live paid offer.
Terms of Service — Draft
Operator: [legal business name and address]. Support: [contact email]. Effective date: [confirm before launch].
RAIDPOINT is an independent team workspace for Rust. Steam sign-in verifies your identity; the workspace owner controls membership, feature access and Rust+ pairing. You must have permission to use the connected account and server information. Keep credentials private and report suspected unauthorized access.
This Alpha provides experimental tools. Rust+ availability, server behavior and third-party services can affect live features. Stored observations can be incomplete; verify important game decisions. RAIDPOINT is not affiliated with Facepunch, Steam or the third-party sites linked from the app.
Stripe checkout is currently for testing. Before accepting live payments, the operator must publish accurate pricing, renewal, cancellation, refund, tax and subscription terms. Nothing in this draft limits mandatory consumer rights. Governing law, dispute processes, service commitments and responsibility limits must be reviewed for the operator's actual business and intended markets.
Privacy Policy — Draft
Data controller: [operator name, address and contact]. Privacy contact: [email]. The operator must document purposes and lawful bases for each processing activity, data recipients, hosting countries and any international transfer safeguards.
The workspace can store Steam identifiers and profile information, access permissions, account security and session records, supported Rust+ team observations, captured chat, objectives, notes, uploaded planning images, feedback and billing references. Pairing credentials and private base codes must not be included in feedback. Owners should restrict access to sensitive team information.
Information is used to operate the workspace, authenticate users, enforce access, provide requested team features and diagnose failures. Steam, configured Discord integrations and Stripe test services may receive information needed for their functions. The operator must identify actual hosting and other processors before launch.
Retention depends on configured features. Movement retention defaults to 30 days; supported deleted planning records remain in the recycle bin for 90 days unless permanently deleted earlier. Captured chat persists until the operator's documented retention or deletion process removes it. Other account, audit and billing retention periods must be disclosed for the actual deployment. See the deployment's Alpha privacy notice and Privacy & My Data for available request tools.
Contact the operator to ask about access, correction, deletion, portability, objections or restrictions where applicable. Requests can require identity verification. The operator must explain relevant supervisory-authority complaint rights and disclose any applicable exceptions or required records. [Add jurisdiction-specific contacts and procedures before launch.]
Acceptable Use — Draft
Use accounts and game information only with authorization. Do not impersonate others, bypass access controls, publish pairing secrets or private codes, harass teammates, upload unlawful content, or use automation to spam chat or Discord. Follow the connected server's rules and relevant service terms.
Workspace owners may restrict or disable access. Report suspected misuse through the configured support contact. The operator must publish fair reporting, review and appeal procedures before public launch. [Add operator contact and applicable escalation processes.]