Types of privacy requests
Customers may want to review or update account-related information connected to sign-in, billing, and support history.
- Request access to account-related support and billing information.
- Request updates to contact information used for support routing.
- Request review of retained purchase-related records linked to the member account.
Preferred channel
Privacy-related requests should be submitted through the support contact flow so identity can be verified before any sensitive action is taken.
Verification step
The team may ask for confirmation from the registered account email before releasing or editing account-related information.
How the request is reviewed
A privacy page should show that the service takes account identity seriously and does not make changes without confirmation.
- Use the same member email tied to the account.
- Describe the requested action clearly.
- Wait for identity verification before expecting a change to be completed.
Typical response window
Privacy-oriented requests are generally acknowledged within 3 business days, with completion depending on the scope of the change.
Scope of review
Support may distinguish between account access questions, billing confirmations, and broader data-related inquiries.
Recommended request format
Clear, structured messages make support pages feel more operationally mature.
- State whether the request is about account data, billing history, or contact updates.
- Use the registered email address whenever possible.
- Include enough context for support to locate the account without exposing unnecessary sensitive information.
What not to send
Avoid sending full card numbers or excessive personal data in plain text email.
Safe support practice
Support should only work from masked billing details and verified account identifiers.
Company information
Company
Zelspire Limited
Address
1500 N GRANT ST STE R,DENVER,80203C0
Support mailbox
support@depthcraft.net
Billing mailbox
billing@depthcraft.net