Archived copy, read only: Privacy Policy, disclosure version 2026-10-16-v13. This is the exact text of that version. All versions
← Back to evaluator
← Back

Privacy Policy

Effective date: October 16, 2026 · Last updated: October 16, 2026 · Disclosure version: 2026-10-16-v13

This Privacy Policy describes how Dovewood Capital, LLC, a Texas limited liability company (“authentix,” “we,” “us,” or “our”), collects, uses, and discloses information in connection with the authentix account authenticity evaluation service available at authentix-account.com (the “Service”).

1. Who this policy covers

This policy addresses three categories of people whose information the Service may process:

2. Information we collect

From visitors. When you request an evaluation, we record the username you submitted. The Service uses server-side rate limiting to prevent abuse and protect the Service’s underlying data sources. When you ask for a price, we store a one-way coded form of your network address with it (changed every day; the address itself is never stored) to limit how many price checks come from one network each day. When you request an evaluation, Cloudflare tells us the approximate location of the network your request came from, and we record it with that evaluation: the Cloudflare data center that handled the request, the country, continent, region and region code, city, postal code, metro code and timezone, together with the network’s autonomous system number (ASN) and its organization name. It is derived from your internet connection, not from your device’s GPS, and it is approximate: it can point to your internet provider rather than to where you are. We keep it encrypted as part of that evaluation’s audit record and show it only to you, on that evaluation’s result. It is not included in shared results or report PDFs and is not sent to X or xAI. Clearing your evaluation history hides the evaluation from your history but does not delete this record; it is deleted together with the reading, when you choose Delete now or automatically 90 days after the reading (see Data retention and Keeping or deleting a reading). Latitude and longitude are not recorded, and browser geolocation is never collected; records made before October 7, 2026 may also contain the approximate latitude and longitude Cloudflare reported at the time, kept encrypted like the rest of that record. Rate limiting counts requests using a one-way code computed from your IP address with a secret key and the date, so it changes every day; your IP address itself is not stored.

About evaluated X accounts. When an evaluation is requested, we retrieve and store data about the corresponding X account directly from the X API, including (as available): user ID, username, display name, biography/description, location, website URL, profile image, banner image, verification status, account creation date, follower/following counts, post counts, pinned post, and the text, timestamps, references, and public engagement metrics of posts returned for the history window you chose (30 days, 100 days or full history, as the account’s age allows), including the most recent public post.

This data is retrieved from X’s public API in accordance with X’s Developer Agreement and Policy, and reflects information the account holder has made public on X. The account holder has not separately consented to authentix’s specific use of this data, and may not be aware their account has been evaluated.

AI Analysis. Eligible users may receive an automated AI-generated interpretation after an evaluation. The AI layer reads the stored evaluation result, deterministic signal evidence, account facts, seven-day activity aggregates, and the stored public post corpus for the history window you chose (30 days, 100 days or full history, as the account’s age allows). AI output does not change how the AAE-1.0 score is calculated, but automated AI readings, including the Grok assessment, are part of the final score, as described in Final score and Grok assessment. Generated analysis may be cached with the associated evaluation record for authorized future retrieval.

Administrator evaluation access. Authorized authentix administrators may evaluate an account other than the X account used for sign-in. Administrator status is enforced server-side from the authenticated user record. Any signed-in user may also check another public X account for a lawful purpose, after giving the reason described in section 17 (see Terms section 1).

Evaluation results, credentials, and consent records. We generate and store a numeric score, a decision classification (approve / review / do-not-approve), a confidence rating, and the underlying signal-level evidence used to reach that assessment. If an evaluation meets our approval threshold, we may issue a one-time verification credential. We store a cryptographic hash of each issued credential (never the credential itself in plain form) along with its issuance time, expiration, and consumption status, and we log verification and issuance events for audit purposes. Before an authenticated user may request an evaluation, the Service requires affirmative approval of the then-current Privacy Policy, Terms of Service, and Disclaimer. We retain an immutable consent record containing encrypted representations of the submitted username and approval response, together with the authenticated account identifiers, disclosure versions, consent schema version, and timestamps, for consent, legal, and audit purposes.

3. How we use this information

4. Disclosure to third parties

X (formerly Twitter). We query X’s API to retrieve the account data described above. This is the source of that data, not a recipient of data we collect independently.

