Start 7-day free trial

Privacy Policy

Effective October 30, 2026

This Privacy Policy explains how Inflight Technology LLC ("we", "us") collects, uses, and protects information through Squawk Secret, including our website at squawksecret.com and the Squawk Secret service. A "squawk" is a one-time, encrypted message or file sent through Squawk Secret. We do not sell personal information, we do not share it for advertising, and we do not use advertising or analytics trackers.

Our role

For information about account holders, such as your name, contact details, and billing, Inflight Technology LLC decides how it is used and is responsible for it.

For the content you send and collect through Squawk Secret, and for information about the people you send it to or collect it from, you (or your organization) decide what is sent and to whom. We handle that information only to operate the service on your behalf, as described here and in our Terms of Service. If you received a Squawk Secret link or request and have questions about what was shared with you or asked of you, please contact the person or organization who sent it.

Information we collect

When you create an account

  • Your first and last name, email address, mobile phone number, and mailing address.
  • A password, which we store only as a scrypt hash and cannot read.
  • If you turn on two-step verification, the setup key for your authenticator app (stored encrypted) and your recovery codes (stored only as one-way hashes).
  • Confirmation that you verified your email address and mobile number, and when.
  • Your organization's name, and your role in it.

When your company uses single sign-on (Business plan)

  • If your organization signs in with Microsoft 365, Google Workspace, or Okta, we receive your name, email address, and account identifiers (such as your Microsoft tenant and user IDs, your Google account ID and Workspace domain, or your Okta user ID) from your company's identity provider. We do not receive your password or access to your mailbox, files, or other data.
  • For Okta, your organization's Okta domain and the client ID and client secret your administrator enters. We store the client secret encrypted.
  • The email domains your organization verifies, and the DNS verification record used to verify them.

When your organization uses the API (Business plan)

  • API key names, the first characters of each key (the full key is stored only as a one-way hash), allowed networks, and when and from which IP address each key was last used.
  • Webhook endpoint addresses and delivery results. Webhook notices contain an item's ID, your reference, and times, and for a Squawk Drop the name of the Squawk Drop, the sender's email address, the topic, and the number of files; they never contain the contents of anything sent or a link to it.
  • If your systems use the API to collect request responses or Squawk Drop items, we return them still encrypted, exactly as the sender's browser encrypted them, together with the sender's email address, topic, time, and IP address. Your systems decrypt them with a key that you hold and we never receive. We record when an API key fetches items, downloads files, marks items done, erases them, or changes approved senders.
  • The reference your system sends with each squawk, such as an employee or ticket number.

When you invite a team (Business plan)

  • The email addresses you invite, and the first and last names, email addresses, and roles of team members.
  • Which team members can open each Squawk Drop and the role each has there, and, for someone invited to a Squawk Drop before they have joined the team, their email address and the role waiting for them.
  • Your organization's logo, if you upload one. It is shown to people who open your team's links and in emails sent on your behalf.

When you pay

  • Your plan, seat count, subscription status, and renewal date, and identifiers for your customer and subscription records at Stripe.
  • We send Stripe your name, email address, mobile number, and mailing address so your invoices are accurate and to help prevent fraud. Your card number goes directly to Stripe. We never receive or store it.
  • A fingerprint Stripe provides for your card (not the card number), so each card can be used for only one free trial.

When you send a squawk

  • The content itself (text and files), stored only in encrypted form. Squawks created in the app, and responses to requests, are encrypted in the sender's or responder's browser before they reach us, so we never receive their contents or the keys to read them. Squawks created through the API are encrypted on our servers as they arrive. In every case, the key needed to decrypt a squawk is part of the link and is never stored by us. If you ask us to email a link, it passes through our mail system to the recipient without being stored.
  • Settings and records about it: when it was created, its expiration and view limit, whether a passphrase is required, the file names and sizes of any attachments, who created it, and the IP address it was created from.
  • Timing you choose, such as a time before which it can't be opened.
  • Recipient email addresses, if you ask Squawk Secret to email the link for you, along with whether the email was delivered.
  • Access restrictions, if you use them: the email addresses allowed to open a squawk (we email each person a one-time code when they ask to open it, and record which address was verified) and the IP addresses or networks it may be opened from.

