Gig and platform work
An account suspended or deactivated on a work platform
Goal: organize the notice and the documents for the platform's appeal.
The problem
An account is suspended or deactivated, cutting off income and access to earnings history, ratings, messages or the reasons given.
Check the appeal deadline and channel. Keep the notice, any export and the reference number. Keep the lawfully preserved original separate from a copy with customer data redacted, and note which file matches the hash.
People who work through apps depend on information stored by the platform: how much they earned each week, their customer rating, the warnings they received, the support team's replies. When the account is suspended or deactivated, access to all of it is usually cut at the same moment. To ask for a review or explain their track record, the person is left without the numbers or the messages.
This use case isn't for registering your account every day. It makes sense when a warning, a strange drop in ratings or another concrete sign of risk appears.
What to preserve
Earnings and rating history, notifications, messages and relevant documents while they are still accessible.
Goal: organize the notice and the documents for the platform's appeal.
Main file: the notice, any available export and the reference number.
When to capture: when you receive the notice, within the appeal deadline.
Supporting sources: the platform's rules and its appeal channel.
Limit of this scenario: on its own, the Record does not establish that the suspension was unfair or that you are entitled to reactivation.
Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.
If the platform lets you export statements or reports, prefer those files. Where there is no export, take full screenshots with the date visible. Save warning notifications, conversations with support and any explanation you received. Where lawful, create a derived copy with customer data redacted, separate from the original, and note which version you registered.
How Provenia documents this scenario
Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.
Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.
Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.
Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.
In this scenario, use the notice, any available export and the reference number as your reference material and check it against the platform's rules and its appeal channel. The timestamp on a hash does not confirm that the suspension was unfair or that you are entitled to reactivation.
Step by step
- Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
- Check the appeal deadline and channel. Keep the notice, any export and the reference number. Keep the lawfully preserved original separate from a copy with customer data redacted, and note which file matches the hash.
- Preserve the notice, any available export and the reference number exactly as it is; don't edit the file you register.
- Link the material to the platform's rules and its appeal channel; describe its origin and when it was captured as declared information.
- Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.
What the Record shows and what it does not
A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish that the suspension was unfair or that you are entitled to reactivation. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
My account is already suspended. Is it still worth it?
Yes, for whatever you can still access, such as saved emails and notifications. Ideally, register when the first warning signs appear.
How should I organize the files for this case?
Put the suspension notice first, then the exports or screenshots of earnings and ratings, then your appeal and the platform's reply. Register the original files; if you need a copy without customer names, make it a separate file and say which one you registered.
Which date is certified?
Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.
Official references
Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.
Already have an account? Log in.