What CrewPulse actually does with your data

Nobody sees your individual score. Not your CTO, not your manager. Every check-in you submit is tied to your account in the database (your CTO needs to see trends for the team, which requires real data), but by the time that data reaches any screen or email a human looks at, it has already been averaged across your whole team. The API response your CTO's dashboard renders from contains team-level numbers only: averages, response counts, week-over-week deltas. There is no field, no endpoint, no admin view anywhere in the product that returns one engineer's individual score. Managers see the same shape of data as CTOs, just scoped to their own team, not a more detailed view.

Your free-text note goes further: it's not just aggregated away, it's structurally unlinkable. Your note is stored in a separate database table from your check-in scores, and that table has no column connecting a note back to an engineer, only which team and week it belongs to. This isn't a display-layer filter that could have a bug in it; the link doesn't exist in the schema. Your CTO never sees raw note text, only an AI-generated summary of themes across your team's notes for the week. That summary is generated by sending Anthropic's API just two things: your team's name and the raw text of that week's notes, never your name, email, or any other account identifier. Anthropic has no way to link a note back to you even if it wanted to, since that link doesn't exist in our own database either. If fewer than 2 people on your team submitted a note, no summary is generated at all.

Questions about this? Email hello@crewpulse.io.