Privacy Policy

1. Scope

This Policy applies to every Bodek service and to its websites, mobile and desktop apps, APIs and support interactions: Bodek Accounts, Bodek Files (including the iPhone, Android and desktop apps), Bodek Forms, Bodek SMS, Bodek Games, Bodek Tools, Bodek Developers, the Bodek API, our billing pages, this Help Center, and the Bodek Solutions website at bodek.us.

It does not govern third-party storage providers, payment processors, carriers, app stores, websites or services, which have their own terms and privacy practices. It also does not govern what a Bodek customer does with information they collect through the Services: if you answered someone's form, received a text message sent through Bodek SMS, or use an account your employer owns, that customer decides what is collected and why, and section 11 explains our role.

2. Information we collect

• Account and billing information: name, email address, phone number if you add one, profile image, organization, workspace and business details (including a company name and tax identifier if you open a business account), subscription and plan status, and transaction records. Our payment processor handles your full payment-card details; we receive only customer and subscription references and limited billing information, never the full card number.
• Your content: files, folders, filenames, albums, album messages, photos and videos, forms and their responses, uploads, text and multimedia messages, group and member names, game chat, saved tool items, and other material you upload, import, create, send or direct us to process.
• Usage and device information: IP address, browser and device details, login and security events, approximate location derived from IP address, feature activity, API and webhook activity, cookies, session identifiers, and server logs. We also keep our own first-party usage counters, such as session start and end, upload throughput, message counts and error messages the page reports. We do not use a third-party analytics, advertising or tracking service anywhere in the Services.
• Security information: password hashes, two-step verification methods, passkey public keys, recovery codes, remembered-device records, failed sign-in attempts and lockouts, and the IP address and user agent attached to them.
• Communications: support requests, contact-form submissions, feedback, copyright notices and other messages you send us, together with what the form reports about your visit (see section 3).
• Diagnostics: crash and freeze reports from the mobile apps, as described in section 7.

We collect information from you, your organization or workspace administrator, your device, your use of the Services, people who send a message to a number you use, people who answer a form you publish, and providers you connect at your direction.

3. What each service collects

Bodek Accounts

Your identity across every Bodek service: the account and security information above, the sites and apps you have signed in to, the sessions and devices signed in, and — if you use "Sign in with Bodek" at a third-party application — a record of the authorizations you granted and the scopes they cover.

Bodek Files

• File and photo information: size, type and dates; the metadata stored inside your photos and videos, including the date taken and, when the file carries them, the GPS coordinates that we also turn into a place name for the Places view; thumbnails and preview or streaming copies we generate; extracted document and media metadata; and a search index built from the above. See section 6 for what we do with location and faces.
• Face data: if photo organization is used, for each face we detect in a photo or video we store a numeric face descriptor (a list of 512 numbers computed from the image of that face), the face's position and a few landmark points, and the group of similar faces it was placed in, along with any name you give that group. This is data derived from a person's face, so we treat it as sensitive. See section 6.
• Connected-service information: provider type, account identifiers, encrypted access credentials or tokens, bucket or folder configuration, connection status, and data needed to transfer files to and from storage you choose.
• Search history: your most recent searches (currently the last twenty) so the search box can suggest them back to you. You can clear them.
• Signed-in devices: for each device signed into the Service, a device name and model, the platform, the operating-system and app version, the IP address it last used, and, if you allow notifications, a push token. See section 7.
• Sharing and collaboration: album members and invitations, shared links and their settings, reactions and messages, reports and blocks, and workspace membership and roles.

Bodek Forms

The forms you build and the responses you receive. With each response we record the answers submitted, any files uploaded, the respondent's IP address, an approximate location derived from it, the browser user agent, the time, and — where the respondent was signed in or the form asked — their account or email address. Where a form collects a signature, we store what the respondent entered with those submission details. The customer who published the form decides what it asks; we hold the responses for them (section 11).

Bodek SMS

• Messages: the phone numbers of sender and recipient, the full text of each message, direction, status and timestamps, the group it belongs to, how it was sent (website, API, text command, flow or system notice), the API key used, segment counts and any delivery error.
• Multimedia (MMS): pictures and other media sent or received, their type, size, dimensions and a content hash, stored so the conversation can display them.
• Groups and members: group names and settings, member phone numbers, display names, roles and join or leave history, including members you import from a list or CSV.
• Calls: for calls to and from your numbers, the other party's number, direction, outcome, which rule applied, the duration and timestamps. We do not record the audio of calls.
• Text menus (flows): the flow you built, each session's step-by-step progress, the answers a person texted in, and a log of what the flow did, together with any opt-out we recorded for that number.
• The equipment that sends and receives: for each number, the status of the device that serves it — its name, manufacturer, model, operating-system and app version, battery and charging state, network, the IP address of its last request, the time it was last seen, and link events such as connects, drops and errors.

