# Games should be a place to have fun.

We want to enjoy building Summer, and we want people to enjoy playing here. Predatory behavior, serious abuse, illegal trade and financial abuse would destroy the place we are trying to make. We take that seriously.

- Competitive banter needs context.
- Chat safety and privacy both deserve a straight answer.
- People need a way to challenge mistakes.

Principles for how people play together.

[Read the Summer Engine privacy policy](https://www.summerengine.com/privacy)

## Protecting the experience is part of building it.

We are gamers ourselves. We have played in competitive WoW guilds and MOBAs, and we know how much a game and its community can mean to people. We want Summer to be a place we are proud to spend time in.

That means dealing with the things that can ruin it. Safety cannot be something we remember after the rest of the product is built. It belongs alongside the engine, the store and the ways people connect.

## Be clear about the abuse we are trying to stop.

Predatory behavior, exploitation, illegal trade, financial abuse and serious harassment are real concerns for a platform where people meet and money can change hands. Emerging misuse of AI adds problems that need continued attention.

We expect people to try to misuse the platform. The job is to take those attempts seriously, learn from them and improve protections. Claiming that abuse is impossible would give people the wrong reason to trust us.

## Competitive banter needs context.

Trash talk can be part of a competitive game. Friends joke with each other, and adults can choose experiences that are different from those appropriate for children. We do not want to flatten every conversation into the same rules of polite small talk.

Age, context and whether people actually welcome the interaction matter. Calling someone a friend does not make exploitation acceptable. A word or an automated score alone cannot explain every situation. Safety decisions need to distinguish the fun people came for from conduct that is harming someone.

## Parents need useful choices, and creators need to describe their games.

A game’s audience, content and ways of interacting should be understandable before someone starts playing. Creators have a responsibility to describe what happens in their game, including the experiences a parent or player may need to consider.

Parental controls should give families meaningful choices about what children can see and play. Games for adults and games for children need different treatment. That is part of making room for different audiences, rather than making the whole platform feel like a children’s toy.

## Chat safety and privacy both deserve a straight answer.

Communication helps people play together. It can also be used to approach someone with predatory intent, arrange illegal activity or move an abusive interaction elsewhere. Those are reasons to take chat safety seriously.

AI can help identify signals for review, but “AI-monitored” is not a complete explanation of how a system works. People deserve to understand what information is processed, who can access it, how it is retained and how decisions are made. Asking those privacy questions is reasonable. We do not treat a model’s output as proof that it cannot make mistakes.

## People need a way to challenge mistakes.

Safety decisions can be wrong. A person affected by a decision needs to understand the relevant reason and have a way to challenge it. Appeals matter especially when a system relies on automated signals.

Rules also need to account for applicable law and the context in which people play. We want to explain those responsibilities plainly, without turning the experience into a platform for policing people’s opinions.

## Help us get difficult decisions right.

These questions affect the kind of place Summer becomes. We want feedback from players, parents, creators and people who work on safety, privacy and abuse prevention. If you see a problem or want to contribute to that work, contact [founders@summerengine.com](mailto:founders@summerengine.com).

The Summer Engine terms and privacy policy describe the Engine service. They do not replace the specific rules and explanations needed for Summer Games, its social features or the creator program.

- [Summer Engine privacy policy](https://www.summerengine.com/privacy)
- [Summer Engine terms](https://www.summerengine.com/terms)
- [The values behind these choices](https://www.summerengine.com/values)

## Make the experience clear before people join.

When you share a game, explain its content, intended audience and how people interact. That introduction is part of looking after the players who arrive.

[Read about publishing and player expectations](https://www.summerengine.com/publishing)

## Keep exploring

- [Our values](https://www.summerengine.com/values)

- [AI transparency](https://www.summerengine.com/ai-transparency)

- [Publish a game](https://www.summerengine.com/publishing)

[Page map](https://www.summerengine.com/page-map)

[Summer Engine — Terms of service](https://www.summerengine.com/terms)

[Summer Engine — Privacy policy](https://www.summerengine.com/privacy)

[Summer Engine — Refund policy](https://www.summerengine.com/refunds)

[Source and licensing](https://www.summerengine.com/source-status)

Canonical: https://www.summerengine.com/safety

Language: en

[Read as Markdown](https://www.summerengine.com/safety/content.md)