When you create a request

  • Request templates you save, which your organization's members can reuse.
  • The subject and message you write for the request, which are shown to the person responding and are not encrypted.
  • The responses you receive (text and files), stored in encrypted form. The names, types, and sizes of files in a response are stored unencrypted so you can see what was sent.

When someone opens your link or responds to your request

  • The time, IP address, browser information, and outcome of each attempt to open a squawk, and the time and IP address of each response to a request. This record is shown to the sender so they can confirm who accessed what and when.

People who open Squawk Secret links or respond to requests do not need an account and are not asked for any other information.

Secure chats

  • Messages, credentials, and files in a secure chat are encrypted in each participant's browser; we store them only in encrypted form and cannot read them. They are erased when the chat is closed or reaches its time limit (at most 7 days).
  • For each participant we keep their email address, the name they choose to show, and when they were invited, confirmed their email, and joined. This activity record, without any message contents, is kept for up to one year after the chat ends for the organization's audit trail.

When someone sends to a Squawk Drop

  • The sender's email address as they enter it, the topic they choose, the time, and their IP address, shown to the people at the business who are allowed to open that Squawk Drop. What they send is end-to-end encrypted and can be read only by that business. Items are erased after the period the business chooses (at most 365 days).
  • A business can have several Squawk Drops and chooses which of its team members can open each one. Each Squawk Drop has its own encryption key, which is kept in the browsers of those team members. For each browser a team member uses to open a Squawk Drop we store a public key, a general description of the browser (for example, "Chrome on Windows"), and when it was last used, along with copies of the Squawk Drop's key that are sealed to that browser and that we cannot open.
  • So that a large upload can continue after a lost connection, the sender's browser keeps a record of an unfinished upload on the sender's own device (the upload's encryption key in a form that cannot be exported, an upload token, and each file's name and size). It is removed when the upload finishes and is not used after 24 hours. The encrypted parts of an unfinished upload that have reached us are deleted within about 26 hours.
  • If the business accepts items only from approved senders, it keeps a list of approved email addresses or domains, and we email senders a one-time code to confirm their address before they can send.

When you use Squawk Vault (Business plan)

  • Squawk Vault stores files for you until you delete them. Each file is encrypted in your browser before it is uploaded, with a key that only you can unlock. We store the encrypted files, each file's size and the date it was added, and how much of your storage you have used. File names and types, and the names of any folders you make, are encrypted too, so we cannot see them.
  • Your vault's key is stored only in sealed form: once sealed with a key made from your passphrase and once sealed with your recovery key. Your passphrase and recovery key never leave your browser and are never sent to us, so we cannot open your vault, reset your passphrase, or recover your files, and neither can the administrators of your organization.
  • While your vault is unlocked, its key is kept in your browser for that tab, or on that browser if you choose "Keep the vault unlocked on this browser". Locking the vault removes it.
  • We record when a vault is created or erased, when its passphrase is changed or recovered, and when a file is added, downloaded, or deleted, identified by a file number and size, never by name.

When you use Squawk Links, or follow one (Business plan)

  • Squawk Links are short links and QR codes that a business makes to point at a web address of its choosing. We store the link's name, the address it goes to, who made it, and when.
  • When someone follows a link or scans its code, we send them on to that address and record: the time, whether it was a scan or a click, the kind of device, operating system and browser (worked out from what the browser tells us), and, for a click, the website it was clicked on if the browser says. We keep only that site's name, never the page.
  • We work out roughly where the person is (their country, and with some location data their region and city) from their IP address at the moment they follow the link, using a location database kept on our own servers (DB-IP). Only that answer is stored; the address is not sent to anyone for this.
  • We do not store the IP address of a person who follows a link. To count visitors we keep a one-way value made from the address and browser. It changes every day and is different for every link, so it cannot be turned back into an address or used to follow anyone from one link, or one day, to another.
  • We set no cookie when someone follows a link, and we do not pass on to the destination which site they came from.
  • The business that made the link can see these records and totals for its own links. Visits by link previews and other automated tools are recorded and left out of the totals.

