Pergunta Me
ChatGPT app support and review details
This page is the operator-facing reference for the Pergunta Me ChatGPT app. It summarizes the review-only access path, declared data handling boundaries, and the contact points used during OpenAI review and post-launch support.
Support contact
[email protected]Reviewer operations contact
[email protected]Connect and try Pergunta Me in ChatGPT
Use this path when you want ChatGPT to capture, list, update, or complete tasks in your Pergunta Me account. The first useful action is capture; planning and review can come after tasks exist.
Setup steps
- Sign in to Pergunta Me and accept the required legal acknowledgments.
- Approve access, then return to ChatGPT.
- Start with one capture prompt before trying planning, review, or advanced tools.
First prompts
- Capture these tasks: send the invoice, book the dentist, renew the passport.
- What should I do today?
- Make this task actionable.
- Review what is stuck.
ChatGPT app privacy summary
This page supplements the canonical Pergunta Me privacy and terms notices with the ChatGPT-specific operational details that OpenAI reviewers and support operators need to verify.
Data categories and purposes
- Tasks, comments, and daily planning records from the linked Pergunta Me account.
- Authentication and consent state needed to prove the user can access the connected account.
- Launch-critical operational telemetry such as auth outcomes, tool failures, and latency without raw task-body analytics.
Processors and recipients
- Pergunta Me operators and self-hosted infrastructure process account data to deliver the task and planning flows.
- Supabase Auth verifies account identity and session state for the connected user.
- OpenAI and ChatGPT process prompts, tool calls, and widget rendering needed to operate the ChatGPT app experience.
User controls and rights
- Users can disconnect the app by revoking access from the ChatGPT/OpenAI side and by signing out of Pergunta Me.
- Users keep access to export and account-deletion controls through the Pergunta Me privacy settings and GDPR routes.
- Required legal acknowledgments remain enforced before MCP or app access resumes after a legal-version change.
Review operations
- The hidden reviewer path is configured through `NEXT_PUBLIC_ENABLE_REVIEWER_PASSWORD_AUTH` and `NEXT_PUBLIC_REVIEWER_AUTH_PATH`.
- Reviewer access is limited to the allowlist in `REVIEWER_AUTH_ALLOWED_EMAILS`.
- OAuth review and production callbacks must both remain allowlisted in Supabase Auth.
- MCP protected-resource metadata is published from the public API origin and linked from the `WWW-Authenticate` challenge.
- Focus tools and focus screenshots remain outside the ChatGPT app scope.
- Public users stay on Google-first auth. A hidden reviewer-only password path exists only during the review window and is disabled afterwards.
- The shared reviewer account may be reset between review attempts so screenshots, prompts, and tool responses stay deterministic.
- Runtime metrics avoid raw task-content analytics. Per-user launch funnel analysis relies on existing MCP audit rows under controlled operator access.
Reauthenticate in ChatGPT
- If Pergunta Me starts failing after a session expires, use the sign-in or reconnect action that ChatGPT shows for the app and then retry the request.
- If ChatGPT does not surface a reconnect button, open ChatGPT Settings, find Pergunta Me in Apps, and reconnect it there before retrying.
- MCP authentication failures publish a standards-based `WWW-Authenticate` challenge and link back to this support page through protected-resource metadata so reconnect guidance stays discoverable.
Canonical legal notices
Canonical privacy, cookie, and terms notices live on pergunta.me and remain the source of truth for declared processing and user rights. This ChatGPT support page is the operational supplement for review routing, recipients, and launch-era controls.