Cloudflare, Inc. The Service is hosted on Cloudflare’s infrastructure, which processes and stores data on our behalf as part of providing that infrastructure, potentially across multiple jurisdictions as part of Cloudflare’s global network.

Network location and X profile location. The Service records the approximate network location of each evaluation request, but not its latitude or longitude, as described in Information we collect. Browser geolocation is never collected. An evaluated X account’s profile location field may nevertheless be retrieved from X when it is publicly available, because it is part of the public X account data used by the evaluation.

Relying parties who verify a credential. When a third party submits a valid credential for verification, we return to them the associated evaluation’s username, X user ID, and AAE-1.0 score, decision, and confidence rating for the evaluated account. Credentials are based on the AAE-1.0 result, not on the final score. This means information about an evaluated X account can be disclosed to a party the account holder has no relationship with, based solely on that party’s possession of a valid credential. We do not independently verify what a relying party does with this information after it is disclosed.

xAI. We send xAI public information about the checked account, including the text of its posts and the pictures attached to them, as described in Evidence view and AI-assisted analysis and Final score and Grok assessment, so that its Grok models can read them and return an assessment. xAI also provides Ara’s voice (Grok Voice), as described in section 19.

Stripe, Inc. processes card payments and refunds. We receive the payment result, the amount, the Stripe customer reference and the email address given at checkout; card numbers are handled by Stripe and never reach us. Resend delivers our email, such as refund notices, block notices and privacy-request messages. Google Cloud Vision web detection is used as described in Pictures and faces. We do not send text messages (SMS) or make phone calls; the share option that offers to text a report link opens your own device’s messaging app, and we send nothing through it.

Visitor notifications. When someone opens the home page, we send ourselves a short notification through a third-party push-notification service (not a text-message service), at most once an hour for the same browser: the visitor’s country (as Cloudflare reports it), whether the device is a phone or a computer, the website that linked to the page (its domain only), and, if the visitor is signed in, their X username, or otherwise the word anonymous. Automated agents and our own administrators are not included. To avoid repeat notifications we briefly keep a one-way code made from the visitor’s IP address and browser, in Cloudflare’s cache for one hour; we do not store the notification ourselves, and the notification service keeps it under its own terms. Sky and weather. The home page shows a live sky above the Challenger Deep, with the time and temperature there. The weather comes from MET Norway (api.met.no). Our own server fetches it and passes it on, so your browser never contacts MET Norway or any other weather service, and nothing about you is sent to one. We do not disclose information for cross-context behavioral advertising. When a customer requests a check, we create observations and inferences linked to the checked X account and disclose the report to that customer. A paid disclosure like this may be treated as a sale of personal information under some state privacy laws, even though the underlying posts are public. A customer’s acceptance of our Terms is not the account holder’s consent. If your account was checked, you can ask us to stop future checks or opt out of sale or sharing using the privacy request form (see section 6).

5. Data retention

We keep information only as long as we need it, and we delete it automatically on the schedule below. Deletion runs every hour, in batches, and each deletion is recorded in an audit log (what kind of record was deleted and when, not its contents).

We keep some records longer because the law or our legal obligations require it: payment and billing records (including paid prices, charge authorizations, refunds and the Stripe customer reference); consent records, which are the evidence of what you agreed to and are not deleted when a report is deleted; reasons recorded for checking another account (3 years, see section 17); records of blocks, appeals and refunds with their logs; and the minimum needed to honor a privacy request, such as a request not to be checked. Information that is subject to a legal hold, an investigation or a legal claim is kept until the hold ends. Backups and caches may hold a copy for a short time after deletion.

Credentials expire automatically 15 minutes after issuance or immediately upon use, whichever comes first, and cannot be reused once consumed or expired.

6. Your rights and choices

Depending on your location, you may have rights to request access to, correction of, or deletion of personal information we hold about you. This includes account holders whose public X account was evaluated by a visitor, even though that account holder did not initiate the evaluation themselves.