Bodek Games

Games you create or join, the other players, invitations, moves and game state, scores and results, and in-game chat messages. Games against the computer are played by our own engine; nothing about a game is sent to a third-party AI service.

Bodek Tools

What you type into a tool in order to produce its output — for a QR code, the link, text, Wi-Fi details or contact details you entered — plus any logo image you upload and the saved items you keep in your account. The tools work without an account; saved items require one.

Bodek Developers and the Bodek API

Your API keys (stored only as a hash, with a visible prefix), their names and scopes, the application and OAuth client details you register including redirect URLs and client secrets, access requests and grants, and request logs: the time, endpoint, response status, IP address and key used for each call, plus an audit trail of administrative changes. We keep per-key usage counts for rate limiting and billing.

Billing

Your plan, subscription state, invoices and payment history, references to your saved payment methods held at our payment processor, scheduled recurring payments, and the records our accounting obligations require. Full card numbers never reach our servers.

This Help Center and bodek.us

Help pages are public and set no sign-in cookie. When you send the contact form, we collect what you type plus details about the visit so that a person can answer you: your IP address and an approximate location looked up from it, the browser user agent, the page you were on and the page that referred you, the campaign or link parameters in the URL if any, your screen and window size, time zone and local time, language, platform, connection quality, color-scheme and reduced-motion preferences, whether cookies and storage are available, and basic timing of how the form was filled in (which helps us tell a person from a bot). This is used only to answer and to keep the form usable; we do not build profiles with it.

4. How we use information

We use information to provide, authenticate, operate, maintain, bill, secure, troubleshoot and improve the Services; store and transfer content; generate previews, thumbnails, streaming copies and search results; organize photos; send and receive the messages and handle the calls you ask us to; deliver forms and collect their responses; run games and tools; enable sharing, collaboration, APIs, OAuth applications and connected storage; communicate service, security, billing and support messages; measure usage against plan limits; detect, investigate and prevent fraud, abuse, spam and security incidents; enforce our Terms and policies; comply with law and respond to legal process; and protect users, recipients, Bodek and others.

We do not sell your information, we do not share it for cross-context behavioral advertising, we do not use it for advertising at all, and we do not use the content of your files, forms, messages or games to train machine-learning models for anyone else.

5. Automated processing

Several features work by processing your content automatically, inside your own account, on systems we operate: building the search index, extracting file and media metadata, generating previews and thumbnails, grouping photos by face and by place (section 6), running the text menus and keyword rules you build in Bodek SMS, checking messages against the limits and opt-outs that apply, playing the game engine's moves, and screening for abuse, spam and prohibited content. None of this involves a third-party AI service, and none of it makes a decision about you with legal effect. A human at Bodek does not read your content as part of these features; the limited cases in which a person may need to look at content are in section 10.

6. Faces, places, and our second server

Faces. When a photo or video is processed in Bodek Files, we detect the faces in it and compute a face descriptor for each one: a list of 512 numbers derived from the appearance of that face, stored together with the face's position in the image and a few landmark points. Descriptors that match closely enough are grouped into a "person," and you can name, merge, hide or delete a group under Photos › People.

Face descriptors and groups are used for exactly one purpose: grouping the photos inside your own library or workspace so you can browse them by person. We do not use them to identify anyone outside that library, to match against other users' photos, for advertising, or to build facial-recognition profiles, and we never sell or share them. Faces of people who do not have a Bodek account are processed the same way, because they appear in the photos you upload: if you upload photos of other people, you are responsible for any notice or consent the law where you live requires. Face data is deleted when you delete the photo it came from, when you delete the person group, and in full when your account is deleted (section 12).

Places. Most phones and cameras write the location where a photo was taken into the photo file itself. When you upload such a file we read those coordinates, store them, and turn them into a place name so the Places view can group your photos by where they were taken. Our apps and websites request no location permission and never read your device's location. The coordinates come only from inside the files you upload, so a photo with no coordinates in it gives us none.

Our second server. Face detection and the Create-video renderer run on a second machine we operate, at video.files.bodek.us. To do their work they fetch the specific photos or videos being processed from the main server over an encrypted HTTPS connection, using a single-use link that is valid only for that one job, and they keep the media only as long as that job needs it. That machine is ours: the same company, the same operator, under this same Policy. It is not a third party, and no third party receives your file content for face grouping or video rendering.

7. The mobile and desktop apps

