Your record. In clear terms.

Dear 2126 cards

Dear 2126 works without an account. Your sentence and optional nickname remain in the page in your browser; the card is generated there. They are not sent to BYTE, automatically published, or added to a private archive. Leaving or reloading the page clears the text. Saving a card downloads an image to your device; sharing it sends the image to the destination you choose, under that service’s rules.

When enabled, BYTE collects daily totals for page views, card creation, share and save actions, invitations, referred visits, and the Explore BYTE link. These totals use only predefined campaign, prompt, and headline choices. They do not include sentences, nicknames, account identifiers, or saved visitor identifiers. We respect Do Not Track and Global Privacy Control signals for this measurement.

Invitation links can contain an anonymous signed token that expires after 30 days. We do not store individual invitation tokens or build a relationship graph. Your browser may keep up to eight of its own tokens in session storage to avoid counting its own invitations as referred visits. Daily aggregate measurements are retained for 90 days. Abuse prevention briefly uses network addresses in server memory; ordinary server access logs also contain network addresses and requested paths, but omit query strings and message contents. Counts are approximate activity, not a count of unique people.

Staff administration

Authorized staff use individual passkey accounts with permissions assigned to their role. Account-support tools show account details, verification status, and aggregate storage and session counts. They do not provide access to private archive contents. Finance tools show payment references and financial status; anonymous donation records have no donor name or BYTE account association. Administrative access, account and payment lookups, and operational changes are recorded in an activity log with the staff account, action, time, relevant record identifiers, and a reason where required.

Account access

The service stores your display name, an account identifier, passkey public credentials, and authentication metadata to maintain your account. Passkey private keys remain with your authenticator or passkey provider. Session cookies are required for signed-in access; the database stores hashes of session tokens. Challenge records and security rate limits help prevent replay and automated abuse. This application does not include advertising trackers.

Optional account email

You may add an email address at registration or in Account security. We verify that you control it before sending welcome, allocation, refund, and security notifications. Email does not grant sign-in or account recovery access. You can change or remove the address after verifying a passkey. This is not a marketing subscription.

Contact addresses and queued message contents are encrypted in our database. SMTP2GO processes the recipient address and message to deliver these emails. We do not include private archive contents, recovery codes, or payment card details, or use tracking pixels. Queued recipient and message data are cleared after delivery or expiry, within seven days. Address changes and account closure may generate a final security notice to the previously verified address. Contact details are removed on closure; encrypted recovery copies expire under the 30-day backup policy.

Identity verification

Stripe Identity collects identity documents and a matching selfie on its hosted verification page. BYTE retrieves the verification result and temporarily processes a verified document number, issuing country, and document type to compute a keyed fingerprint. It retains the fingerprint, verification status, and Stripe session reference; it does not store raw identity images, document numbers, or dates of birth in its account database. The fingerprint detects repeated use of the same document. It is still personal information and is protected as account data.

Stripe processes and retains verification material under its own applicable terms and privacy policy. If the provider cannot supply the verified information needed for the check, checkout remains unavailable for that account.

Payments and certificates

Stripe’s hosted checkout handles payment details. BYTE does not receive or store your full card number or security code. It stores checkout and payment references, amount and currency, payment processing status, accepted terms version, and the issued allocation. Signed certificates contain an allocation identifier, display name, payment references, and the service’s public verification key. Certificates contain no passkey or server signing private key. Share a certificate only if you intend to disclose its contents.

Donations and anonymous giving

Donations can be made without an account. An anonymous donation is recorded without a donor name or link to a BYTE account. If you turn off the anonymous option, the name you provide and any signed-in account can be associated with the donation. Donor names are not published on this website.

Stripe processes payment and billing details, which may be visible to BYTE’s payment administrators in Stripe. Anonymous giving does not conceal a transaction from the payment processor or your bank. BYTE’s application retains the amount, currency, payment references, payment status, and limited refund or dispute information. A private browser cookie lets you return from checkout and view your donation confirmation. Its token is stored as a hash in the database.

Private archive files

Files you choose to upload pass through the service and are stored with application encryption in its configured private storage. The operator controls the server encryption keys; this is not end-to-end encryption against the operator. Account authorization protects retrieval and deletion. The database retains metadata such as filenames, file sizes, record type, and storage references. Supported text imports may be processed to provide archive and persona features. Upload only material you have the right to provide, especially genetic data and private conversations.

You can remove supported files in the archive. Removal deletes the active stored file and its active archive record. This notice does not promise immediate deletion from independently retained provider logs or retained payment records. Encrypted daily recovery copies are retained for 30 days in the same private storage bucket. Deletion records are applied before a backup can be restored to service, so deleted content is not returned to an active archive.

Optional persona processing

A persona request, when the feature is configured, sends your question, relevant archive material, and up to six recent chat messages (4,000 history characters total) to the configured model provider with your consent for each request. Recent chat supplies context; current archive excerpts provide the supporting evidence. File upload alone does not request a persona response. The interface identifies availability and asks you to initiate the request. Do not submit information you do not want processed for this purpose. A generated response is not a living person, an authenticated memory, or proof of consciousness.

OpenAI provides optional persona answers and audio transcription. Transcription sends only the audio file you select after a separate consent step and stores the returned transcript in your private text archive. Uploaded audio is not sent automatically. A saved transcript can later supply excerpts for persona questions with your consent. Genomic files are excluded from these requests. Provider processing is subject to OpenAI’s privacy and data retention policies.

Retention and your choices

Account information is used to provide access, enforce allocation limits, secure the service, and maintain payment records. Private archive material is retained until you remove it or the service’s account and retention processes require otherwise. Applicable access, correction, erasure, objection, and other data protection rights are not waived by purchasing an allocation. The archive’s export and removal controls support management of uploaded files. The service operator is responsible for responding to requests that cannot be completed through those controls.

The Security tab provides a complete archive export and account closure. Closure immediately ends access and deletes active private files and conversations. If storage is temporarily unavailable, access remains revoked and deletion is retried. Financial records, signed allocation receipts, and allocation identity fingerprints are retained for payment administration and allocation limits. Closing an account does not issue a refund. A full allocation refund ends membership access; data export and deletion remain available while the account is open.

The service is intended for adults. Do not submit a child’s genomic information or identity documents. Contact the service operator below about privacy requests that are not available through your account controls.

Service operator and contact

Dekamco Development

legal@dekamco.com