What stays in your browser and what normal site operation records.
Public tool input stays in your browser unless a tool page clearly states otherwise. This page explains the separate handling of ordinary web logs, sanitized product events, and support messages.
- No account is required.
- Files and pasted content are not uploaded for these tools.
- Generated results stay in the browser tab until you copy or download them.
- Product events exclude tool input and generated output.
- Search events use length and result counts rather than raw search text by default.
- Internal QA events are marked separately from ordinary usage.
- Do not submit secrets or sensitive files.
- Messages are retained only as needed for support and follow-up.
- Access is restricted to authorized operational purposes.
- Browser-side tool inputs are not retained by AscendLab servers.
- Support records can be corrected or deleted by request subject to legal limits.
- Security logs may be retained for abuse prevention and audit needs.
Area
Public browser tools
Example pages
calculators, converters, JSON tools, image/video preparation tools
Upload
No, unless a page clearly states otherwise
Account
No
Retention
No server retention of tool input
Status
Live
Area
Normal web logs and product analytics
Example pages
route, tool identifier, coarse device, performance, and error metadata
Upload
No tool input or generated output
Account
No
Retention
Limited to reliability, security, and aggregate product review
Status
Active
Area
Contact and support
Example pages
contact form, bug report, correction request, security report
Upload
Do not send sensitive files through the contact form
Account
No
Retention
Kept as needed for support and follow-up
Status
Available
What may be stored
Sanitized event names and limited metadata that help AscendLab understand tool discovery, search behavior, saved tools, related-link clicks, workflow discovery, errors, coarse performance signals, and aggregate usage trends.
- route
- locale
- surface
- tool_slug
- tool_category
- category
- target
- action
- experiment_id
- variant
- result_count
- result_position
- saved_count
- recent_count
- query_length
- query_token_count
- token_count
- has_query
- no_result
- source
- device_type
- browser_family
- browser
- os
- network_type
- save_data
- event_id
- session_id
- anonymous_user_id
- timestamp
- page_path
- source_page
- viewport_width
- viewport_height
- web_vital
- metric_value
- metric_delta
- rating
- navigation_type
- action_name
- result_success
- input_type
- duration_ms
- file_size_mb
- file_type
- file_size_bucket
- output_size_kb
- settings_preset
- wasm_load_ms
- error_code
- error_stage
- country
- language
- os_family
- traffic_source
- user_agent_family
- anonymous_session_hash
- returning_visitor
- session_age_seconds
- session_id_hash
- visitor_age_days
- visitor_id_hash
- release_id
- release_sha
- build_id
What is not stored
Product analytics are designed not to store public tool input, generated output, raw search text, uploaded file names, uploaded file contents, clipboard contents, full IP addresses, full user-agent strings, full referrer URLs, or precise location.
- raw tool input
- raw uploaded file content
- uploaded file name
- full clipboard content
- exact geolocation
- full IP as product event metadata
- full user-agent string
- full referrer URL
- canvas or font fingerprint
- cross-site advertising identifier
- personal pasted text
- raw sensitive query
- generated result content
Search metadata
Search events use query length, token count, result count, and no-result flags by default so AscendLab can improve search without retaining the raw query.
Anonymous visitor and session IDs
Product analytics may use first-party random identifiers stored in this browser to estimate unique visitors, sessions, and returning visits. These identifiers are not derived from IP address, user-agent fingerprinting, tool input, or cross-site tracking.
Human and bot-like traffic
Admin analytics can separate likely human traffic from bot-like traffic using coarse user-agent family and device hints. AscendLab does not store full user-agent strings for this product-event view.
QA and internal events
Internal QA events may be retained for release validation, but admin analytics separate those events from the default real-traffic overview. Ordinary localhost and non-production product events are skipped unless they are explicitly marked for QA.
Admin exports
Admin CSV exports use the same sanitized product-event fields shown in the dashboard. Some fields may be expanded into columns for filtering, but exports are intended for operational review, not session replay or raw visitor profiling.
Retention
Product events can be pruned after a limited operational window. The default maintenance script targets events older than 180 days unless a shorter or longer internal retention period is configured.
Do public browser tools upload my files?
No. Public browser tools are designed to run locally in your browser unless a specific page clearly says otherwise.
What information can normal site operation send to AscendLab?
Normal page requests can produce web logs, and sanitized product events can record route, tool, coarse device, performance, and error metadata without tool input or generated output.
What should I send in a support request?
Send the affected URL, browser, expected result, and reproducible steps. Do not send secrets, private documents, or sensitive tool input.
Security and deletion questions
AscendLab uses HTTPS for public pages and limits operational access to account-based workflow data. Payment details are handled by payment processors, not stored as full card data by AscendLab. For deletion, privacy, or security questions, email support [at] ascend-lab.com.