Bodek Files has apps for iPhone and iPad, for Android, and for desktop computers. Everything above applies to them; this section covers what is specific to a device.

What the app tells us about the device: a device name you will recognize, the model, the platform, the operating-system version, the app version, the IP address of its most recent request, and, if you allow notifications, a push token issued by Apple's or Google's notification service so a notification can reach that device. Every signed-in device is listed under Settings › Signed-in devices, where you can sign it out remotely at any time; signing a device out deletes its push token.

Device permissions the mobile app asks for, and why:

• Photo library — to upload the photos and videos you pick, and, if you turn on camera backup, to upload new ones automatically. The app reads only what it is uploading.
• Adding to your photo library — only when you save a photo or video from Bodek Files back to the device.
• Notifications — upload and backup progress and album activity. Optional; the app works without it.
• Camera — on iPhone and iPad only, and only to scan the pairing QR code shown on the website when you sign in. The Android app asks for no camera permission at all, because that scan runs inside Google Play services.
• No location permission is requested on either platform.

The apps contain no advertising, no advertising identifier, no cross-app or cross-site tracking, and no third-party analytics or crash-reporting SDK.

The desktop sync app runs on your computer and reads only the folders you choose to sync. It reports the device name, platform, app version and sync state so you can see and manage it from the website.

Crash and freeze diagnostics. If a mobile app crashes or stops responding, it sends us a diagnostic report so we can fix the bug. A report contains the type of crash, the call stack, the app and operating-system version, the device model, and your account id so we can follow up with you. A report never contains file names, album names, people's names, search terms, or any part of the content of a file. We use these reports only to find and fix problems in the app, and we keep them for 30 days. After that the report is deleted; a de-identified summary of the crash itself — the type, where it happened and how often — carries no account id and is kept as engineering history.

8. Google user data

If you connect Google Drive as storage, or import photos from Google Photos, we access only the account and file information authorized through the permissions you grant. We use Google user data to show you your connection, and to store, retrieve, migrate or organize files as you direct. We do not use Google user data for advertising and do not allow humans to read it except with your affirmative permission for support or security, when necessary to comply with law, or when data is aggregated and anonymized for internal operations.

Bodek's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You may revoke Google access through your Bodek Files storage settings or your Google account settings.

9. Cookies

Our sites use first-party cookies for signing in, keeping you signed in if you ask us to, switching between accounts you have signed into, and protecting forms against cross-site request forgery. Your browser's local storage holds things that belong on your device, such as an unsent draft, an upload queue and the sort order you last chose. There are no advertising, analytics or third-party tracking cookies anywhere in the Services. Our Cookie Policy lists what we set and how to control it.

10. How we disclose information

We use a small number of outside providers, and only for the job named here. The full list, kept current, is at Service Providers.

• Our hosting provider — the rented servers and network the Services run on. It supplies the machines; we do not give it access to accounts or content.
• Stripe — payments and subscriptions. You enter your card details with Stripe; we receive customer and subscription references and limited billing information.
• Email delivery — our mail server sends your sign-in codes, receipts, notices and support replies to your email address.
• Mobile carriers and the phone network — when you send or receive a text message or a call through Bodek SMS. Carriers necessarily receive the numbers involved and the content of the message in order to deliver it (section 3 and the Messaging Terms).
• IP geolocation — an IP-lookup service turns an IP address into an approximate city and country for a form response or a support request. Only the IP address is sent.
• A public code CDN — our pages load the Bootstrap stylesheet and icon font from a public content-delivery network, which necessarily sees your IP address and browser when it serves those files. It receives no account information and sets no cookie for us.
• Google — when you connect Google Drive or import from Google Photos (section 8).
• Apple and Google — only to deliver a push notification to your device, if you allow notifications.
• The storage you choose — Amazon S3 or S3-compatible storage, Backblaze B2, Dropbox or Google Drive, when you connect one (Bodek Forms can keep its uploads in your own S3 or B2 bucket in the same way). Before a file leaves our server we encrypt it with our own keys, so what is stored at the provider is an encrypted object that only Bodek Files can read. The provider holds your content but cannot read it. If you store with us instead, your files are kept on our own server and encrypted there the same way.

We may also disclose information:

• to people you invite, share with, send a message to, or give a public link, and to workspace or organization owners and administrators who control that workspace;
• to the customer who published a form you answered, or who sent you a message, since the information belongs to them (section 11);
• to our own personnel, who may access content only where it is necessary to provide support you asked for, to investigate abuse or a security incident, to fix a fault, or to comply with law;
• when we reasonably believe disclosure is required by law, subpoena or other legal process, or needed to protect rights, safety, security or the integrity of the Services; and
• in connection with a merger, financing, acquisition, bankruptcy or sale of assets, subject to applicable law.

