What we hold, and what we never do with it.

1. Who we are and what this notice covers

Distinguished Automations, Inc. d/b/a Consigliere ("Consigliere," "we," "us") is a Delaware C-corporation operating from San Francisco, California. This notice describes information handling for our website, founder go-to-network inquiries, estimated matching, discovery, and related service communications. It also explains how to ask about information we already hold.

The Terms describe website use and the boundary between discovery and separately signed paid work. This notice is not a request for blanket permission, marketing opt-in, or acceptance of new obligations by people who previously contacted us.

2. Information you provide and records we create

On the start page, your email is required. Personal and business addresses both work. The type of business and stakeholder persona in your ideal customer profile (ICP) are optional. Please describe professional needs, not sensitive personal information or someone else's confidential details.

We store your email, the ICP text you submit, the estimated match count, a submission identifier, and creation time. The intake also creates internal workflow fields, including an initial booking-status value and a rate placeholder. These are not information you supplied or evidence that you booked, bought anything, or accepted a price. This form does not collect a name, website, payment details, or password, and it does not create a public account.

For each new accepted scan, we also record your Terms acceptance and privacy acknowledgment: the intake link, evidence identifier, content-bound document IDs and SHA-256 hashes, the exact checkbox wording and its ID and hash, affirmative acceptance and acknowledgment flags, and server time. The checkbox starts unchecked. This evidence records what you reviewed for that submission, not marketing consent, email verification, or agreement to pay.

After results, you may explicitly save one optional USD fee proposal. A blank field saves no proposal; an explicit 0 saves zero cents. We store the proposed amount as integer cents, USD currency, server save time, proposal version, a request UUID and a SHA-256 digest of the canonical proposal for replay detection, all linked to that intake. The UUID identifies a retry, not a person. Capture and proposal audit events record internal intake references and time; capture includes the estimated count, and proposal includes its version and save time.

A successful new scan issues a short-lived bearer authorization for that scan's proposal save. The database keeps its SHA-256 token hash, purpose (proposal creation), intake link, server issuance and expiry times, and consumption or revocation times when set. It does not store the raw bearer token. These records are created for new accepted scans, not backfilled onto earlier inquiries.

If you correspond with us, book discovery, or separately engage us, we may receive the contact details, professional context, scheduling information, permissions, and service records you provide through those interactions. Operational records include lead-capture events, internal alert content, and email delivery status or errors.

3. Network information and its sources

The estimated scan uses a private, locally stored index derived from an export of Josh's LinkedIn connections. Its matching fields are company and position keywords. The underlying network export can include professional names, profile links, and connection information; the scan does not give visitors those private records. This is not a live LinkedIn search or API lookup, and we do not scrape LinkedIn as part of this scan.

Keywords and related terms from your ICP are compared with the local index to produce an aggregate estimate. The export can be stale or incomplete, and a keyword overlap is not verified fit, availability, or willingness to speak. A zero count can reflect absent or unrecognized input or unavailable index data.

The separate Friends of Ours proof roster contains public names, photos, roles, and profile links. It is not the private matching index. A public profile is not permission to introduce or solicit that person. Information for later service conversations may also come from the people involved or professional information they make public.

4. Why we use information

We use inquiry information to generate the estimate, understand and assess your request, prepare for discovery, communicate with you about that request, and determine whether a separate engagement makes sense. We use an optional proposal to understand your expectations and discuss a possible engagement. Authorization and replay records restrict saving to that scan and avoid duplicate proposal writes; acknowledgment evidence documents the policies and wording attached to that submission. We also use operational records to deliver alerts, troubleshoot problems, restrict abuse, maintain service records, and meet applicable legal obligations.

Submitting the form or booking discovery is not a purchase, a billable sales-qualified lead (SQL), or authorization for prospect outreach. Prospect outreach and paid work require a separately accepted signed engagement. An introduction requires affirmative permission from both sides before we share private identifying or direct contact details for it. An engagement does not replace either person's permission.

Saving a proposal, including $0, is not an agreed price, authorization to charge, agreement for free work, or permission for prospect outreach. Pricing is mutually negotiated in a separate signed engagement. For go-to-network work, fees depend on completed qualified prospect calls attended by both sides and meeting the signed criteria, not discovery, booking, an introduction alone, cancellation, or a no-show. Booking discovery stays independent: you can skip saving, or book even if saving fails or expires.

