dontbeameatproxy.si privacy notice
Kind: privacy notice. Core commitments last changed October 21, 2026. Available features and account permissions determine which operations a person or connected tool can use.
Operator: dontbeameatproxy.si, 1428 Bryn Mawr St, Saxton, PA 16678, United States.
Scope and permissions
This notice covers this product. The current service details below identify its providers, data-store locations, retention settings and access setup. Those details do not broaden the purposes or permissions in this notice. A data-store location is not a promise that all network or provider processing occurs in that location.
dontbeameatproxy.si supplies reusable material and tools and supports research, feedback, testing and collaboration. It processes the inputs needed for the operations you request. Browsing and downloading material do not give dontbeameatproxy.si automatic access to your computer, local files, prompts or model keys.
You or a tool acting with your permission may send messages, feedback, research, source links, reports, files and other inputs through available forms, uploads, APIs, command-line tools or connections. dontbeameatproxy.si may receive, read, store, organize, analyze and return that content to provide requested features, respond to questions, investigate problems, evaluate quality and improve its services and reusable materials. Send only content you have permission to provide, and leave passwords, access keys and unrelated personal information out of submissions.
Where an integration is available, it may exchange selected inputs and results with the service or tool you connect, within the permissions you grant. Private submissions do not become public library material just because they were uploaded. Publication and reuse require the relevant permissions and review. This notice does not grant access to an account, authorize executing uploaded code or make every described interface available to every account.
Data and purposes
The following categories apply when the relevant feature is available and used. A description of a category does not enable that feature or authorize collecting unrelated information.
| Data | Why | Where |
|---|---|---|
| Your email address, password hash, email-verification records and sign-in sessions | To verify your email, complete account setup, sign you in, reset your password and end sessions. Authentication passwords are used only for the requested account-setup, confirmation, sign-in or reset operation; they are not logged or stored in plaintext. | This product's configured identity service |
| An account record that links your sign-in to your account | To know which material and features you may use | This product's service database |
| A digest of each access key | To check a key without being able to show it again. The key itself is shown once and never stored. | This product's service database |
| One usage record for each downloaded item: the item name, its digest and the time | To show usage and reconcile access | This product's service database |
| Feedback, ratings, requests and other content you explicitly submit, together with the account, dates and version or request references needed to understand it | To respond, reproduce problems, identify missing material and improve the service | This product's service database |
| Submitted reports and files, source links, replies, checksums and immutable revision records | To support collaboration, review, reliable retrieval and improvement work | This product's service database and private file storage |
| Connection and consent records, client metadata, granted scopes, expiry information and token digests | To operate authorized connections, check their permissions and investigate access problems | This product's service database |
| A digest of a browser session that you signed out of, until it would have expired | To refuse that session afterwards | This product's service database |
| A waiting list entry, if you ask to join: your email address, an optional note, the state of the entry and its dates | To send the access invitation you requested | This product's service database |
| One-way address digests, bounded attempt counts and their expiry times | To limit repeated sign-in and account-email attempts. Persistent counter records do not contain the raw address. | This product's configured security stores; counters expire when their stated windows end |
| Diagnostic records of refused requests: a random reference, address path, reason code, account when known, time and service version; request content only when detailed capture is explicitly enabled | To find and fix problems within the stated capture and retention limits | This product's restricted service records |
| Your payment details when you choose an available billing feature | The payment provider collects and keeps payment details. dontbeameatproxy.si receives the customer identifier and subscription information needed to manage access. | This product's configured payment provider and billing records |
The current service details explain whether passwords go directly to an identity provider or pass transiently through this product's account-setup, confirmation, sign-in or reset service. Either flow uses them only for that authentication operation. An identity service stores passwords in hashed form, not plaintext.
The default diagnostic profile does not store request bodies or network addresses. Explicitly enabled detailed diagnostics may retain supplied request content for troubleshooting within the configured limits. That content can include project or personal information present in a request. Diagnostic records are restricted, not a public feed; do not rely on automatic removal of every sensitive detail before submitting content.
Access and data exchange
Access to private submissions follows the account and feature permissions. Authorized service operators may review submissions for support, security, quality evaluation and improvement. Content displayed in a private work log is not an anonymous public feedback feed. Removing a name alone may not make a report anonymous; public summaries need review for identifying details.
Customer accounts, billing records, private content, connection consents and history are not shared or combined with another product's customer records. An account or credential for another product does not authorize access here. This does not prevent an exchange with a tool you explicitly connect, within the permissions and purposes described above.
Hosting, identity, transactional-email and payment providers process the information needed to run their respective parts of the service. Optional connected tools or model providers may process content when that workflow is enabled and authorized; their own terms and data practices also apply. Uploading a file by itself does not trigger a model call or send it to an unrelated external service. dontbeameatproxy.si does not sell personal information. General improvement wording, a connection or this notice does not authorize unrelated advertising disclosure, a new unrelated purpose or unrestricted access to other accounts.
Creating an account, retrieving material or requesting an account email does not enroll you in marketing. Any marketing signup is a separate choice and must offer a way to unsubscribe. An access invitation you requested is not permission to add you to a marketing list.
Browser and operational records
- Browser storage is limited to the functional and security purposes disclosed in the current service details. Local storage does not by itself submit that information to a hosted service. These words do not authorize undisclosed storage or tracking.
- It runs no analytics, advertising or tracking scripts. Every script on the site is served from the site itself.
- It records the account, download, submission and connection events described above, rather than a general log of every successful request. Search-gap counts do not retain the search text. Refused requests use the diagnostic records described above.
- Email sent to you has open and click tracking switched off.
Retention and deletion
The storage periods, retention limits and cleanup controls stated in the current service details apply. Access expiry and physical deletion are different: cleanup may run periodically or when records are next used, rather than at the instant access expires. This does not extend a stated retention commitment. Ending a browser session or a connection does not erase the records it created. Token expiry limits access, not the lifetime of associated registration or consent history. Changing a provider or a setting does not by itself override an earlier retention commitment.
To request deletion of your account or submitted content, write to the contact address below and identify the relevant account or report. Removal must account for stored copies, attachments and revision history, not just hide a listing. Records needed for security, disputes or applicable legal obligations may require separate retention. To leave the waiting list, ask in the same way: the entry keeps only a one-way digest of the address and the history of decisions, so the address itself is gone. Current service details identify available deletion controls and when retained backup copies expire.
Current service details
Details last changed: October 21, 2026. These details apply to dontbeameatproxy.si only.
Hosted customer sign-in, billing and private account storage are not configured for this product. Public browsing and browser-local tools do not create an account or payment record. This product does not borrow another product’s customer identity, billing or private-content store.
Before a hosted customer feature is enabled, this section must identify its own providers, data-store locations, retention and backup periods, password handling and deletion controls. No new identity provider, storage location or backup period is represented as active here.
Browser storage: the service sets no cookies. Where a page lets you save selections or export a file locally, those selections stay in that browser or the file you save until you explicitly submit them through an available feature. They are not a hosted account or consent to marketing.
Contact
dontbeameatproxy.si, 1428 Bryn Mawr St, Saxton, PA 16678, United States.
Use this contact for privacy and deletion requests. Do not post passwords, access keys or personal information in a public issue or discussion.
Changes
We keep the current service details accurate when an implementation changes. The date of the last meaningful change is shown with the affected text; formatting or code-only changes do not silently change these commitments. Material changes to data handling need clear notice and any consent required by law before they apply. A revised notice or details section does not by itself authorize a materially different use of information collected under earlier promises. It does not remove your applicable rights.