This Privacy Policy explains how Sosa Projects, LLC (“Sosa Projects,” “we,” “us,” or “our”), a California limited liability company, collects, uses, shares, and protects information in connection with the Tipmik mobile application (the “App”), the website at tipmik.com (the “Site”), and related services (together, the “Services”). It also explains the choices and rights you have.
By using the Services, you acknowledge this Privacy Policy. If you do not agree with it, please do not use the Services. Our Terms of Service also apply.
The short version
- Tipmik keeps a record of your shifts: your jobs, hours, tips, tip outs, wages, and goals. That record exists so the App can show it to you.
- We do not sell your personal information, share it for cross-context behavioral advertising, or use it for advertising. The App contains no advertising SDKs and does not track you across other companies’ apps or websites. It measures how the App itself is used, which you can turn off (see “App analytics”).
- When you scan a checkout slip or screenshots of a tip payout app, the photos are read by an AI model to fill in your shift. We instruct our AI routing provider to use only providers that do not store or train on it.
- If you connect an AI assistant, such as Claude or ChatGPT, it can read your records, and log, edit, and delete shifts if you allow it, until you disconnect it. What it receives is handled by the company that provides it, under its own privacy policy.
- You can export your shift history at any time, and you can delete your account and data from inside the App.
Information we collect
Information you provide
- Account information. You sign in with Apple or Google. We receive a unique account identifier and, if your Apple or Google account provides it, your email address. If you use Sign in with Apple and choose to hide your email, we receive Apple’s private relay address instead. If you share your name with Apple, the App stores your given name in your sign-in profile with our authentication provider. We do not collect passwords.
- Profile information. The first name you enter during setup.
- Work records. The jobs you add (for example, an employer or venue name, your role, your hourly wage, and your tip-out rule) and the shifts you log (date, start and end times, sales, tips, tip ins and tip outs (including, if you enter or scan them, who each came from or went to — which may be coworkers’ names or roles — and how each was worked out), what you were paid out for a shift, wages, and any note you write about a shift, which may mention other people, such as a guest or coworker who tipped you), your scheduled shifts (including any you set to repeat weekly), your earnings goals, and your settings (such as pay period, week start, appearance, and reminder schedule).
- Checkout photos. If you scan a checkout slip or a tip payout app’s screen, the photos you take or choose (up to four for one shift). They may show information beyond your earnings, such as your employer’s name or store number, your name or employee number, coworkers’ names or roles, or register details. The App does not attach the photo’s location or other embedded camera metadata.
- Imported records. If you import shift history from a file (for example, a CSV exported from another app), the App sends us the file and our servers read it: the shifts, amounts, jobs and notes it contains. Until you choose to import them, those records are held apart from your account’s records so the App can show you what the file holds; nothing is added to your shifts before you confirm. We do not keep the file itself, only the records read from it. Imported shifts are then stored like shifts you logged, marked with the import they came from so you can undo it. A file you choose while setting up the App is sent to us as soon as you choose it, so the App can show you what it holds before you have an account; that first read keeps nothing, neither the file nor the records in it. When you finish setting up, the file is sent again and its records are imported into your account; finishing is your confirmation, and you can undo the import for 30 days. If the import doesn’t go through when you finish, it is tried again the next time you open the App. If you don’t finish, nothing from it is kept.
- Tax tools information (optional). If you turn on Tipmik’s optional tax tools, you may also provide your filing status, an income range, your name and mailing address (used only to print on documents you choose to export), your occupation and employment type for a job, cash and card tips separately, service charges, the recipients of your tip outs (which may be coworkers’ names), whether you declared tips to your employer and any undeclared amounts, and whether figures on your Form W-2 match your records. We never store the amounts from your W-2. We also keep a history of changes you make to verified shift records, which you can export as a record of your tips.
- Communications. If you contact us, the content of your message and your contact details. If you use “Report a bug” in the App, the email it drafts also includes the App’s version and build number, your device model, and its operating system version. You see this information in the draft and can edit or remove it before sending.
Information collected automatically
- Technical and log information. When the App or your browser connects to our servers, we and our infrastructure providers receive technical information necessary to deliver the connection, such as your IP address, device and browser type, and the time and path of the request. Our server logs record request paths, which can include dates or record identifiers, and error details that may include your internal account identifier. We do not log the contents of the shift records you save.
- Connection requests. When you start connecting an AI assistant to your account, we receive the browser and operating system of the device that started it and, from our network provider, an approximate location for its IP address, such as a city and state. The App shows you these when it asks you to approve the connection (see “Connected assistants”).
- App analytics. The App and our servers record how the App is used, such as which screens are opened, which onboarding steps are completed or skipped, whether a shift was logged or scanned, and subscription events (a trial started, a renewal, a cancellation and whether it came during the free trial, a subscription bought again after it lapsed), each naming the store, the App Store or Google Play, and, for a subscription started or renewed, the price and currency it was charged in and any offer it was bought under. See “App analytics” below.
- Website analytics. On the Site, we may use PostHog to measure aggregate visits, such as which section of the page was viewed, whether an App Store button was clicked, whether the free-month gift page was opened and its code copied, whether the download page sent you on to a store, the referring website, campaign, or social app (such as TikTok or Instagram, from the link you followed or from that app’s built-in browser), and your device category. A Google Play link from the download page also passes that source on to Google Play. This analytics does not use cookies or persistent identifiers: each page view gets a random identifier that is never stored on your device, and events are not tied to a profile. PostHog receives your IP address and browser information as part of each request.
We do not collect your precise location, contacts, health data, biometric data, or advertising identifiers, and we do not request App Tracking Transparency permission because we do not track you.
Permissions on your device
The App asks for permission to use your camera only to scan checkout slips and the codes that connect an AI assistant, your photo library only to scan checkout slips, and notifications only to deliver the reminders you set up. Reminders are scheduled on your device; we do not use push notification services or collect push tokens. You can change these permissions at any time in your device settings.
Information stored on your device
The App stores some information on your phone so it works offline: a cache of your records (kept up to 7 days), changes you made offline that have not yet synced, your in-progress setup answers, and your sign-in session. If you add the App’s widgets to your Home Screen or Lock Screen, the App also keeps a summary of your current week and month on your phone for them to display. This information is removed when you sign out. Setup answers given before you sign in stay on your phone until you sign in, which moves them to your account.
How we use information
We use information to:
- provide, operate, and maintain the Services, including syncing your records across sessions and devices;
- read checkout slips you scan and fill in your shift for you to review;
- answer the AI assistants you connect, and save the shifts they log, edit, or delete for you;
- calculate the totals, averages, goals, estimates, and exports you ask for;
- schedule the reminders you choose;
- respond to your requests and provide support;
- secure the Services, prevent fraud and abuse, and troubleshoot problems;
- understand, in aggregate, how visitors use the Site;
- comply with legal obligations and enforce our Terms; and
- carry out any other purpose we describe to you when we collect the information, with your consent where required.
We do not use your information to make decisions that produce legal or similarly significant effects about you, and we do not sell it or use it for advertising.
Scanning and AI
Before your first scan, the App asks your permission to send the photos and shift date to OpenRouter and its AI providers, and remembers your answer on that device for your account. You can decline and enter your shift manually, and you are asked again until you allow it. If you allow the scan, the App uploads the photos directly to our private cloud storage. Our server then sends the images, together in one request with the date of the shift, to OpenRouter, a service that routes the request to an AI model provider, currently Anthropic (Claude) and, as a fallback, Google (Gemini). The request does not include your name, email address, or account identifier. The model reads the numbers on the slip or screens and returns them to the App, where you review and correct them before saving; nothing is saved to your records until you confirm. Unless you have turned app analytics off, our server keeps what the model read beside the photos until you save the shift, so it can measure how often the reading needed correcting (see “App analytics”); it is then deleted. Also unless you have turned app analytics off, our server keeps a history of your scans for 90 days so we can find out why a scan went wrong and fix it: for each scan, what the model read (which can include anything printed on the slip or screen, such as a coworker’s name), which model answered, or why no answer came back, and — only for a scan that failed or found no checkout or payout — the photos themselves. Only the people who fix scanning look at it, and turning app analytics off deletes it.
We instruct OpenRouter to route these requests only to providers that do not retain or use request data for training (OpenRouter’s “deny data collection” setting). The AI providers process the image to return a result and handle it under their own terms and privacy policies. AI can misread a slip or a screen, which is why the App always asks you to check the result.
Photo retention. Photos you scan but do not save with a shift, and what the model read from them, are automatically deleted from our storage, generally within one day. The scan history described above, including the photos of a scan that failed, is deleted after 90 days. Photos you save with a shift are kept with that shift so you can view them later, until you remove them from the shift, or delete the shift or your account.
Connected assistants
You can connect an AI assistant, such as Claude, ChatGPT, or Muse, to your Tipmik account, so it can answer questions about your records and, if you allow it, log, edit, and delete shifts for you. Nothing is connected unless you do it, and connecting requires a Tipmik subscription.
How a connection is approved. You start connecting in the assistant, which opens a Tipmik page in your browser. On a computer, the page shows a code that you scan with the App (More → Connections → Scan); on your phone, it shows a button that opens the App. The App then shows which assistant is asking, where the request started (the browser, operating system, and approximate location described in “Information collected automatically”), and what the assistant will be allowed to do, and you approve or decline it there. A request expires 10 minutes after it starts, and we delete it, with those details, within about two hours after that.
What the assistant receives. A connected assistant can ask for your totals and averages for a day, week, pay period, month, or year; your goals and your progress toward them; your best shifts, weekdays, parts of the day, and jobs; your planned shifts; your shifts, including their times, amounts, and notes; your jobs, with their roles and wages; comparisons between shifts; and, if you use tax tools, your qualified tips, estimated tax savings, tips not yet reported to your employer, and withholding figures. It receives only what its requests return, when it makes them. Results never include your email address or your sign-in identifiers. To ask, the assistant sends us the details of its request, which can come from your conversation with it: the days or periods it asks about, any words it searches your shifts for, and the jobs it narrows a search to.
What the assistant can change. Only if the assistant asks to change your shifts and you leave “Change your records” on when you approve it, the assistant can add shifts with the details it sends, at most 20 in any 24 hours from each assistant, and correct or delete any of your shifts, including ones you entered yourself, at most 20 corrections and 20 deletions in any 24 hours from each assistant. It cannot change anything else. A shift an assistant logs is saved like one you entered and is marked in the App with the assistant’s web address, such as claude.ai. A correction or deletion is made as if you had made it in the App, and every one an assistant makes is recorded in the history of changes with the assistant’s web address: what it changed, from what to what (for a note, only that it changed, not its words), and when. Changes to a verified shift record and deletions are part of that record’s history, as they are for changes you make. Deleting a shift also deletes the photos saved with it, and it cannot be undone in the App.
The assistant’s provider. What an assistant receives from Tipmik is then handled by the company that provides the assistant (for example, Anthropic for Claude, OpenAI for ChatGPT, or Meta for Muse) under its own terms and privacy policy, including whether it keeps your conversations or uses them to train its models. We do not control that. Anything you tell or show the assistant, such as a photo of a checkout slip you ask it to log, goes to that company, not to us; we receive only what the assistant sends when it logs or corrects a shift: the day, job, times, and amounts, and any note or names of who tips were shared with; to delete a shift, it sends only which one.
What we keep. For each connection, we keep which assistant it is, what it may do, and when it was approved and last used. The assistant gets access keys that expire after an hour and are renewed for as long as it keeps using them; if a connection goes unused for 90 days, its access lapses and we delete the connection. We store these keys only in a form that cannot be read back.
Disconnecting. You can disconnect an assistant at any time in More → Connections; it loses access immediately. Deleting your account disconnects every assistant. Removing Tipmik in the assistant’s own settings disconnects it too when the assistant tells us, and not every assistant does, so check More → Connections afterwards. Disconnecting does not delete what the assistant already received; its provider’s privacy policy explains how to delete that. Shifts an assistant logged or corrected stay in your records as it left them until you change or delete them.
How we share information
We share information only as described here:
- Service providers. We use service providers (sometimes called processors or subprocessors) that process information on our behalf, under contracts or terms that limit their use of it to providing their services to us. They are listed in the table below.
- Legal and safety. We may disclose information if we believe in good faith that it is required by law, subpoena, court order, or other legal process, or necessary to protect the rights, property, or safety of Sosa Projects, our users, or others, or to investigate fraud or security issues. Where the law allows, we will try to notify you before disclosing your information in response to a legal demand.
- Business transfers. If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of our assets, information may be transferred as part of that transaction, subject to this Privacy Policy or a notice we provide you.
- At your direction. When you export your records or share a file from the App, you choose where it goes. When you connect an AI assistant, we send it what its requests ask for (see “Connected assistants”). Information you send to others is governed by their practices, not ours.
We do not share your records with your employer, the IRS, or any other government agency, except as required by law as described above.
| Provider | What they do for us | Information involved |
|---|---|---|
| Hetzner Online | Hosts our servers and database in the United States | All account and record data |
| Cloudflare | Network security, content delivery, domain name services, and private storage for checkout photos and exports | Connection data; checkout photos and exports |
| Google (Firebase Authentication) | Sign-in and account authentication; Sign in with Google | Account identifier, email address, given name (Apple sign-in) |
| Google (Firebase App Check) | Confirms that requests come from the genuine App, including before you have an account | An attestation for this installation, from Apple’s App Attest on iPhone and Google Play Integrity on Android; no account identifier |
| Apple | Sign in with Apple; App Store distribution and subscription billing | Account identifier; purchase information (handled by Apple) |
| Google (Google Play) | Distribution of the Android app and subscription billing on Android | Account identifier (attached to purchases); purchase information (handled by Google) |
| OpenRouter | Routes checkout photos to AI model providers | Checkout photos and the shift date |
| Anthropic and Google (Gemini) | AI models that read checkout photos | Checkout photos and the shift date |
| PostHog | App analytics and website analytics | Usage events, internal account identifier, device information, IP address |
| ntfy | Sends us, the people running Tipmik, a notification when a subscription starts, bills, is cancelled, renews, or ends | The event, plan, store, and kind of offer only; no account identifier, name, email address, or amount |
| AI assistants you connect (such as Anthropic’s Claude, OpenAI’s ChatGPT, or Meta’s Muse) | Not our service providers: they receive information at your direction and handle it under their own terms and privacy policies | What their requests return, such as totals, goals, shifts and their notes, jobs and wages, planned shifts, and tax tools figures |
We may change our service providers from time to time. We will update this table when we do.
App analytics
To learn which parts of the App help people and where they get stuck, the App and our servers send usage events to PostHog, our analytics provider. An event names what happened, such as “shift logged” or “subscription started” (and which store, the App Store or Google Play), with a few details from a fixed list: for example, whether a shift was scanned, how many jobs you added in onboarding, how long a setup screen was open, whether signing in went through, or which plan you chose. To measure the App’s quality, events also say how many photos a scan read and how many tip share lines it found, how a scan compared with what you saved (for each figure, whether you kept it, entered it yourself, or changed it, and by roughly what share — such as “less than 5%” — never by an amount), whether a shift was edited or deleted soon after it was logged and which kinds of field changed, how many days after a shift it was logged, where Log shift was opened from, whether a W-2 box matched, how many rows an imported file had and why rows were skipped, how many shifts an import added or undid, which screens of an import’s highlights you viewed or skipped, whether you opened the Totals breakdown or Compare and which measure you ranked by, whether you compared a shift with another and with which kind (last week, last month, your average, or one you picked), whether you shared the free-month gift with someone (sent or cancelled, never with whom), whether you connected or disconnected an AI assistant and which one (Claude, ChatGPT, Muse, or another), which kind of request a connected assistant made (such as a summary, a goal check, or logging a shift) and whether it worked, whether a shift was logged, edited, or deleted by an assistant, and, while setting up, which app’s export steps you opened and whether you chose a file to import (its kind, such as CSV or Excel, never its contents).
Events never include your earnings, tips, wages, sales, or any other amount from your records; the only amount they carry is the price of your Tipmik subscription, on the events for a subscription started or renewed, with its currency and any offer, such as a free trial, an offer code, or a win-back offer; your name, email address, or notes; the names of your jobs; or the contents of a checkout slip. Once you are signed in, events are tied to your Tipmik account’s random internal identifier, so we can see, for example, how many people who start a trial keep using the App. Most of setting up the App happens before you sign in; those events are recorded under a random identifier for this installation and linked to your account when you sign in. If you have turned analytics off on this phone before, it stays off while you set up again. The App does not record your screen, and it does not capture what you type or tap beyond the named events. PostHog receives your device type, operating system, app version, and IP address, which it uses to estimate your country and region.
We use this information only to improve the App. We do not use it for advertising, we do not sell it, and we do not combine it with information from other companies. App analytics is on unless you turn it off. You can turn it off at any time in More → Share usage analytics, or using Usage analytics on the sign-in screen or subscription screen; a choice made on the sign-in screen applies to your account once you sign in. Changing this choice does not require a subscription.
Payments
Subscriptions are purchased and billed through Apple’s App Store or Google Play, depending on where you subscribe. Apple or Google processes your payment information under its own privacy policy; we do not receive your payment card details or your Apple Account’s or Google account’s name or email.
To know whether your subscription is active, the App attaches your Tipmik account’s random internal identifier to a purchase, so Apple’s records of it name your Tipmik account. On Google Play, the same random internal identifier is attached to the purchase as its account identifier. We then receive the subscription’s details from Apple or Google, both from the App and directly from their servers: its transaction identifiers, the plan, whether it is in a free trial, when it renews or expires, whether it will renew, and whether it was refunded, and, for each period it bills (a free trial included), the price and currency charged, the country of the store, and any offer it was bought under, such as a free trial, a discount, or an offer code. Apple signs this information, and we check that signature before using it; for Google Play, we ask Google’s servers directly. We use it only to give you access to the App, to keep a record of our sales and of which offers are taken, to remind you, if you allow notifications, the day before a free trial ends, and to send ourselves a notice through ntfy when a subscription starts, bills, is cancelled, renews, or ends. That notice says only what happened, the plan, the store, and the kind of any offer (such as a win-back offer), never whose subscription it is or its price, so it is sent whether or not app analytics is on.
Retention
We keep information for as long as your account is active and as needed to provide the Services, unless a shorter period is described here:
| Information | How long we keep it |
|---|---|
| Account, jobs, shifts, goals, settings, tax tools information | Until you delete it or your account |
| History of changes (changes to verified shift records, every deletion, and every change an assistant made, with which assistant made it) | Until you delete your account; it is kept after you delete an individual shift so your tip record stays complete |
| Checkout photos saved with a shift | Until you delete that shift or your account |
| Checkout photos not saved with a shift, what the scan read from them, and export files | Automatically deleted, generally within one day |
| Scan history (what each scan read, and the photos of a scan that failed), unless app analytics is off | Automatically deleted after 90 days |
| Records read from an import file you didn’t confirm | Automatically deleted, generally within one day, or as soon as you choose another file |
| A summary of a confirmed import (what its highlights show) | Until you delete your account; undoing the import deletes the shifts it added |
| Connected assistants (which assistant, what it may do, when it was approved and last used) | Until you disconnect it, it goes unused for 90 days, or you delete your account |
| Assistant access keys | One hour for each access key; renewal keys until the connection goes unused for 90 days, you disconnect it, or you delete your account |
| Connection requests (browser, operating system, approximate location) | Deleted within about two hours after the request expires, 10 minutes after it starts |
| Shifts logged by an assistant, and which assistant logged them | Like other shifts: until you delete the shift or your account, including after you disconnect the assistant |
| Subscription details received from Apple or Google | Until you delete your account |
| A record of each subscription charge (the plan, when it billed, the price and currency, the store’s country, and any offer) | Kept after you delete your account as our record of sales, no longer linked to your account |
| App analytics events | As long as needed to understand how the App is used; after you delete your account they are no longer tied to anything that identifies you |
| Server logs | For a limited period for security and troubleshooting, then deleted |
| Support messages | As long as needed to resolve your request and keep a record of it |
When you delete your account, we delete your account and records from our production systems, delete your checkout photos and exports from storage, disconnect every assistant connected to your account, and delete your sign-in account with our authentication provider. Information you exported or shared before deletion is outside our control. We may keep information where the law requires it, or where it is reasonably necessary to resolve disputes, enforce our agreements, or protect against fraud and abuse, and only for as long as that need lasts.
Your choices and controls
- Review and correct. You can view and edit your records in the App at any time.
- Export. You can export your shift history as a CSV file from the App (More → Export history).
- Delete. You can delete individual shifts, and you can delete your account and all associated data from the App (More → Delete account). If you signed in with Apple, deleting your account also revokes Tipmik’s access to your Apple ID.
- Connected assistants. You can see the assistants connected to your account, and disconnect any of them, in More → Connections.
- Permissions and reminders. You can turn camera, photo, and notification access on or off in your device settings, and change or turn off reminders in the App.
- App analytics. You can turn app analytics off at any time in More → Share usage analytics, or using Usage analytics on the sign-in screen or subscription screen, without a subscription. It applies to your account on every device, and our servers stop sending events about you too. The subscription notices described under “Payments” name no one, so they are still sent.
- Tax tools. Tax tools are off unless you turn them on. You can delete your tax profile information in the App.
- Contact us. You can also make any request below by emailing hello@tipmik.com.
Your privacy rights
Depending on where you live, you may have rights over your personal information, including the right to know or access the information we hold about you, to correct it, to delete it, to receive a portable copy, and to opt out of the sale or sharing of personal information, targeted advertising, or certain profiling. We do not sell or share personal information, use it for targeted advertising, or profile you in ways that produce significant effects, so there is nothing to opt out of; you may still contact us with any request.
To exercise a right, use the controls in the App or email hello@tipmik.com. We will verify your request by confirming it through the email address or sign-in account associated with your Tipmik account, and we will respond within the time the law requires (for example, 45 days under California law, which may be extended once by 45 days where permitted). You may use an authorized agent to submit a request on your behalf; we may require proof of the agent’s authority and ask you to verify your identity directly. If we deny your request, you may appeal by replying to our decision, and we will respond to your appeal within the time required by law. We will not discriminate against you for exercising any of these rights.
California residents
This section supplements the rest of this Privacy Policy and applies to California residents under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (“CCPA”), to the extent the CCPA applies to us.
In the preceding 12 months, we have collected the following categories of personal information, from you, from your device, from our authentication providers, and from our network provider (the approximate location of an IP address), for the business purposes described in “How we use information”:
| Category (CCPA) | Examples | Disclosed for a business purpose to |
|---|---|---|
| Identifiers | Account identifier, email address, IP address, name, mailing address (tax tools) | Hosting, network, and authentication providers |
| Personal information described in Cal. Civ. Code § 1798.80(e) | Name, address, employment information | Hosting and network providers |
| Commercial information | Subscription status, the price, currency, and offer of each subscription charge | Apple or Google |
| Internet or other electronic network activity | Server logs, app and website analytics events | Hosting, network, and analytics providers |
| Professional or employment-related information | Employers, roles, wages, tips, hours, tip outs, tip declarations, shift notes | Hosting and network providers; AI providers (checkout photos only) |
| Sensory information | Checkout photos | Storage and AI providers |
| Inferences | Earnings estimates and goal progress calculated for you | Hosting provider |
If you connect an AI assistant, it receives information in these categories at your direction, as its requests ask for it (see “Connected assistants”); that is not a sale or sharing.
We do not collect sensitive personal information as defined by the CCPA for the purpose of inferring characteristics about you, and we use any sensitive information only as permitted by the CCPA. We do not sell or share (as those terms are defined in the CCPA) personal information, and we have not done so in the preceding 12 months. We do not knowingly sell or share the personal information of consumers under 16.
Shine the Light. California Civil Code § 1798.83 permits California residents to request information about disclosures of personal information to third parties for their direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes.
Do Not Track and Global Privacy Control. Because we do not track you across third-party websites or sell or share personal information, we do not change our practices in response to Do Not Track signals. If your browser sends a Global Privacy Control signal, we treat it as a request to opt out of sale and sharing, which we already do not engage in.
Other US states
Residents of other states with consumer privacy laws (such as Colorado, Connecticut, Virginia, Texas, and Oregon) may exercise the rights described above in the same way, including the right to appeal a decision.
Users outside the United States
The Services are operated from the United States, and your information is processed and stored in the United States, where data protection laws may differ from those in your country. If you are in the European Economic Area, the United Kingdom, or Switzerland, we process your information on the following legal bases: to perform our contract with you (providing the Services), our legitimate interests (securing and improving the Services and measuring Site visits in a privacy-protective way), your consent (such as device permissions, which you can withdraw at any time), and compliance with legal obligations. You have the rights described above and may also object to or restrict our processing and lodge a complaint with your local data protection authority. Where required, we rely on appropriate safeguards, such as standard contractual clauses, for international transfers.
Security
We use reasonable administrative, technical, and physical safeguards designed to protect your information, including encryption in transit (HTTPS/TLS), private storage accessed only through short-lived signed links, a database that is not reachable from the internet, access limited to the people and systems that need it, verification of your sign-in on every request, and assistant access keys stored only in a form that cannot be read back. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we learn of a security breach affecting your personal information, we will notify you and any required authorities as the law requires.
Please protect your device and your Apple or Google account, since anyone with access to them may be able to access your Tipmik records.
Children
The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. You must meet the age requirement in our Terms of Service to use the Services. If you believe a child under 13 has provided us with personal information, contact us and we will delete it.
Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version here and change the effective date above. If we make a material change, we will notify you in the App or by other reasonable means before it takes effect, and where the law requires your consent, we will ask for it.
Contact us
If you have questions or requests about this Privacy Policy or your information, contact:
Sosa Projects, LLC
California, United States
Email: hello@tipmik.com