Your inquiry is not automatically published on the proof roster or licensed for public marketing. The scan itself does not send messages to prospects or create introductions. Follow-up to you about your inquiry is distinct from permission to market to you or contact other people.

5. Internal alerts, providers, and other disclosures

Inquiry details, including your email, optional ICP text, estimated count, and submission time, are used in an operator email alert. When configured, the same summary is also sent to an internal Duet channel. Saving a proposal does not send an additional operator alert, email, or booking. The application does not include the raw save token in these alerts. These alerts are best-effort; successful submission does not guarantee delivery. Copies can remain in the service database, email systems, and internal collaboration tools.

Hosting and infrastructure support the website and database. Duet supports our hosting and internal collaboration; the configured email-delivery path uses Gmail through Duet's integration service. These providers receive information needed for the functions they perform. This notice does not promise that information stays on one machine or in one country, or that providers have identical practices.

Private service information, including proposals, authorization records and acknowledgment evidence, is available to authorized operators and others supporting the work as needed for their role. This does not mean the current operator dashboard displays every record. We share introduction details with the people involved after the required permissions, or disclose information when you direct us to do so. We may also disclose information as reasonably necessary to comply with law, address security or misuse, protect rights, or handle a business transfer, subject to applicable protections. We do not provide visitors with the private export or sell access to individual contact records through the scan.

6. Calendly and other external services

Discovery booking opens Calendly outside this website. Calendly collects the information you enter there and technical information under its own terms and privacy practices. We receive scheduling and contact information associated with bookings made with us. Merely displaying the booking link is not evidence that you booked; the scan does not itself submit a booking.

Retained pages load Google Fonts, and our Contact page includes a Google Maps embed. Loading these resources connects your browser to Google, which can receive technical request information such as your IP address and browser details and may use its own cookies or similar technologies. External profile links and other sites have their own practices when you visit them. You can choose not to open external links and use browser controls to restrict third-party resources; some presentation or functions may be affected.

7. Technical information, cookies, and browser storage

Website requests send technical information to hosting infrastructure, such as IP address, browser information, and the requested URL. The scan and proposal endpoints store bounded request-attempt counters in the service database to restrict abuse. Each counter holds its kind, a shared request key or an authenticated save authorization's SHA-256 hash, attempt count, first-use time, and last-seen time. These counters contain no raw save token, email, submitted text, or IP address. They persist across restarts and coordinate workers only when they share the same database file and working database locks, not independent databases or globally coordinated replicas. Separate limits on simultaneous requests remain local to each server process. These controls do not establish verified IP identity. Admitted attempts remain counted even if a request later fails, times out, or disconnects. Other retained public forms use IP-related request-header values for counters; those values are not verified identity or trusted proxy attribution. A lead-capture event records the submission identifier, estimated count, and time; email operations also maintain delivery records. Existing private introduction booking links record an introduction-linked click count and event before opening the booking provider; this is separate from the direct discovery link on the start page and is not proof of attendance. Hosting and providers may process request and security logs separately from the lead record, including headers or response data according to their configuration. The raw save authorization passes through the hosting path in the issuance response and in an Authorization header on save. The application does not deliberately log that bearer, but we do not guarantee provider or edge log redaction, log contents, retention, or storage practices.

Attempt-counter quota windows run for one hour from first use, not as an automatic deletion deadline. Expired counters are pruned synchronously only when a later request reaches counter admission and the database validation and transaction succeed; there is no scheduled cleanup. Idle rows can remain, and a backward server-clock change can delay expiry. Removing a row does not guarantee secure physical erasure from database files, write-ahead logs (WAL), backups, or provider systems, which have separate storage and retention practices. This counter cleanup does not delete intake, acknowledgment, proposal, or save-authorization records.

The current lead-form script sends email and ICP text to our server without saving a resumable form in browser storage or issuing a new account sign-in cookie. The operator dashboard uses local storage for an operator credential; that is not a visitor signup feature. Your browser may still retain cookies or local data from earlier visits. Retirement of public account pages does not itself clear those items.