To make a request, use the privacy request form, contact us at kellyhorak@authentix-account.com or use the in-site support chat (use the ? help button). The form covers access, deletion (including deleting your authentix account), correction, opting out of sale or sharing, and asking that your X account not be checked. You do not need an authentix account or a purchase to send a request, and we do not charge for it. We act on a request only after you confirm your email address. We acknowledge requests within 10 business days (usually at once, by email) and respond within 45 calendar days; if the law allows an extension and we need one, we tell you why within that time. Opt-outs of sale or sharing are processed as soon as feasible, and within 15 business days where California law applies. If we deny a request, we explain why, and you can ask for human review by replying to our response. Requests and appeals stay available even if purchasing has been suspended for your account. Deleting information we hold does not delete a PDF, screenshot or other copy someone has already made. We will need to verify the request relates to an account or record we actually hold before acting on it.

State privacy rights

We apply one standard to everyone in the United States. Whichever state you live in, and whether or not a state law covers us or you, you can use the rights below, and we never refuse, slow down or limit a request because of your state. We do not block or restrict any state from using the Service. Some state laws, including those of California, Colorado, Connecticut, Texas, Virginia and other states, give these rights by law; we offer them to everyone.

An authorized agent may make a request for you with your signed permission; we may ask you to confirm your identity with us directly. We verify requests in proportion to their sensitivity, usually by confirming your email address and, for information linked to an X account, that the account is yours. We do not use cookies or trackers for advertising, so we do not disclose information about your visits to our site for advertising; if your browser sends a Global Privacy Control signal, we treat it as an opt-out of sale or sharing for that browser and for your authentix account if you are signed in. To opt out for an X account that was checked, use the form so we know which account. If we deny your request and your appeal, we explain why, and you can contact the attorney general of your state.

If you hold an X account, you can ask that it not be checked on authentix. Once you show that the account is yours, either by signing in to authentix with it or by adding a one-time code to your X bio, we add its X user ID to a “do not check” list and refuse new prices and checks for it before any payment, including if the username changes. We keep the X user ID, the username at the time and the request record so the list keeps working.

There is no self-service account deletion. To delete your authentix account, sign in and send a “Delete my authentix account” request with the privacy request form; the owner carries it out after confirming the request. When we delete an authentix account, we delete its sessions, sign-in tokens, saved accounts, unpaid prices and readings, and remove the X identity from the account record. We keep payment and billing records (including paid price records, charge authorizations, refunds and the Stripe customer reference), consent records, reasons recorded for checking another account (3 years), records about any block or appeal, the request record itself, and any reading under a legal or investigative retention hold until the hold ends. Signing in again later starts a new, empty account.

7. Cookies and tracking

The Service uses a small number of security and authentication cookies. During X OAuth sign-in, oauth_state and oauth_verifier are temporary cookies used to validate the OAuth state and PKCE security flow; they expire after no more than 10 minutes. After successful sign-in, authentix_session maintains the authenticated session and expires after 30 days. These cookies are marked HttpOnly, Secure, and SameSite=Lax. They are used for authentication and security, not for advertising or behavioral tracking.

Visitor count. To count how many different browsers visit the Service, we set a first-party cookie named ax_vid containing a random identifier. We store it with the date it was first seen and nothing else: not your IP address, device details or X account. It expires after two years. Browsers used by our administrators carry a second cookie, ax_vx, so they are not counted; it expires after five years. Like the cookies above, these are HttpOnly, Secure and SameSite=Lax, and are not used for advertising or behavioral tracking.

Welcome window. When you are signed in, we record that your account has been shown the welcome price window (your account and the date), so it is not shown again on your other devices.

Settings kept in your browser. The Service saves a few preferences in your browser’s own storage, such as your display mode, sound and motion choices, and which notices you have already seen. They stay on your device and are not sent to us.

8. Children’s privacy

The Service is not directed to individuals under the age of 18, and we do not knowingly collect information from children. If you believe a child has been evaluated or has submitted a request through the Service, contact us at kellyhorak@authentix-account.com.

9. International data transfers

Because the Service is delivered via Cloudflare’s global edge network, data may be processed in countries other than your own or the evaluated account holder’s own, including the United States.

10. Security

Credentials are stored only as SHA-256 hashes; the plaintext credential is never persisted. Credentials are single-use and time-limited. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Evidence view and AI-assisted analysis

When you ask us to check an X account, we build an evidence view from public information about that account that X makes available to us: the public profile (name, bio, location, link, profile picture, join date, verification status, and public follower, following, post and list counts), public posts from the history window you chose (30 days, 100 days or full history, as the account’s age allows) (their text, time, kind, public like, reply and repost counts, links, and the pictures attached to them), and public lists and a small sample of recent followers and accounts followed, which we use only in aggregate and never display by name.

