What the site collects, where it goes, and what remains to be confirmed

A contact or chat inquiry may include a name, email address, telephone number, city, preferred contact method, and referral information. It may also include facts the visitor chooses to share about a possible legal matter. The site may also preserve attribution details that help the firm understand how the visitor reached the form. Visitors should avoid sending originals or information beyond what is reasonably needed for an initial inquiry.

The memorial scholarship form asks for a name, email address, telephone number, grade-point average, and intended college, university, or trade school. It also asks for an essay in Portable Document Format and agreement to the displayed terms. The tribal scholarship form also asks for the applicant's high school and a Cheyenne and Arapaho enrollment or Certificate of Degree of Indian Blood number. Those fields may involve minors, education information, tribal-citizenship information, and a personal essay.

The current scholarship forms submit through Netlify Forms and redirect to a confirmation page after the browser receives a successful response. The public privacy policy names Supabase, Resend, and Sentry but does not presently name Netlify or describe scholarship uploads. That gap must be corrected only after the firm confirms the production data path, access controls, notifications, retention, deletion, and download practices.

The public and Spanish layouts load Google Analytics when a measurement identifier is configured. A browser visiting a site that uses Google services may send Google the page address and Internet Protocol address, and Google may set or read cookies. Analytics can also receive event details associated with page views and interactions configured by the site. The exact production configuration and enabled Google features require a settings-level audit before a final disclosure is approved.

The site's chat and lead-attribution components use browser session storage for limited session state. That may include chat history, whether the chat was open, and attribution details used with an inquiry. Session storage remains in the browser for the session and is distinct from a server-side intake record. The final policy should describe only the keys and purposes confirmed in the released code.

The firm may use technical logs and error-monitoring information to keep the site functioning, investigate abuse, and diagnose failures. The precise fields visible to Sentry, Netlify, the hosting layer, and other infrastructure providers must be checked against production settings. This draft does not represent that an Internet Protocol address, device identifier, or event record is anonymous.

Information from a legal inquiry may be used to respond, perform an initial conflict or matter assessment, communicate about the inquiry, route the request inside the firm, and maintain operational records. Scholarship information may be used to process the form, review stated eligibility, evaluate the essay, request verification, contact a selected recipient, administer payment, and document the program. Those scholarship purposes are separate from legal intake.

Current code uses Supabase for intake data and related operational records, Resend for certain email delivery, and Sentry for error monitoring. It uses Google Analytics for traffic and event measurement and Netlify Forms for scholarship form submissions and file uploads. Service-provider access, data location, subprocessor terms, security settings, notifications, and retention are controlled partly outside this repository and remain subject to a production-account audit.

The current public policy says the firm does not sell, rent, or share personal information for another party's own marketing. That statement should remain on hold until the owner confirms all advertising, analytics, referral, integration, and vendor practices. Disclosures may also occur when authorized by the person, required by law, needed to protect the site or firm, or necessary to complete a requested service. The final wording still requires legal review.

The firm should keep personal information only for a legitimate operational, legal, ethical, security, or recordkeeping reason. The appropriate period may differ for a declined inquiry, an accepted client matter, an analytics event, an error log, a scholarship application, and a selected recipient's payment record. This guide states no fixed schedule.

A person may contact the firm to ask what information the firm controls about them or to request correction or deletion. Whether the firm can fulfill a request depends on identity verification, applicable professional duties, legal holds, security needs, backups, third-party systems, and other retention requirements. The final policy should describe the process and response expectations the firm can actually deliver, rather than label every request as an unconditional right.

Reasonable safeguards depend on the information and system involved. The Federal Trade Commission advises businesses to inventory personal information, limit collection, protect what they keep, control access, manage service providers, dispose of data safely, and plan for incidents. The public phrase “industry-standard safeguards” is too broad without evidence. The proposed policy should instead describe verified controls and acknowledge that no transmission or storage system eliminates all risk.

Visitors can adjust browser settings, use Google's published analytics opt-out tool, close the chat, and avoid submitting a form. A request to stop direct communications should be honored through the available contact channels, subject to messages needed to address an existing relationship or legal requirement. The current categorical statements about automated text messaging and consent withdrawal remain held for an operational and communications-platform audit.

Using the website or sending a form does not, by itself, obligate Addison Law Firm to represent the sender. Representation requires the firm's agreement and an authorized engagement. A sender should not assume that the firm will protect a deadline, preserve evidence, contact an opposing party, or take any other action unless the firm expressly agrees.

Oklahoma's professional rules separately address information related to representation and circumstances in which a person consults about possible legal services. Duties can depend on the nature of the exchange, what the firm invited, and what occurred. The final privacy and terms language should be reviewed together so a no-engagement warning does not inaccurately promise or disclaim confidentiality.

Questions about the website policy may be directed to the published firm email, telephone number, or Oklahoma City address. A privacy request should identify the relevant form or interaction and enough information to locate the record without sending additional sensitive material. The firm should verify identity before disclosing or deleting information.