The raw proposal bearer is held only in the current page's JavaScript memory, not in the DOM, URLs, cookies, local storage, session storage, or another persistent browser store by this script. It is lost on refresh, closing or leaving the page; returning through browser history does not restore save access. A new deliberate scan is a separate intake, not recovery of the old one. Possessing the bearer authorizes that scan's save only. It does not verify email ownership, identity, employment, or authority to bind a business, and page memory is not protection against hostile scripts running in the same page.

Save authorization expires 30 minutes after server issuance and permits one proposal save. While still unexpired and unrevoked, an identical retry with the same request UUID and canonical USD cents can return the original receipt without a second write, subject to request limits. A changed UUID or amount after saving conflicts. Expiry ends even identical replay access, not the saved proposal. There is no email-based or receipt-based recovery or proposal editor on this page.

Browser settings let you clear or restrict cookies and local storage. Third-party resources and external booking have their own storage and measurement practices. We do not describe the whole website or its providers as cookie-free, analytics-free, or tracking-free.

8. Retention and historical records

We retain information according to the legitimate purpose it serves, including responding to an inquiry, performing agreed work, documenting permissions, accounting, resolving disputes, and addressing security or legal obligations. We review information for deletion or de-identification when it is no longer reasonably needed. This notice does not set an automatic deletion deadline or guarantee immediate removal from backups or provider systems.

The 30-minute authorization window is not a database deletion deadline. Saved proposals, hashed authorization records (including expiry and consumption), acknowledgment evidence and audit events can remain after authorization expires or page memory is cleared. There is no automatic deletion schedule for these records in the current application; the short-lived attempt counters described above have a separate, request-triggered pruning rule.

Ordinary database operations are guarded against changing or deleting initial acknowledgment evidence, proposals and capability bindings, or deleting their linked intake. This protects record integrity; it is not a legal reason to refuse a request. Corrections, withdrawal or deletion involving these records need human review and, where appropriate, a separately reviewed privileged procedure that the current page does not automate. These technical guards do not override applicable rights or retention duties. We will consider your request and explain what can be changed, removed or retained and why, including provider and backup limits.

Earlier application, profile, consent, transaction, or service records may remain for appropriate administrative, contractual, security, or legal purposes. Keeping a historical record does not reopen a public account or signup path, authorize new outreach, or mean that person agreed to this updated notice. A request to withdraw an inquiry or delete information will be considered alongside any legitimate need or legal duty to retain particular records.

9. Your choices and requests

You can leave optional ICP fields blank, decline an introduction, choose not to book, or ask us to stop following up on an inquiry. Email josh@consigliere.so to request access to, correction of, or deletion of your information, to withdraw an inquiry or permission, or to raise a privacy concern. This contact is also available if you appear in a network export or the public roster without having submitted the lead form.

Describe what you want us to review and enough context to locate the information. We may ask for proportionate verification before disclosing or changing private records. Do not send passwords, full identity documents, or sensitive identifiers in an initial request. We will explain the response and any applicable retention limits; requests are handled by people, not an automated account tool. Withdrawal cannot undo an introduction or disclosure already made, and a paid engagement has its own termination terms.

You may have additional rights under the laws that apply to you and to us, including rights concerning access, correction, deletion, or certain uses and disclosures. Nothing here waives those rights. We will address applicable requests under those laws rather than treating this notice as a claim that every privacy law applies or that statutory rights are unavailable.

10. Security

Controls in the service include restricted operator access, private-file exclusions in web serving, and form rate limits. These controls reduce risk but are not a guarantee of absolute security, confidentiality, or error-free operation. Please avoid submitting information that is not needed for a professional inquiry. Report suspected unauthorized access or disclosure to josh@consigliere.so.

11. Changes and contact

We identify the notice revision here. If our information handling materially changes, we will identify the changes on the website or communicate them directly when appropriate. We will seek separate permission where required rather than treating historical contact or consent as agreement to a new use. Publishing this notice does not create an assent record or retroactively change a signed engagement.

Privacy questions and requests: josh@consigliere.so, or see our Contact page.

Mailing address: Distinguished Automations, Inc. d/b/a Consigliere, 2261 Market Street, STE 46146, San Francisco, CA 94114.