We do not sell personal information and do not share it for cross-context behavioral advertising. We may use or disclose aggregated or de-identified information that cannot reasonably identify you.

11. Business and workspace accounts, forms and messages

Where a business or another person uses the Services to collect or send information about you, that customer decides what is collected and why, and we handle it on their behalf and under their instructions:

• If you answered a form built with Bodek Forms, the customer who published it controls your response. Ask them about their own privacy practices, and send access or deletion requests to them; if you send one to us, we will refer you to them or pass it on.
• If you received or sent a text message through a Bodek SMS number, the customer who operates that number controls the conversation and the group membership. They are responsible for having your consent and for honoring your opt-out; texting STOP to the number ends automated messages from it.
• If your account, workspace or organization belongs to your employer or another organization, its owner and administrators can see and manage the content stored in it, export it, change your access and delete it, and their own policies apply to you as well as this one.

For our own account, security, billing and operational records, we act on our own behalf and this Policy applies directly.

12. Retention and deletion

We retain information while needed to provide the Services and for legitimate business, security, fraud-prevention, dispute and legal purposes. Some specific periods:

• Crash and freeze diagnostics from the apps: 30 days (section 7).
• Bodek SMS multimedia (MMS) files: 180 days, after which the file is deleted even though the message stays in the conversation.
• Bodek SMS equipment link events (connects, drops, errors): 30 days.
• Your content — files, albums, form responses, messages, groups, games and saved tool items: until you delete it, or until the account is closed or deleted as described below. Deleting a file, response, message, group or album removes it from the Services; copies may remain in backups until they are overwritten in the normal course of operation.
• Bodek Forms uploads that were never submitted: 3 days.
• Bodek Games tables: a finished game is removed 60 days after it ends, a table that was never started after 14 days, a game with no activity for 90 days, and an unaccepted invitation after 30 days.
• Accounting records — invoices, charges and customer records: kept as long as tax, accounting and anti-fraud law requires, even after an account is deleted.
• Security and server logs: kept for a limited period for security and troubleshooting, then rotated and overwritten.

Two different things can bring an account to an end, and they are not the same:

• Your subscription stops, but your account still exists. If you cancel, or your subscription lapses or is terminated, normal access to the Services ends on the effective date, and we keep the files that are available to us for a 60-day export window during which the account owner can sign in and download a full ZIP export. After those 60 days we may delete the account and the remaining content.
• You ask us to delete your account. The request starts a 5-day grace period. During those 5 days the account is locked: it will not sign in to any Bodek site or app, and existing sessions, remembered browsers and app sign-ins are ended immediately. You can stop the deletion at any point in those 5 days: sign in at accounts.bodek.us, go to Settings → Delete account, and choose Keep my account (we ask for your password or your authenticator code to confirm it is you). The account then comes back completely untouched. Simply signing in does not by itself cancel the request, so that nobody can undo your decision by opening a page. When the 5 days are up, the account and everything in it is permanently wiped: your Bodek Files content — every file, including the copies held in any storage you connected (Dropbox, Google Drive, Amazon S3, Backblaze B2 or any other provider you connected) and every thumbnail, preview and video copy we made; albums and album messages; people, face groups, and all face data; sync state; your search history; your signed-in devices and their push tokens; your two-factor methods and passkeys; webhooks; your API keys, including SMS keys; your saved payment methods; your avatar; your saved Bodek Tools items; and the games you created, their players, invitations and chat. Any scheduled recurring payment is cancelled. Organizations and workspaces you own are deleted in full; files and albums you created inside an organization owned by someone else belong to that organization and are handed to its owner rather than deleted. Bodek Forms, Bodek SMS and Bodek API data is not yet covered by this automatic deletion — if you have used those products, email support@bodek.us and we will remove it for you. There is no 60-day retention after a deletion. The 60-day export window belongs to the case above and does not apply here, so make any export you want before you ask us to delete the account.

Only two kinds of thing can outlive a deletion: limited records we have to keep to meet legal, accounting, tax or fraud-prevention duties, and copies that sit in backups or log files until they are overwritten in the normal course of operation. One thing is deliberately not deleted: files and albums you created inside someone else's organization belong to that organization, so they are transferred to its owner rather than removed along with your account.

Content stored with a third-party provider remains subject to that provider's retention and deletion practices. Disconnecting a provider does not necessarily delete data from that provider, and deleting data there may make it unavailable through Bodek Files. A message that has already been delivered cannot be recalled from the recipient's phone or from their carrier.