When you use Squawk Keeper (Business plan, beta)

  • Squawk Keeper is a password keeper. It is in beta and is turned on for an organization, or for particular people in it, at their request. It stores what you put in it until you delete it: logins, payment cards, bank accounts, API keys, server and database details, Wi-Fi passwords, software licenses, identity documents, PINs, and notes. Each entry is encrypted in your browser, so we store only sealed blobs, their size and their dates. We cannot see what kind of entry it is, or a name, username, password, web address, card or account number, note, or authenticator key, and neither can the administrators of your organization.
  • Your keeper's key is stored only in sealed form: once sealed with a key made from your keeper passphrase and once with your keeper recovery key. Neither leaves your browser, so we cannot open your keeper, reset your passphrase, or recover your entries.
  • A shared folder is readable by the teammates it is shared with. For this we store, for each person, a public key, and their private key sealed with their own keeper key; and for each folder, a copy of its key sealed to each member. We record who is in each folder and what they may do there. The folder's name is encrypted with the folder's own key, so we cannot read it.
  • If your account owner turns on an organization recovery key, each shared folder key is also stored sealed to it, and whoever holds that key can give a shared folder back to someone. Everyone in the organization is told in the app while it is on, use of it is recorded, and everyone in the folder is emailed. It never covers anyone's personal entries.
  • While your keeper is unlocked, its key is kept in your browser for that tab, or on that browser if you choose to keep it unlocked there. Locking the keeper removes it.
  • A request template can say how a response is saved to Squawk Keeper: the kind of entry, a name pattern, and which answer fills which field. We store only that setup. When you choose Add to Keeper on a response, the entry is built and encrypted in your browser from the decrypted answers, the same as any other entry.
  • When you import from another password manager, the file you choose is read in your browser. It is not uploaded; only the entries made from it are sent to us, encrypted like any other entry.
  • Authenticator codes are worked out in your browser from the key stored in the entry. We never see the key or the codes.
  • The browser extension. To connect the extension we store a one-time pairing code in hashed form for five minutes, with the IP address that asked for it, and then issue the extension a sign-in token that can only read your encrypted keeper entries and save new ones. The extension keeps that token, your email address, your settings, and the list of sites you have told it never to ask about, in your browser. While it is unlocked it also keeps your keeper key and decrypted entries in the browser's memory, until it locks or the browser closes. To offer a saved login it compares the address of the page you are on with your entries, and to offer to save a new one it reads the username and password you type into a sign-in form. To fill a payment card you choose, it looks in each frame of the page for card boxes and hands the card only to the frames that have them, which is often a frame run by the shop's payment company. All of this happens on your own device: the sites you visit and what you type there are not sent to us, and a login reaches us only if you choose to save it, encrypted first.
  • We record when a keeper is set up, changed, recovered, or erased, when a browser extension is connected, when an entry is added, changed, moved, or deleted, and when a shared folder is made, shared, handed on, recovered, or deleted, identified by numbers rather than names.

If you use the Windows notifier

  • For each computer you connect, we keep its name, when it was connected, and when it last checked for notifications. Its connection is stored only as a one-way fingerprint and can fetch notifications and nothing else. You can disconnect any computer in Settings.

Feedback you choose to give

  • Trial survey answers: after your first squawk or request during a free trial, we may ask a few optional questions about your experience, in the app and once by email. Answers are linked to your account and used only to improve Squawk Secret. You can decline, and we won't ask again.

Security and activity records

  • Sign-ins, sign-in failures, password resets, verification steps, team changes, and billing events, with the time, IP address, and browser information. When your account signs in from a new device, we email you the time, browser, and IP address.
  • Our web servers also keep standard technical logs of requests to the website, including IP addresses.
  • To protect the service from attacks, we record requests that look hostile, such as repeated failed sign-ins, probes for weaknesses, and requests turned away, with the time, IP address, the country it is in (worked out on our own servers from a location database), and the address requested. An IP address that crosses a limit is blocked for a time. We also note which countries each account signs in from, to spot sign-ins from somewhere new. The service may accept connections only from certain countries; if your organization adds a trip under Travel, we keep the country, the dates, the note you enter, and who added it.

When someone reports a link

  • The reason and any details the reporter enters, and the reporter's IP address to prevent misuse of the report form. Reports are not shared with the sender.

When you contact us

  • The information you include in your message.

When you use the Outlook add-in

  • Only when you use it, the add-in reads the recipients and subject of the email you're writing (to lock a link to the recipients and suggest a request subject) and the attachments you choose to send securely. Attachments and anything you type are encrypted in the add-in before they're uploaded, the same as on our website.
  • We keep a record that your Outlook is connected (when it was connected and last used) so you can disconnect it in Settings. We don't read your mailbox or other emails.

