Protecting digital accounts and deliveries

Customer support does not need your card PIN, banking password, authenticator code, private key, or full recovery code. If a screenshot contains a secret, crop or cover it before sending. Use the protected delivery screen for values supplied with an order.

Be cautious when a message creates urgency and asks you to move payment, reveal a code, or install remote-control software. Return to the official Scrid order or support page instead of following an unexpected link.

Follow the product instructions in the stated order. If the listing permits password and recovery changes, complete them from a trusted device and save recovery information in a password manager. If changes are restricted, do not test unsupported settings that may lock the account.

Enable multi-factor authentication when the product allows the buyer to control it. Do not reuse a password from email, banking, social media, or another store.

Shared environments are not appropriate for confidential documents or private conversations. Sign out when finished on a public device, avoid saving payment details, and do not change global settings that affect other members.

If another member's action disrupts access, report it through the order instead of attempting to remove other users. The administrator can inspect the team or shared-delivery record.

Start support from the signed-in account or the contact options linked in the Scrid footer. Keep the case connected to the order whenever possible. Scrid may ask for an order or transaction reference, but it should not ask for the secret value needed to spend money or take over an account.

Review the address before signing in or revealing delivery information. The official storefront uses scrid.space, and order details should remain inside its authenticated account and support flows.