Privacy Policy

This policy describes how A-Zing Innovations handles data when you use DevCentra™ (web, desktop, and mobile). It supplements the A-Zing platform Privacy Policy for your account.

1. A-Zing authentication and Wallet

DevCentra does not have a separate login or credit currency. Authentication and the Wallet are from A-Zing and are used on DevCentra and other A-Zing-owned products. Your A-Zing identity, login, and wallet balance are platform data; DevCentra uses them to sign you in, show your balance, and debit credits for access. See the A-Zing Privacy Policy (Shared A-Zing Account, Authentication & Credits).

APICentra also uses the same Wallet, but APICentra call packs are not DevCentra ETOW day passes. One wallet credit reserves 50 APICentra calls when you reserve them from Access or when APICentra auto-reserves.

Share to Care peer transfers of Wallet credits are operated by A-Zing (sender, recipient email, amount, timestamp). DevCentra surfaces the same Wallet balance; it does not run a separate transfer ledger. See the A-Zing Privacy Policy and A-Zing Terms.

2. Job tools and Copy tools

Every service in the DevCentra catalog is labeled Job / download or Copy on page. The label tells you whether DevCentra creates a stored work item.

• Job / download: Creates a work item (a Job). May accept uploaded files and produce downloadable outputs. Job metadata, inputs, and outputs appear in My Work and follow the file retention rules below.
• Copy on page: Runs in your browser (or client UI). The result is text you copy—for example cron expressions, colors, permission modes, number bases, URLs, HTML entities, Dockerfiles, or nginx snippets. Copy tools do not create a Job, do not upload work files to DevCentra, and do not leave input or output file bytes for us to retain.

An active day pass is still required to use either kind of tool. See also Job and Copy on the DevCentra home page.

3. Data we process

• Account identity from your A-Zing Account (email, name, credits balance).
• Access-pass records (capability, duration, validity window, credits charged, auto-deduct preference).
• Device seat registrations used to bind your account license across clients, and a device identifier used so ETOW My Work stays on this device.
• For Job tools: job metadata, uploaded input files, generated output files, form fields you submit, and connection profile details you save.
• For Copy tools: we do not store the calculator inputs or the copied result as a Job or work file. Your client may keep a short local copy history on that device only (clearable in the tool UI); it is not synced to DevCentra or A-Zing servers. Ordinary technical logs for security and operations may still apply.
• Optional passwords you set on a compression or archive job are used only to encrypt that output and are not kept as a reusable credential store.
• Technical logs needed for security and operations.

4. How we use it

• To provide DevCentra features you request across web, desktop, and mobile.
• To show your Job work in My Work (inputs, outputs, submission date, expiry date, status). On ETOW, My Work for new jobs is scoped to the device that ran them. Copy tools do not appear as My Work items.
• To debit credits and show payment history.
• To email your Job work files before they are deleted under our default retention policy (unless you opt to keep files).
• To secure accounts, operate SSH/SFTP connections you configure, and prevent abuse.
• To meet legal and support obligations.

5. Files and connections

• For Job tools, uploaded inputs and generated outputs are stored so jobs can complete and so you can download them from My Work while they remain retained.
• Copy-on-page results are not stored as work files on DevCentra.
• You can delete file bytes for a work item from My Work at any time. The work record (service, dates, status, file names) may remain.
• Connection secrets are stored encrypted for SSH and SFTP profiles you create. Dual-pane workspace sessions use those profiles only while you are connected.
• We do not use your private files or code to train public AI models.
• There is no public share, public drop, or coworker feed for your work files.

6. Retention (29-day file policy)

• This retention policy applies to Job / download file bytes. It does not apply to Copy-on-page results, which are not retained as work files.
• Default: Input and output file bytes are retained for 29 days from job submission.
• Keep files: In Access settings you may opt in to keep files after that window. The default is off. You can turn keep-files off again at any time; files already past the window may then be purged on the next retention run.
• Transparency: My Work shows submission date, expiry date, status, and file names while files are available—and after purge, the work record without file contents.
• Before deletion: Unless keep-files is on, we email those files to the email address on your A-Zing account from [email protected] and record that the notice was sent.
• After deletion: File contents are removed from DevCentra systems. A lightweight work record may remain (service, dates, status, file names).
• Incognito: Incognito Job runs use a much shorter retention window and are not kept as lasting My Work history.
• Account and day-pass records are kept while your A-Zing Account is active and as needed for billing and records.
• You are responsible for downloading or retaining copies you need beyond the 29-day window unless you opted to keep files.

7. Sharing

• We do not sell your personal data.
• Processors (hosting, payments, email delivery) may process data only to provide the service.
• We may disclose data when required by law.

8. Your choices

• Download Job files from My Work at any time while they are still retained.
• Delete work files from My Work without deleting the job record.
• Opt in or out of keeping Job files after 29 days in Access settings.
• Delete connection profiles you no longer need.
• Request removal of account data via Contact.

9. Contact

• Contact A-Zing for privacy requests.
• Related: DevCentra Terms, A-Zing Privacy Policy, Job and Copy, Data policy on DevCentra.