Privacy requests
Where should privacy requests go?
Use the public or tenant privacy request form. Do not send secrets, OTPs, card data, private links, or full documents in free-text support fields. The tenant-routed form is still public and does not sign you in or confirm a customer record. Complete bot verification, or use the published email link when verification is unavailable. A successful submission intentionally shows no public request ID and does not promise deletion, fulfillment, an outcome, or a response deadline.
How should restricted delete or retention actions be handled?
Use the compliance request retention workflow. Record a retention plan, target safety check, blockers, and action notes before any restriction, soft delete, or anonymization. Immutable records such as audit logs, payment callbacks, invoice payments, inventory ledgers, generated artifact versions, and ownership history should not be silently rewritten.
Why is a retention target marked manual or unsupported?
Motornauts only completes target/action pairs with a verified service handler. Generic soft delete, restriction, provider-account deletion, unsupported object targets, a tenant-scoped change to the shared customer profile, and standalone notification-attempt/SMS/email anonymization remain blocked. Approved vehicle-document, inspection-media, and generated-artifact deletion is asynchronous: it stays Executing until primary storage absence is verified. Supported deletion and anonymization handlers commit source state, action, and sanitized audit evidence together; if finalization fails, no completed action is kept.
Why does a retention target show an active legal hold?
An executed legal-hold action protects that exact tenant and target across retention plans. New destructive plans are blocked, and execution rechecks the hold inside the same locked transaction. Use the approved hold-release action only when the hold is genuinely ready to close; repeating a release does not create a second release or audit event. A hold or release is workflow evidence, not proof that provider copies or backups were physically deleted.
After a valid release, refresh the request and run a new safety check before using a plan that was previously blocked. Motornauts does not silently clear stored blockers or reuse old safety evidence.
Why can an access export not be marked ready?
Ready exports require a verified durable subject link and the exact categories approved in the access fulfillment. Motornauts currently projects the compliance request and its safe event history. Broader customer, workshop, fleet, staff-activity, payment, document/media, and service-history categories stay review-needed rather than producing a partial bundle that looks complete.