We analyze this information automatically. The automated reading of posts and pictures is done by Grok models provided by xAI: we send xAI the text of the posts and the pictures attached to them (the image files themselves), and xAI returns its readings under the terms that apply to its API. Each picture is sent once and is never resubmitted. Cloudflare, Inc. runs supporting models for us on its Workers AI service, which receive post text to compare wording, and Workers AI replaces xAI for these readings only if our xAI service is unavailable. The analysis can describe a picture, read text that appears in it, and offer an estimate of whether a picture may have been generated or heavily edited by AI. These estimates are opinions and can be wrong. We never use facial recognition or identify anyone from their face. Impersonation is checked by comparing the account’s claimed name and handle with verified accounts, and whether its picture is an exact or near-exact copy of the verified account’s image. The banner and bio are compared the same way (a copied banner image or copied bio wording). These are whole-image and text comparisons, not face comparisons: a different photo of the same person is not matched. We do not create biometric identifiers or templates: pictures are compared only as whole images, by a small fingerprint of the image file.

We use this information only to produce the evidence view for the customer who requested the check. We do not use it to train our own models. We keep the results with the evaluation in your history, encrypted at rest. We store the analysis, including text read from pictures, and links to pictures hosted by X; we do not store copies of the pictures. These results are deleted when you clear your evaluation history or delete the reading. You can also ask us to delete them sooner by contacting us using the details in this policy.

If you hold an X account that someone else has checked and you want information about it removed from our records, contact us using the details in this policy and we will review the request.

12. Deeper evidence view and automated reading of posts

With every report, the evidence view can read more of what X makes available about the checked account: all of its public posts from the history window you chose (30 days, 100 days or full history, as the account’s age allows) that X returns (up to X’s own limits), the public posts those posts reply to or quote, public posts by other accounts that mention it together with those accounts’ public usernames and basic public profile details, the public lists it owns or follows, X’s own daily post counts, and the public Spaces it hosts. Posts written by other people are used only as context for the checked account and are never the subject of a check.

authentix reads public data only. Reading protected posts is turned off: we do not read protected posts or likes for any account, including your own, and your X sign-in is used only to sign you in, never to read evidence. If an account is protected, its posts are not read and the report says so.

Every report includes an automated reading of the account: Grok models provided by xAI read the bio, posts, replies and the posts they answer, mentions, lists and the picture analysis, and give scores for authenticity, credibility, behavior, conversation context, alignment between the bio and the posts, language, and pictures. Each score must cite the posts it relies on, and a reading that cites anything not in the evidence is discarded. These scores are automated opinions about public content and they have not been validated against accounts of known origin. They do not change the AAE-1.0 result, but they are part of the final score, as described in Final score and Grok assessment.

These results are stored with the evaluation, encrypted at rest, replaced when a newer check of the same evaluation finishes, and deleted when you clear your evaluation history or delete the reading.

Pictures and faces. Our image comparison checks whether whole images appear identical or similar within the sources actually searched. An apparent match does not establish who created an image, who owns its rights, which publication came first, whether use is authorized, or whether an account is impersonating anyone. An absence of matches does not establish originality. We do not use this feature to identify a person from their face or compare different photographs of a person using facial features. Pictures are compared only as whole images, by a short fingerprint of the image file (a perceptual hash) that contains no face measurements. The AI models that describe pictures are instructed never to identify or name anyone, compare faces, describe facial geometry, or estimate age, race, ethnicity, religion, health, sexual orientation or other sensitive traits, and we do not use face-recognition, face-matching or face-template services. Where we use Google Cloud Vision web detection to find where a profile picture appears online, we use only the list of matching pages; Google states that Cloud Vision does not support recognizing specific individuals. We do not collect voiceprints.

13. Price quotes

When you ask for the price of a check, we read a small amount of public information about the account you name before anything is purchased or run: its public profile and X’s own counts of how many posts, and how many posts with pictures, it published in roughly the last 30 days (counts for 100 days and full history are estimated from these). We use this only to calculate the price, and to start the check without reading it again if you buy it. We keep the quote with your account so that a paid check can be matched to the account it was priced for, and if part of a paid check cannot be completed, for example pictures that could not be read, and the part of the price for it is refunded automatically, we record the refund with the payment in our billing records and use the email address given at checkout to tell you about it, sending that message through our email delivery provider, Resend.