When you use the Microsoft Teams app

  • The Teams app encrypts what you type in its window before uploading it, the same as our website. To add the card to your message, the finished link (including its key) passes through our server and Microsoft Teams; we don't store it, and it stays in your chat like a link in an email. We keep a record that your Teams is connected (when it was connected and last used) so you can disconnect it in Settings.
  • Squawk Guard: in channels and group chats where the Teams app has been added (with the owner's approval), Microsoft Teams sends each message to our server so it can be checked for passwords, card numbers, Social Security numbers, and similar. Messages are checked in memory and are never stored or logged; if something is found, the app replies with a warning that names only the kind of information. In Outlook, Squawk Guard's check runs inside Outlook on your computer, and the email isn't sent to us.
  • If your organization sets up Teams channel notifications, we send details like a squawk's reference, view count, and time to the channel address your organization provides.

When you use the AI assistant

  • Where the optional in-app assistant is available and you use it, your questions, the conversation so far, and the account details it looks up to answer you are sent to our AI provider, Anthropic, to generate its answers. Its lookups include only status, dates, counts, and titles (for example, whether a link was opened and when); it never has access to the contents of squawks, request responses, Squawk Drop items, or chats.
  • We don't store your questions or its answers. The conversation is kept only in your browser tab. We keep a daily count of how many questions each person asks, to apply a limit.
  • Please don't type passwords or other secrets into the assistant. Messages that look like secrets are refused before they're sent. Account owners can turn the assistant off for their whole account: in Settings on Individual and Family plans, or on the Policies page on Business.

When you use Squawk Back to confirm who you're talking to (Business plan)

  • The email address or mobile number a team member enters for the person being checked, and optionally that person's name. We store the address or number only in masked form (for example, j•••@example.com), plus a one-way fingerprint used to limit how often one person can be contacted. For a check sent by text, the number is kept encrypted only while the check is open, and deleted when it ends.
  • The one-time code: stored only as a one-way hash, or, when a team member must read it aloud, encrypted until the check ends. Codes sent by text are generated and checked by Twilio, and we never see them.
  • The result (verified, not verified, or the person said it wasn't them), how, and when, and which team member ran the check.
  • We send the person an email or text on the organization's behalf, naming the organization and the team member.

When you use two-person protection (Business plan)

  • Requiring approval: the approvers' email addresses, the reason the sender gives, and the decision, who made it, when, and any note. Approvers see who is sending, to whom, and why, but never the contents.
  • Two people together: both people's email addresses (each confirms theirs with a one-time code). To open it, one person's browser sends their half of the key, encrypted so that only the other person's browser can read it; we relay it without being able to read it, and delete it as soon as it's collected, or after 15 minutes.

When you use Certified delivery (Business plan)

  • For each attached file, its name, size, and a SHA-256 fingerprint, computed in the sender's browser before the file is encrypted. A fingerprint identifies a file but doesn't reveal its contents. We record whether text was included, but never fingerprint text, because a short secret's fingerprint could be guessed.
  • When someone requests a Certificate of Delivery, we keep the facts it certifies: the sender's name and email address, the organization, the file names, sizes, and fingerprints, the protections used, the recipients' email addresses, and each attempt to open it (time, IP address, browser, and the email address confirmed with a code). We sign these facts so they can't be altered.
  • Anyone who has a certificate's ID can view those facts on our verification page. Organizations decide whom they give certificates to. Verification pages are not listed in search engines.

Compliance evidence packs (Business plan)

  • At an administrator's request, we compile reports from the records described in this policy (for example, how many links were locked to recipients, and how many team members use two-step verification). No additional information is collected to produce them.

How we use information

  • To provide the service: creating and delivering squawks and requests, erasing them on schedule, managing teams, and showing senders their access records.
  • To verify accounts and prevent abuse: confirming your email address and mobile number, requiring a payment card before a plan starts, rate limiting, and investigating reports of misuse. This keeps the service from being used by throwaway accounts to send harmful content. For support and to investigate misuse, a small number of authorized Inflight Technology LLC staff can view the records about squawks and activity described in this policy (such as who created a link, when, from which IP address, and whether it was opened) across organizations. They cannot see the contents of anything sent, and each time they open that view it is recorded.
  • To bill you through Stripe.
  • To communicate with you: service email only, such as verification, password resets, invitations, read receipts, and important changes to the service or these policies.
  • To keep the service secure and to comply with the law.
  • To produce records you ask for, such as Certificates of Delivery and compliance evidence packs.

Text messages

We text account holders only to send verification codes when they sign up or change their number. When a Business customer uses Squawk Back, we also text the mobile number the customer enters, on the customer's behalf, with a one-time code or a message naming the organization. We do not send marketing texts. Message and data rates may apply. Mobile information is not shared with third parties or affiliates for marketing or promotional purposes.

How we share information

We share information only as follows:

  • Service providers that operate parts of Squawk Secret for us, under agreements that limit their use of the information:
    • Stripe: payment processing and billing. Stripe's handling of your payment details is governed by its own privacy policy.
    • Twilio: sending and checking mobile verification codes, checking that a number is a valid US mobile number, and sending Squawk Back codes and messages to the numbers our customers enter.
    • Microsoft, Google, and Okta: signing in members of organizations that use single sign-on.
    • Microsoft: delivering email sent by Squawk Secret, and, for organizations that use our Microsoft Teams app, relaying Teams messages and cards between Teams and our service.
    • Let's Encrypt: issuing HTTPS certificates for custom domains our customers connect (it receives the domain name, which is recorded in public certificate logs).
    • IONOS: hosting our servers.
    • Wasabi: storing encrypted nightly backups of our service and, where used, files sent to Squawk Drops and files kept in Squawk Vault (encrypted in the browser before upload; file names are encrypted too).
    • Anthropic: generating the in-app AI assistant's answers, where it's available and used (questions, the conversation, and the account details it looks up; never the contents of secrets).
  • Within your organization: Business plan administrators can see their team members' names, email addresses, and roles. The owners, admins, and managers of a Squawk Drop can see which team members can open it, and everyone who can open it can see the items sent to it and who sent them.
  • Within your organization, for two-person protection: approvers see who is sending, to whom, and why.
  • With senders: the access record described above for links they created.
  • With anyone a customer gives a Certificate of Delivery to: the facts it certifies, on its verification page.
  • At your organization's direction: when a Business organization connects Squawk Secret to its other systems, through our API, webhooks, or a security event feed to a SIEM (such as Splunk or Microsoft Sentinel), we send the information it has set up to the destinations it chooses. A security event feed contains records of activity in that organization's account: its members' email addresses, and the time, IP address, and browser information of sign-ins and of people who open its links, respond to its requests, send to its Squawk Drop, or join its chats. It never contains the contents of anything sent or received. The organization chooses and controls those destinations, and how they store and use the information is governed by its own arrangements with them, not by this policy.
  • For legal reasons: when required by law or legal process, or when needed to protect the rights, property, or safety of our users, the public, or Inflight Technology LLC. Because we never store the keys to squawks, we cannot decrypt squawk content for anyone, including in response to legal demands.
  • In a business transfer: if Inflight Technology LLC or Squawk Secret is involved in a merger, acquisition, or sale of assets, information may transfer as part of that transaction, subject to this policy.

Cookies and browser storage

We use only what the service needs to work:

  • sc_session: keeps you signed in. Expires after 12 hours.
  • sc_plan: remembers the plan you chose while you finish signing up. Expires after 30 days, or when you start checkout.
  • sc_authtx: used only during staff single sign-on. Expires after 10 minutes.
  • sc_theme: remembers your light or dark mode choice. Expires after one year.
  • sc_device: a random identifier for your browser, so we can alert you when your account signs in from a new device. Expires after about 13 months.

We use no advertising, analytics, or cross-site tracking cookies. Payment pages are hosted by Stripe, which sets its own cookies under its own policy. Because we do not track you across sites, browser "Do Not Track" and Global Privacy Control signals do not change how we handle your information.

How long we keep information

  • Squawk content is erased within minutes after its view limit is reached or it expires. Squawks can last at most 30 days.
  • Request responses are erased when you close the request or when it expires, whichever comes first. Requests can stay open at most 365 days (a year is meant for reusable forms).
  • Records about squawks and requests (settings, access records, recipient email addresses, file names, request subjects and messages, and response times and IP addresses) are deleted 12 months after the squawk was erased or the request closed.
  • Security and activity records are deleted after 12 months. Web server logs are deleted after 180 days. Records of hostile requests and address blocks are deleted after 30 days. Trips added under Travel are kept with your organization's records.
  • Squawk Back records are deleted after 12 months, and when the organization is deleted. When a team member deletes their account, their name is removed from the checks they ran.
  • Halves of keys relayed for two-person protection are deleted as soon as they're collected, or after 15 minutes.
  • Certificates of Delivery are kept for six years from when they were issued, so that anyone relying on one can still verify it, including after the account that requested it is deleted. Because they are signed, their contents can't be changed during that time.
  • Squawk Keeper entries are kept until you delete them, and go when you erase your keeper or your account is deleted. Extension pairing codes that have expired are removed whenever a new one is made. If Squawk Keeper is turned off for you or withdrawn while it is in beta, your encrypted entries are kept so that you can be given access to copy them out, and are deleted when you erase your keeper or delete your account. Entries in a shared folder belong to the folder: they stay when a member leaves and are deleted with the folder. A folder nobody can open any more is kept rather than deleted, in case the person who held its key returns.
  • Squawk Links records of scans and clicks are deleted after 12 months, and at once when the link or the organization is deleted.
  • Squawk Vault files are kept until you delete them. If you leave your organization, or it is deleted, your vault is erased 7 days later; deleting your account erases it immediately. An upload that never finished is removed within about a day. Vault files are held in file storage and are not part of our service backups, so a deleted file is gone as soon as it is deleted.
  • Backups of the service are kept for 90 days and then deleted. Information you delete, or that expires, may remain in backups until they are deleted.
  • Account information is kept while your account is open. You can delete your account at any time in Settings: this immediately erases the squawks and requests you created and removes your name from the records about them, and if you own your organization, cancels its subscription and deletes it. You can also ask us to delete your account, and we will do so within 30 days. Records we must keep for tax, accounting, or legal purposes, such as billing history, security records within their retention period, and Certificates of Delivery, are kept until their retention periods above end.

Erased content cannot be recovered, by you or by us.

How we protect information

Squawks and request responses are encrypted with AES-256-GCM, and the keys to squawks are never stored. All traffic uses HTTPS. Passwords are hashed with scrypt. Access is logged and rate limited. Our Security page describes these protections in detail, including exactly where encryption takes place. No system is perfectly secure, but we work to protect your information and will notify affected users of a breach as required by law.

United States only

Squawk Secret is offered only to individuals and businesses in the United States. Creating an account requires a US mailing address, a US mobile number, and a payment card, and we do not market or offer the service to people in the European Union, the United Kingdom, or any other country. Our servers are located in the United States, and information is stored and processed there.

People who receive a Squawk Secret link or request may open it from anywhere. The information recorded when they do is described above and is handled on behalf of the account holder who sent it.

Your rights and choices

You can update your information and cancel your subscription from within Squawk Secret. You can also ask us to:

  • give you a copy of the personal information we hold about you,
  • correct information that is wrong,
  • delete your account and personal information (you can also do this yourself in Settings), or
  • stop or limit certain uses of your information.

Depending on the state you live in, such as California, Colorado, Connecticut, Virginia, and others with consumer privacy laws, you may have some or all of these rights by law, along with the right to receive your information in a portable format. We will not treat you differently for exercising your rights.

To make a request, email support@squawksecret.com from the address on your account. We may need to confirm your identity before acting on a request, and we will respond within the time required by law, generally within 45 days. You may use an authorized agent where the law allows. If we deny your request, you may appeal by replying to our response.

If you received a Squawk Secret link or request and want information about it, please contact its sender; we can only confirm our own records about that link.

Children

Squawk Secret is a business service and is not directed to children under 16. We do not knowingly collect information from them. If you believe a child has given us information, contact us and we will delete it.

Changes to this policy

We may update this policy as Squawk Secret changes. We will post the new version here with a new effective date, and for material changes we will notify account owners by email before the changes take effect.

Contact us

Inflight Technology LLC
14 Commerce Street, Suite 106
Flemington, NJ 08822
Email: support@squawksecret.com