What is held, what is refused
The strongest privacy policy is a short list of what was never collected. This desk's list is deliberately short, and this page is the whole of it.
Held: what you send about your course, the work produced for you, and the contact address you chose. Refused by design: your Walden password, your student ID number, and your payment card details, which live with the payment processor and never touch the desk. Everything held is deleted on request.
The three refusals
No arrangement here ever requires your Walden login, and the desk will not accept it if offered, because holding it converts a writing service into an account intrusion and you into the person who handed over the key. Your student ID number is never requested for the same reason: the desk needs your course, not your identity in Walden's systems. And card details go to the payment processor directly, so there is nothing here to breach. If a message claiming to be this desk asks for any of the three, it is not this desk; close it and say so through the chat panel.
What is held, and for how long
Your course thread. Prompts, rubrics, dates and the conversation itself, kept while the arrangement runs so week nine can be consistent with week two.
The delivered work. Kept through your term for revisions and resends, then removed in routine cleanup rather than archived forever.
One contact route. The email or number you gave, used to reach you about your work and for no other purpose. No lists, no partners, no drip campaigns.
Ordinary technical traces. The chat panel keeps a visitor token in your browser so conversations survive a reload; server logs record requests as every website's do.
Deletion, on your word
Ask in the thread or through the chat panel and the thread, files and contact route are removed. No reason required, no retention argument, no export ceremony beyond sending you anything you want to keep first. People in this market often want no trace of the arrangement afterward; the desk considers that a reasonable wish and honors it as the default expectation rather than an awkward request.
Questions, answered
Will anyone ever know I used this service?
Not from this side. The desk does not name clients, does not keep testimonials with identities, and deletes threads on request. Your own devices and habits are the only part outside its control.
Why do you refuse logins even when offered?
Because holding a login makes every future dispute unwinnable for you and converts the service into something neither of us should want it to be. The refusal protects both sides, and it is permanent.
Where do payments actually happen?
With the payment processor, on their infrastructure. The desk sees that a payment cleared, never the card that made it.