14. Final score and Grok assessment

When a check finishes, we calculate a final score from 0 to 100 and keep it with the evaluation. Part of the final score is an assessment by Grok, an artificial-intelligence model provided by xAI. To produce it, we send xAI the public information about the checked account that the check uses: its public profile (name, username, bio, location, link, join date, verification status and public follower, following, post and list counts), its pinned post, the text, time and public engagement counts of its recent public posts, and our automated readings of the pictures in those posts. The pictures themselves are also sent to xAI for the picture readings described in Evidence view and AI-assisted analysis. xAI also receives the public profile and recent public posts for a separate automated check for impersonation, unsupported claims and scam patterns. We send xAI only information about the checked account, never the name, email address, sign-in or payment details of the customer who requested the check. xAI processes this information to return its assessment, under the terms that apply to its API.

The rest of the final score combines a score for the account’s public profile and activity, the score from the evidence view for the history window you chose, which is calculated mainly by fixed rules from the account’s public data although some of its inputs come from automated readings, and the automated reading scores. How much each part counts depends on how confident it is and on how strong the fact-based scores are; the exact method is proprietary. Within each score, information that is missing or could not be read earns no points, so it lowers the score rather than being left out. Only a part of the check that could not run at all, for example because a provider failed, is left out, and the remaining parts make up the whole score. The final score is then described by one of six conclusions: Looks genuine, Mostly checks out, Mixed signals, Hard to verify, Warning signs found (a specific signal, such as a resemblance to another account or to a known risk pattern), or Too new to tell (too little public history). Each conclusion is shown with the reasons behind it. A conclusion is an automated opinion and not a finding about any person. Automated readings of whether a picture was generated or altered by artificial intelligence count toward the final score and are shown next to the post the picture belongs to.

The final score, its decision and confidence, and the scores it was built from are what your evaluation history, shared results and report PDFs show. The AAE-1.0 score is still calculated and kept with the evaluation, and verification credentials are issued and verified on the AAE-1.0 result, not on the final score.

15. Keeping or deleting a reading

After each reading we ask whether you want to keep your own copy on your device, delete the reading now, or do neither. If you do neither, the reading stays on our servers, in your history, for 90 days or until you delete it, whichever comes first (see Data retention).

Delete now. If you choose Delete now, we permanently delete the reading from our servers, together with everything we stored about it: the evidence, the post and picture analysis, the AI interpretation, any share link, any verification credential and the audit records tied to that reading. This cannot be undone. The records of what you agreed to (consent and checkout confirmations, with the document versions and times) are kept separately as the record of your agreement and are not deleted with a reading. We keep only our payment and billing records for the check, which we are required to keep, and they no longer point to the reading. A reading that is subject to a legal or investigative retention hold cannot be deleted while the hold lasts. Backups and caches may hold a copy for a short time after deletion, including a share image that has already been cached.

Saving to your device. If you choose Save to this device, a copy of the reading is stored in this browser on this device only, using the browser’s own storage. It is never sent to our servers. authentix, including its administrators, will not open, read or copy that copy without your explicit written consent. We cannot control who else can use your device or browser: anyone who can use this browser profile, software or browser extensions you have installed, and the browser itself can see it, and clearing this site’s data in your browser erases it. Saving a copy does not delete the reading on our servers, and deleting the reading on our servers does not remove your device copy. You can open or remove your saved copies at any time from Menu, Saved on this device.

16. What prompted a check

Before you check an account other than your own, you may choose what prompted the check from a short list (for example signals that could resemble impersonation, a fabricated identity or a scam, automation, harassment or hate, or mass false reporting) and add a short note. This is optional. If you give it, we store your selection and note with that evaluation.

We use it to point the automated assessment of the account at those questions, so that the report can say, for each one, what the public evidence in that check shows for and against it, and we use the selections, counted together across many checks and without your note, to check and improve how well our method works. It is part of the information sent to xAI for the Grok assessment described in Final score and Grok assessment. Your selection does not change the score, its weights or the conclusion.