13. Your choices and privacy rights

Through the Services you can review or change account details and workspace settings, manage sharing links and members, sign out any device, disconnect storage providers, revoke API keys and application authorizations, clear your search history, hide or delete a person group and its face data, delete files, responses, messages, groups and games, download your content, and request account deletion.

Depending on where you live, you may have rights to access, correct, delete or obtain a portable copy of personal information, to opt out of certain processing, or to appeal a denied privacy request. To exercise a right, email privacy@bodek.us from the address on your account. We may need to verify your identity, we may decline a request where law permits or requires, and we will tell you why. We do not charge for a request or treat you differently for making one. An authorized agent may act for you with written proof we can verify. Where the information belongs to one of our customers rather than to us — a form response, a message, an employer's workspace — we will refer you to them (section 11).

Use browser controls to manage cookies, although blocking required cookies may prevent sign-in or other features. Transactional and security messages are necessary for the Services; you can manage optional communications where settings are offered. Automated text messages from a Bodek SMS number stop when you reply STOP.

14. US state privacy rights

Residents of California and of other states with comprehensive privacy laws (including Colorado, Connecticut, Virginia, Texas, Oregon, Montana and others as they take effect) have the rights described in section 13: to know and access the personal information we hold, to correct it, to delete it, to obtain a portable copy, and to appeal if we deny a request. Submit requests to privacy@bodek.us; if we deny one, you may appeal by replying to our decision, and we will respond within the time the law allows.

The categories of personal information we collect, the purposes, the categories of recipients and our retention are described in sections 2, 3, 4, 10 and 12. Sensitive personal information we may handle includes account credentials and security data, precise location contained in photo files you upload, and face data derived from your photos; we use these only to provide the feature they belong to and never to infer characteristics about you. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use or disclose sensitive personal information for purposes that require an opt-out right. We do not use personal information for profiling that produces legal or similarly significant effects. We do not knowingly collect or sell the personal information of anyone under 16.

15. Europe, the United Kingdom and Switzerland

If you are in the EEA, the United Kingdom or Switzerland, we process personal data on these legal bases: performance of a contract (providing the Services you signed up for, billing you, and supporting you); legitimate interests (securing the Services, preventing fraud and abuse, measuring usage against limits, and improving what we offer); consent where we ask for it (such as optional communications or a device permission), which you may withdraw at any time; and legal obligation where law requires us to keep or disclose something. Where a Bodek customer uses the Services to collect your data, that customer is the controller and we act as processor under their instructions (section 11).

You may have the right to access, rectify, erase, restrict or object to processing, to data portability, and to lodge a complaint with your supervisory authority. Email privacy@bodek.us.

Bodek is based in the United States and our servers are operated there, so using the Services involves transferring your data to the United States. Where required, we rely on appropriate safeguards such as the European Commission's standard contractual clauses, together with the technical measures in section 16.

16. Security and international processing

We use administrative, technical and organizational safeguards designed to protect information, including access controls, encryption in transit, encryption of connected-storage credentials and API secrets, hashed passwords and API keys, support for two-step verification and passkeys, and encryption of stored file content with keys we hold. Because we hold those keys, this protects your content against a storage provider, a lost disk, a stolen backup or a database leak, but not against someone with full control of our servers.

Text messages and calls travel over the public telephone network, which is not encrypted end to end: carriers and the devices involved necessarily handle the content (see the Messaging Terms). Email we send to you is likewise only as private as your mail provider makes it.

No system or transmission is completely secure, and we cannot guarantee against loss, misuse or unauthorized access. You are responsible for strong authentication, for secure sharing and form settings, and for keeping independent backups. If we become aware of a breach affecting your personal information, we will notify you and the authorities where law requires.

Bodek is based in the United States. Information may be processed in the United States and other locations where we or our providers operate, subject to applicable law.

17. Children and age

The Services are not directed to children under 13, and we do not knowingly collect personal information from them. By creating an account you confirm that you are at least 18 years old. We do not ask for a date of birth and we do not verify anyone's age, so we rely on that confirmation. If you believe a child provided information, contact us so we can investigate and delete it where required. A customer who collects information from children through a form or a message list is responsible for the consent that law requires.

18. Changes to this Policy

We may update this Policy as the Services or the law change. We will post the revised Policy with a new date and provide reasonable notice of material changes. Your continued use after the effective date is subject to the updated Policy.

19. Contact us

For privacy questions or requests, email privacy@bodek.us. For copyright complaints, email dmca@bodek.us. For anything else, contact support or write to support@bodek.us. Bodek Solutions LLC, United States.