Overview
This notice describes what data may be processed when you use yflong.dev, why it is processed, and what control you have. This site is a personal portfolio and does not use ad-tech profiling or data broker integrations.
Some interactive features, including the algorithm visualizer, store functional preferences in your browser and may reflect your current state in the URL so a view can be restored or shared.
What Data Is Used
Data used by this site is limited to:
- Technical request data needed to load and protect the site, including the requested URL.
- Browser-side storage keys used for core interactive features.
- URL query parameters used to restore or share algorithm visualizer state.
- Information you choose to share with third-party services you open from this site.
Browser Storage Keys
The following keys may be stored in your browser for functional behavior:
sessionStorage:yflong_terminal_session
Stores a temporary session code so the terminal boot animation can be skipped.
Retention: Up to 2 hours, scoped to the current browser tab/session.
localStorage:yflong:ctf:unlocked:v1
Remembers whether the CTF vault has been unlocked.
Retention: Persists until you clear site data in your browser.
localStorage:yflong:alg:visualizer:preferences:v3
Remembers algorithm visualizer settings such as the selected algorithm, compare mode, quiz mode, custom dataset values, target value, and graph target.
Retention: Persists until you clear site data in your browser.
URL-Based Feature State
The algorithm visualizer pages under /algcan mirror some of your current settings into the address bar so the experience can be restored after refresh and optionally shared with others.
Depending on how you use the feature, the URL may include compare mode, quiz mode, custom numeric input data, target value, and graph target node, while the selected algorithm itself may also appear in the page path. Because these values become part of the page address, they may appear in your browser history, bookmarks, copied links, and standard infrastructure request logs when that URL is loaded.
Why Data Is Processed
- Deliver site content and keep core UI features working.
- Remember feature state, such as animation skip windows, CTF unlock state, and algorithm visualizer preferences.
- Restore or share algorithm visualizer sessions through URL state.
- Maintain service reliability and security.
Data Sharing and Providers
Hosting and content delivery
Infrastructure providers may process technical request metadata to deliver and secure the site, such as IP address, user-agent, requested URL (including query string), and request timestamps.
External links
Links to third-party services (such as GitHub, LinkedIn, and blog properties) are controlled by those services once you leave this site.
Cookies and Tracking
This site does not currently use marketing cookies or cross-site advertising trackers. Functional browser storage may still be used for site features, as described above. If that changes in the future, this notice will be updated.
Security and Retention
Reasonable technical and organizational steps are used to protect site operations. Storage duration is limited to functional needs, and you can clear browser data at any time.
Your Choices and Rights
- Clear or block browser storage from your browser settings.
- Remove algorithm visualizer query parameters before bookmarking or sharing a link if you do not want that state in the URL.
- Choose not to open third-party links from this site.
- Request information or raise privacy concerns by email.
International Visitors
If you access this site from outside the country where infrastructure is operated, your information may be processed in other jurisdictions.
Children's Privacy
This site is not directed to children under 13, and no intentional collection of personal data from children is intended.
Contact
If you have questions about this notice or data practices, you can contact me via email or LinkedIn using the links provided on the main terminal screen or contact page.