Your selection, your note and the answers to them are shown only to you in your own report. They are not shown on a shared or public report, they are not shown or sent to the account you checked, and they are deleted with the reading. Please do not include personal information about anyone in the note.

17. Why you checked an account

Separately from section 16, when you check an account that isn’t your own we record why, when, your account, the account checked, the policy versions you accepted, a one-way coded form of your network address and your browser type. It is a record of lawful use only: it never changes the check, price or result and is never shown to the account you checked. We keep it 3 years, also after you delete your account; any text you type is encrypted. We may disclose it, and other records, if required by valid legal process such as a subpoena or court order, or in good faith to prevent imminent physical harm (see section 18).

We may disclose information we hold, including check records, reasons for checks and payment records, when we believe in good faith it is required by valid legal process (such as a subpoena, court order or search warrant), to respond to an emergency involving a risk of death or serious physical harm, or to protect authentix, our users or the public from fraud or misuse. Where the law allows and it is appropriate, we try to tell you first.

19. Ara, the site assistant

Ara, the site assistant (disclosure version 2026-10-16-v13). Ara answers support and guidance questions by text and, only if you turn her voice on, by voice. Voice is off until you tick a separate consent box and choose Enable voice; your browser then asks for microphone permission, and Ara runs a short microphone test that stays in your browser. Voice is hands-free: while voice is on, your microphone stays on and the audio it picks up is streamed continuously to our voice provider, xAI, not only while you speak, so that xAI can detect when you start and stop talking and transcribe what you say. Streaming stops when you mute the microphone, pause listening or end voice, voice ends by itself and your microphone is released 15 seconds after you or Ara last spoke, and listening pauses when the page stays in the background; while Ara is speaking, quiet sound (such as her own voice from your speaker) is not sent. Ara does not answer a spoken turn until our server has checked it under our conduct rules. If hands-free listening is not available in your session, voice falls back to push to talk, and your microphone is used only while the talk button is on. Your speech is streamed to xAI to be transcribed and answered. xAI Zero Data Retention is not enabled for our account, so under xAI’s terms xAI may keep voice requests, responses and transcripts for up to 30 days to monitor for abuse and misuse (see x.ai/legal). authentix does not store any audio. Spoken turns appear as captions in your browser and are not saved by authentix, except a question Ara looks up for you, which is kept like a typed support message. Typed messages and looked-up questions are stored with emails, X handles and phone numbers removed, to answer you, to review unanswered questions and to prevent abuse. When you are signed in and ask about a report, Ara is given a short summary of that report only if our server confirms it is yours. Refund requests Ara submits are kept with the records checked and an append-only log of each decision. If a conversation is escalated to the owner (you ask for an owner review, or it ends because of abusive language or a threat), the owner receives an email with the conversation's transcript, including captions of anything spoken, and any name, email or phone number you chose to leave. Escalations are kept until the owner closes them and are deleted 90 days after that; a count of warnings and ended conversations is kept as an append-only record to prevent abuse. If the owner reviews an account for blocking, the request (reason, warning history and transcript) and any appeal you send, with any contact details you add, are kept with an append-only record of each decision until the matter is closed, then for 90 days. When you open, close and approve the Privacy Policy, Terms or Disclaimer, we record which version, the time (UTC and the local time your browser reports) and your account, so you and we can see exactly what you agreed to. You can turn Ara's voice and tips off at any time with the switch in the help window; the setting is kept in your browser.

20. If your account was checked

If someone checked your X account, a report describes signals in your public posts and profile and gives a likelihood, not a statement of fact about you. We only use public information and the reason the person gave for the check. You can ask us what we hold about your account, ask us to correct a mistake, dispute a result, or ask us to stop checking your account (an opt-out) by emailing kellyhorak@authentix-account.com from an address we can verify, or through the ? help button. We may keep a minimal record so the opt-out keeps working, and records we must keep by law or to handle a dispute or misuse.

21. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the “Last updated” date above. Every revision is listed, with its date and time, in the legal change log, and earlier versions are kept in the legal archive.

22. Contact

Dovewood Capital, LLC
d/b/a authentix
Fort Worth, TX 76109
Support: use the ? help button on authentix-account.com
Email: kellyhorak@authentix-account.com

© 2026 Dovewood Capital, LLC. All rights reserved.