PETLoves Open web app

PETLoves Support

Help with PETLoves accounts, privacy requests, safety reports and services.

Text revision: 2026-09-08

PETLoves support helps users and reviewers understand the app, diagnose issues, report safety concerns and request privacy guidance.

Contact

Email: support@petloves.it

Include device type, app version, operating system, account role, release candidate ID if visible and a short description of the issue. Do not send sensitive pet health information unless it is necessary for the request.

Common topics

Safety and moderation requests

Use support@petloves.it to report abuse, unsafe content, privacy exposure, animal welfare concerns, fake professional claims, fake reviews or suspicious sponsor behavior. Include links, screenshots or context when safe to do so.

Support classifies reports by priority. Critical cases include threats, private data exposure, animal cruelty, dangerous health advice and repeated harassment. PETLoves may hide content, suspend sponsored visibility, limit account features, block abusive interactions or escalate to Trust & Safety.

Blocking and unwanted contact

Users should be able to report unwanted contact and block or limit abusive users when backend accounts are active. Blocking should reduce direct messages, tags, comments and repeated contact from the blocked account. Severe abuse is escalated to Trust & Safety.

Privacy requests

For privacy questions, export guidance, data reset, account deletion or content deletion guidance, contact support@petloves.it. The app supports data reset, and production backend accounts must provide a server-side account and data deletion process.

Backup and data restoration

The app can export a snapshot and support bundle where enabled. Public backend services require encrypted backup, restore testing and a data-loss incident path before PETLoves stores cloud data at scale.

Diagnostic bundle

PETLoves can prepare a Diagnostic bundle from the Profile area. The bundle is designed to include release state, permission status, diagnostics and QA context while avoiding unnecessary personal data. The user chooses whether to share it.

Response expectations

Public launch requires confirmed inbox ownership, escalation owners and response expectations for privacy, safety, booking, professional marketplace, media, live sync and store review issues. Critical safety and privacy reports should be triaged first.

Back to PETLoves