Privacy Policy

Who this applies to

Glitchpost is a business-to-business tool used by game development teams. The people whose data we handle are members of those teams — the workspace owner, and anyone they invite or equip with a reporting build. We do not sell data, we do not run advertising, and we do not build profiles for any purpose other than operating the service.

What we collect

Account data. When you sign in with Google we receive your name, email address and profile picture, and we store an authentication session so you stay signed in. We never receive or store your Google password.

Report content. Everything your team attaches to a report: the written description and comments, severity and category, screenshots, gameplay recordings, log files, and technical metadata sent by the build — such as the device model, operating system, build version, and the identifier or nickname of the reporter.

Workspace configuration. Project names, invitations, destination settings (spreadsheet and channel targets, column mappings, routing rules) and the access tokens needed to write to those destinations on your behalf.

Operational data. Server logs, error traces and basic usage counters (for example, how many reports a workspace has published) used to keep the service running and to apply plan limits.

Google account data

Signing in with Google is optional in the sense that it is the only sign-in method we offer, but the additional access we ask for is granted separately and only when you connect a destination. When you connect Google Sheets we request permission to create and edit spreadsheets and to access the files you pick, so that a published report can be written as a row and its attachments placed in the folder you choose.

We use that access only to perform actions you asked for in the app. We do not read unrelated files, we do not use Google user data to train machine learning models, and we do not transfer it to third parties except as described below. You can revoke our access at any time from your Google Account permissions page; doing so stops publishing to Google destinations immediately.

How we use the data

• To accept reports from your builds and show them on the realtime board.
• To store attachments and serve them back to your team through time-limited links.
• To publish a report to the destination you selected — a spreadsheet row, a Slack message, or another connected tracker.
• To generate optional AI assistance: transcribing voice notes and drafting report descriptions or titles when you ask for it.
• To authenticate users, enforce workspace membership, and apply the limits of your plan.
• To diagnose failures, prevent abuse, and comply with legal obligations.

Where the data goes

Glitchpost is a middle point by design: report data leaves us when you publish it. The services we rely on are:

• Google — sign-in, and Sheets and Drive when connected as a destination for report rows and attachments.
• Slack — when connected, report summaries and attachment links are posted to the channel you choose.
• Amazon Web Services — hosting, object storage for attachments, and transactional email such as workspace invitations.
• OpenAI — only for the optional AI features. Audio or text you submit for transcription or drafting is sent for processing and is not used to train models.

Beyond these, we disclose data only when required by law, or when necessary to protect the rights and safety of our users and the service. If Glitchpost is ever acquired or merged, data may transfer to the successor under this same policy until it is replaced with notice.

Retention and deletion

Reports and their attachments stay in your workspace until someone deletes them or the workspace itself is deleted. Published copies that already reached your spreadsheet, Slack channel or tracker are outside our control — they live under your account there, and deleting a report in Glitchpost does not remove them.

When a workspace is deleted, its reports, attachments and destination tokens are removed from our active systems within 30 days. Backups roll off shortly after. Operational logs are kept for a short, rolling window for security and debugging.

Security

Traffic to and from Glitchpost is encrypted in transit. Attachments are stored in private object storage and exposed only through short-lived, signed links; they are not publicly browsable. Destination access tokens are stored server-side and are never exposed to the browser. Access to production systems is limited to the people who operate the service.

No system is perfect. If we discover a breach affecting your data, we will notify affected workspace owners without undue delay and describe what happened and what we did about it.

Your choices and rights

• Access — you can view every report and attachment in your workspace from the app.
• Correction — report content, comments and settings are editable in place.
• Deletion — you can delete individual reports, or ask us to delete your account and workspace entirely.
• Export — ask us and we will provide your workspace data in a machine-readable format.
• Withdrawal — revoking Google or Slack access disconnects those destinations without affecting the reports already in Glitchpost.

Depending on where you live, you may have additional rights under laws such as the GDPR or the CCPA. Write to us and we will honor them.

Children

Glitchpost is a professional tool and is not directed at children. We do not knowingly collect data from anyone under 16.

Changes to this policy

We will update this page when the service changes. Material changes are announced to workspace owners by email before they take effect, and the date at the top of this page always reflects the current version.

Contact

Questions, requests or complaints about privacy go to privacy@glitchpost.dev. We answer every message and aim to resolve requests within 30 days.