Legal
Terms and Acceptable Use
Effective date: June 7, 2026
These Terms and Acceptable Use rules explain the baseline rules for private challenge journeys in SideMissions.
Who operates the app
SideMissions is operated by the app operator named in the production store listing. The final legal name, postal address, and support contact must be completed before public release.
Private journeys
Journeys are intended for private groups. Invite codes should only be shared with people you want to join the same journey.
Members of a journey can see journey details, challenges, progress, recap material, and proof media according to the app's current visibility rules.
Your content
You are responsible for the challenge text, proof descriptions, photos, and videos that you create or upload.
Only upload media when you have the right to do so and when the people shown are comfortable with that use.
Acceptable use
Do not create, upload, or share illegal content, sexual content involving minors, threats, harassment, hate, violence, non-consensual intimate content, private data of others without permission, malware, spam, or content that encourages dangerous or unlawful behavior.
Do not use SideMissions to impersonate others, deceive participants, bypass security, or access journeys that you were not invited to join.
Host and participant controls
Hosts can delete journeys and manage journey settings. Participants can leave journeys from the app.
Production moderation and support contacts must be finalized before public launch so users can report unsafe content or behavior.
Service limits
The app may limit media count, size, duration, file type, invite behavior, or access when needed for reliability, privacy, safety, or security.
Development builds are not intended for real external users and may use temporary storage or testing infrastructure.
No emergency or safety service
SideMissions is for social challenge journeys and recaps. It is not an emergency, location safety, or travel risk service.
Changes
These terms may be updated when the product, backend, moderation process, store requirements, or legal requirements change.