Support
Contact MINT for support, defects, privacy questions, or data-deletion requests. Never send a password, OTP, reviewer code, token, cookie, authorization code, raw header, or raw body.
Contact
We normally respond within two business days. Support hours are weekdays, 10:00–18:00 Japan time.
Frequently asked questions
Does MINT publish automatically?
No. A Threads text post is published only after Preview, DryRun, an immutable ActionRequest, explicit Approval by an authorized human, and a final runtime gate. An immediate plan also requires the user's separate Publish action. A scheduled plan is authorized for the displayed due time by that explicit Approval; creating the schedule has no provider side effect, and the worker re-checks every gate when it becomes due. AI/LLM can suggest a draft but cannot approve or call the provider.
Which provider and permissions are real?
Threads is the only real provider. The approved threads_basic permission is used for the connected user's own profile/posts read-only. This new review campaign uses threads_content_publish only for an explicitly approved text post. MINT neither requests nor executes reply, delete, edit, insights, search, location, or media permissions. Facebook and Instagram are static, not-connected mocks.
How do I connect Threads for publishing?
On Account Connections, choose Connect Threads for Publishing and review the exact permissions shown by Threads. The separate Threads Basic (read-only) path is for the already approved read-only use.
What does Disconnect Threads from MINT do?
It removes MINT's local proof/snapshot, encrypted publishing credential, and saved grants, and causes scheduled work to fail closed. It does not make a provider revoke call or remove MINT from Threads Website permissions. Remove that authorization separately in Threads settings when appropriate.
How do I request data deletion?
The Data Deletion Instructions accurately describe signed Threads provider-account deletion and the support process for a broader MINT data request. MINT does not currently claim a self-service whole-user/workspace deletion button.
How does MINT prevent duplicates?
MINT uses durable idempotency, execution leases, bounded retry, stored container state, and a last-moment permission check. An ambiguous create or publish is never recreated blindly; it is quarantined as a terminal unknown outcome for manual review, with no automated provider GET or publish retry. Only a confirmed post's missing View link uses bounded read-only recovery.
What does AI assistance do?
It can suggest draft copy, tone, and content checks. A human decides whether to accept, edit, reject, approve, and publish it. There is no direct AI-to-provider posting route.