Operational support
Claim, login, product incidents and broken directory signals are routed here first.

Claim, legal, partnerships, or operational support routed to the right lane from the first message.
PINNY responds as infrastructure, with privacy and context first.
Claim, login, product incidents and broken directory signals are routed here first.
Copyright, privacy, compliance and formal takedown requests follow the legal workflow.
Integration proposals, press, B2B discussions and infrastructure licensing start here.
PINNY operates as a distributed infrastructure. While our systems are distributed globally, our core coordination team maintains 24/7 availability.
PINNY routes support, legal and partnership requests into separate handling lanes from the first message.
Clear links, screenshots and profile identifiers reduce manual follow-up time.
Links, screenshots and profile identifiers shorten manual review time.
PINNY does not publish a placeholder mailing office on this page. Use the correct channel above so the team can route your case to support, legal or partnerships without delay.
PINNY routes messages by function so operational support, legal matters and partnership requests do not get mixed into the same queue.

We collaborate with platforms, services and operators that fit PINNY's infrastructure model: visibility, tooling and creator sovereignty without taking a cut from peer-to-peer transactions.

PINNY handles contact intake as an infrastructure provider. Legal, privacy and copyright issues are documented carefully and routed into the appropriate workflow.
