Your data, from input to saved project.

Local molecular inspection

Local inspection runs RDKit in your browser. This mode does not send molecular inputs to the compute service. Its reports are created in your browser.

Molecule analysis and libraries

Complete analysis sends your structures and chosen processing options to the molecular analysis service. The service returns the results without creating a saved analysis job. Library analysis sends records in groups of up to ten.

These results stay in the current page until you export them. Reloading or leaving the page clears them. Evidence packages are assembled in your browser, and the package builder does not upload the files you attach. Exported packages can contain your original structures and attachments, so review them before sharing.

ADMET predictions

ADMET screening sends your structure to the prediction service. The prediction service does not save submissions to an application database. Standalone results and comparison lists stay in the current page, so export them before leaving.

When you choose to attach a result to a project, it is saved in this browser. It is included in a cloud snapshot when you subsequently save that workspace to the cloud.

Docking jobs and temporary downloads

Docking inputs, poses, logs and results are stored by the compute service while the job is available. A private job credential controls polling and downloads. Your browser saves that credential locally; anyone who holds it can access the job until access expires.

Temporary job access expires 24 hours after submission on the free allowance, and after the period your plan gave it if you are on a paid one; the period is fixed when the job is created and a later plan change does not shorten it. Expired completed or failed jobs are removed during worker cleanup. Download an experiment package or save its archive to the cloud while access is available.

Notebooks saved in this browser

Docking notebooks, research notes, batch progress, measurements and linked ADMET results are saved in browser storage. You can return to them in the same browser after closing a tab. Clearing site data or using another browser will not carry those local records with you.

Notebook JSON exports include research records but omit private job credentials. Exporting a notebook does not include the coordinate files contained in an experiment ZIP. Keep both when you need a portable record with poses.

Cloud workspaces and archives

Signing in uses Firebase Authentication. When you choose Save workspace to cloud, notebook content is stored in Cloud Storage and its listing information is stored in Firestore under your account. Access is restricted to the account owner.

Completed experiment files can also be archived with a snapshot. Cloud archives are separate from the temporary compute download and can be reopened after that download expires. Check the archive status: saving a notebook does not guarantee that every experiment file was captured.

Cloud snapshots are saved copies, not continuous live sync. Save a new snapshot to keep later changes. You can delete snapshots and projects from the Research Hub. Deleting cloud records does not remove files you downloaded or records in browser storage.

Your account, and what is recorded against it

Running a workspace requires an account. Firebase Authentication holds your email address, an account identifier and the sign-in method you chose. If you sign in with Google, we receive the address and basic profile Google releases; we do not receive your Google password.

The docking service never receives your email address or your Firebase identifier. It receives a one-way hash of the identifier, which is all it needs to recognise the same person across devices and count an allowance. Job rows carry that hash, the time, and how many structures were submitted, not who you are.

A paid plan adds a subscription record: the same hashed identifier, the plan, when it expires, and a payment reference. Payments are taken by Paystack. We send it your email address so it can issue a receipt; card details are handled by Paystack and never reach us.

Your rights over that data

Under the Nigeria Data Protection Act 2023, and under the GDPR where it applies to you, you can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, object to processing, or ask for it in a portable form. Write to contact@asidsalservices.com from the address on the account.

Deleting your account removes the authentication record and the cloud workspaces saved under it. Job rows whose retention has not expired are removed with it. Anything you downloaded, and anything in this browser's storage, is yours to delete; we cannot reach it.

We hold account data for as long as the account exists, and results for the retention your plan gave them when they were created. We do not sell personal data, do not use it for advertising, and run no advertising or cross-site tracking on this service.

Where the processing happens

Authentication and cloud workspaces run on Google Firebase. The compute services run on Railway. Both operate outside Nigeria, so using this service involves a cross-border transfer of the account data described above, made on the basis that it is necessary to provide the service you asked for. If that does not meet your institution's requirements, do not create an account.

Suggestions and support

When you submit a suggestion, we send your message, its category and your verified account email to our support inbox through Namecheap Private Email. We use these details to review feedback and reply. Suggestions are not published. Please do not include passwords, private links or confidential research data.

The form does not save a separate copy of your message in our application database. We retain submission counters to limit spam. To request deletion of a support message, contact contact@asidsalservices.com.

Website analytics

We use Google Analytics 4 to measure page visits, successful account registration, completed analyses, checkout starts and confirmed purchases. Google Analytics uses cookies and processes technical information about your browser and device. Our custom events send tool and plan categories, aggregate counts and, for confirmed purchases, an opaque transaction identifier, amount and currency. They do not include molecular structures, compound or project names, results, email addresses or account identifiers. Our page-view events exclude URL query strings and fragments, and retain only the origin of the referring website. Advertising personalisation and Google signals are disabled in our analytics configuration. Browser settings and content blockers may prevent analytics collection.

Hosting, visualisation and support

The 3D viewer loads the 3Dmol library from jsDelivr. Molecular coordinates are rendered in your browser and are not sent to that CDN by this application. Hosting providers may process technical request metadata to operate the services. Any infrastructure backups follow the hosting operator's retention policy.

For confidential work, check that this processing and storage model meets your institution's requirements. For questions or help with deletion, contact contact@asidsalservices.com. Include the relevant job or snapshot identifier, but do not send passwords or private job credentials.