Useful tools.
Deliberate boundaries.

Local tools

Self-check answers, pasted headers, JWT samples, IPv4 calculations, file/text hashes, synthetic authorization decisions, learning answers and risk-canvas inputs are processed in your browser. This implementation does not send them to an application server. Up to eight assessment snapshots, their notes and action metadata use local storage only after you choose Save on device or explicitly import into the workbench. Resource bookmarks are stored when you choose Save. The document studio does not automatically store your input. Device storage is not encrypted by this application; do not use it as an evidence vault. You can export or delete snapshots in the workbench. Clearing snapshots does not delete downloaded files, bookmarks or display preferences. Theme and animation preferences are stored when you change them. Browser restrictions may prevent storage; errors are shown where relevant.

Roadmaps and data controls

The current-to-target roadmap stores one record under an explicit Save action. Current responses, intended targets and action states remain separate. Saved snapshots can be copied into a roadmap without changing their original answers. Imports replace the open draft only after validation and confirmation where needed. The help page deletes only selected records belonging to this site. It does not remove enquiries or files already downloaded.

Manual assessment plans

The pentest planner stores one versioned plan in this browser only after you choose Save on this device. Imported plans first enter the working area and are not automatically saved. Plan text, original checklist states and notes are not uploaded or attached to enquiries. You can export a working copy or remove the saved copy independently; removing it does not clear an open unsaved draft or previously downloaded files. These records do not grant testing authorization or establish that a test was performed.

Enquiries

When enabled, the enquiry service stores your name, email, topic, message, consent timestamp and a generated reference. The local preview stores these in a local SQLite file. The supplied Worker adapter uses a separate, owner-configured database. Assessment answers are not attached. Do not submit credentials, sensitive records or live vulnerability details.

Enquiry records are intended for responding to your message, not marketing. The supplied backend expires them after 90 days using its maintenance process; operators must also set compatible hosting logs, backups and provider retention. The preview does not represent an active public service.

Optional notifications

Email notifications are disabled unless the owner configures and tests a verified sender, recipient and Resend API access. A notification contains a reference and topic, not your full message or email. Message acceptance and email delivery are different events. The interface distinguishes a local review queue from an enabled public service.

Hosting and abuse prevention

A hosting provider may process connection data under its own terms. The application uses short-lived keyed address hashes and rate counters to limit enquiry abuse; it does not save raw IP addresses in the enquiry database. There are no advertising pixels, third-party font requests, embedded social feeds or application analytics in this version.

External links and contact

Email links open your own email application. Messages you send directly to abdullahbinzarshaid@gmail.com are handled through your email provider and the recipient’s Gmail mailbox, not through this website’s form queue. Copying the address does not send a message. These email conversations are for the request you choose to make, not automatic newsletter enrolment.

LinkedIn, GitHub, X and official reference sites apply their own policies. Links are not embedded feeds. For a question about an enquiry or an access/deletion request, use the verified personal contact route on the contact page and provide the reference only where appropriate.

Separate company

This personal site does not share a database, authentication session or visitor records with a separate company website or private GRC workspace. A future integration requires an explicit purpose, appropriate permission and an updated notice.