Get started free
Legal

Privacy Policy

We built DeductSam to help you find money, not to sell your data. Here is exactly what we collect, why, and how it is protected.

Last updated: September 29, 2026  ·  Effective: September 29, 2026

This version describes how DeductSam works as of version 1.1. It takes effect on September 29, 2026.

This Privacy Policy describes how DeductSam LLC ("DeductSam," "we," "us," or "our") collects, uses, and shares information when you use our website at deductsam.com and our application at app.deductsam.com (collectively, the "Service"). By using the Service, you agree to the collection and use of information as described in this policy.

1. Information We Collect

Information you provide directly

When you create an account or use the Service, we collect:

  • Account information — your name, email address, and password (stored as a secure hash — see Section 4).
  • Business profile — the type of business you operate, whether you use a home office or vehicle for work, number of employees, state of operation, and other context you share during the onboarding interview. This is used exclusively to personalize Sam's guidance.
  • Expense data — merchants, amounts, dates, categories, notes, and business purpose descriptions you enter for your expenses.
  • Receipts — photos and PDFs of receipts you attach to an expense. The file is stored in encrypted cloud storage under your account. To fill in the expense for you, the receipt image itself is sent to OpenAI to be read (a PDF is first turned into an image of its first page) — not text we extracted beforehand. See Section 3. What it reads is shown to you as a prefilled expense, and nothing is saved until you press Save. When you save, we also record which details were read from the receipt and which you changed, including the value that was originally read.
  • Tax documents — tax forms and other tax records you upload to your Documents, such as a Form W-2, a Form 1098-T, a Form 1095-A, last year's Form 1040, or any other tax-related document (for example a property tax bill). The file is stored in encrypted cloud storage under your account. If you ask DeductSam to read a document, an image of each page it reads is sent to OpenAI (Section 3), and what it reads is shown to you field by field.

    A reading is saved only for the fields you confirm or correct. Fields you leave alone are not saved. When you correct a field, we keep both your value and the value that was originally read, so your record shows which number is yours. Before a reading is saved, Social Security and taxpayer identification numbers, employer identification numbers, and any value printed under a label that names it as an account, policy, or similar number are cut down to their last four digits. That check cannot recognise every account number: an account number printed with no label naming it looks like any other number. The forms we read box by box are set up so that names, Social Security numbers, and dates of birth are not read at all. The page image itself is the whole page, so what is sent to OpenAI contains whatever is printed on it.

    Removing a document does not erase it. Deleting a document from your Documents list hides it, but the file and any readings you confirmed are kept with your records, because tax records can be needed for years. They are erased when you delete your account (Section 5). If you want a single document erased sooner, contact us.
  • Voice dictation — when you dictate instead of typing, the recording is sent from our server to OpenAI's transcription service (Whisper) to be turned into text. We keep the text, which becomes part of what you were entering. The recording itself is never written to our database, our file storage, or our logs; on our side, it exists only for the length of the transcription request. What OpenAI keeps is described in Section 3.
  • Conversations with Sam — the messages you send Sam are sent to OpenAI, along with the context Sam needs to answer (see Section 3), to produce Sam's reply. We do not store your conversations on our servers. Your conversation history is kept in the browser's or the app's storage on your own device, and clearing the conversation removes it there. Signing out does not clear it, and deleting your account cannot reach it, because it is on your device rather than ours — use Clear in Sam, or clear the browser's site data, to remove it. We do keep a count of the messages you send — per calendar month on the Free plan and per day on Pro — to apply the Free plan's monthly allowance and Pro's daily fair-use limit. Your first name, if Sam's greeting used it, is part of the conversation history that is sent.
  • Profile photo and invoice logo — if you add a profile photo or a logo for your invoices, it is stored in a publicly readable location so it can be displayed on your invoices and in the app. Anyone who has the exact link to the image can view it. Do not use an image you would not want seen outside DeductSam.
  • Invoice data — client names, email addresses, phone numbers and postal addresses, amounts, and line items for invoices you create inside the Service, and the name, email address, phone number and address you choose to show as the sender on your invoices.
  • Rental property details — if you use a Property workspace, the property's address and the use and day counts you enter for it.
  • Year-end and tax-year answers — answers you give on your Year-End page and in "A few things about you", such as your filing status, last year's total tax and adjusted gross income, estimated tax payments, and retirement contributions. If you are self-employed and answer the health-insurance questions, this includes the health-insurance premiums you paid and whether other coverage was available to you; if you record a health savings account, its contributions, coverage type and months; and, if you confirm them from a Form 1095-A, its monthly premium and credit figures and the last four digits of the policy number. These are amounts and coverage facts used for tax checks. DeductSam does not ask for, and does not collect, any diagnosis, condition, treatment, provider or other medical information.
  • Your DeductSam subscription, recorded as an expense — each time you are actually charged for DeductSam (on the web through Stripe, or in the iOS app through Apple), the charge is added automatically as a "Software & Subscriptions" expense in your oldest active business workspace (or, if you have none, your oldest property workspace). Free trials, test purchases and non-U.S.-dollar charges are not recorded, a refund reduces the recorded amount, and if the same charge later arrives from your bank through Plaid it is matched to this expense instead of being added twice. We keep a short log of which charges were recorded, so none is recorded twice. There is no setting to turn this off; you can delete the expense, and it will not be added again.
  • Onboarding answers in progress — while you answer the setup questions, your answers so far are saved in your browser's or the app's storage on your own device, so you can pick up where you left off. They stay there until the workspace is set up, you sign out, or 30 days pass, whichever is first. The answers reach our servers only when you finish.
  • Payroll and contractor data — if you use the payroll tracking feature, you may enter wage, salary, and contractor payment information.
  • Stripe Connect onboarding (only if you choose to get paid through invoices) — DeductSam lets you connect your own Stripe account so your clients can pay your invoices. If you start that setup, DeductSam sends you to Stripe's own hosted onboarding, and the information Stripe asks for there goes to Stripe directly, not through us: your legal name and business details, your address and date of birth, a government identification number where Stripe requires one, and your bank account details for payouts. That collection is governed by Stripe's own privacy policy and the Stripe agreement you accept with them — DeductSam is not a party to it and never sees, receives, or stores those details.

    What DeductSam stores from that process is only what it needs to know whether invoicing works: your Stripe account identifier, two status flags (whether Stripe has enabled charges, and whether you finished the onboarding form), and the date you connected. Nothing else. You can disconnect at any time in Settings; to remove DeductSam's access to your Stripe account completely, also remove DeductSam in your Stripe Dashboard. What happens to this connection when you delete your DeductSam account is described in Section 5.
  • Household tax facts — if you use a Personal workspace, you can record a small set of structured answers that the app's household checks need in order to run: whether you have a spouse and whether they have employment income; whether you or your spouse have a workplace retirement plan; whether anyone in the household is a student; whether you own or rent your home; whether you paid for childcare this year; the state you live in; your total tax and adjusted gross income from last year's return; and the birth years of your children. You can also add a free-text note in your own words.

    This is the one category that includes information about people other than you — a spouse, and children who may be minors. Three things about how we handle it:
    • We store birth years, never names or full dates of birth. This is deliberate. A birth year is all the tax rules need — a child's age at the end of the tax year decides whether a credit or an exemption applies — and it is far less identifying than a name or a full date of birth. The app has nowhere to enter a child's name.
    • Nothing is saved until you confirm it. Where the app proposes these facts by reading a description you already wrote, it shows you each proposed answer and the sentence it came from, and writes nothing until you confirm. You can change any answer, or leave it unanswered, at any time in Settings.
    • It is used only to run tax checks for your own return — for example, whether a childcare or education credit is worth discussing with your preparer. It is never used for advertising or profiling, never sold, and never shared with anyone outside the service providers listed in Section 3.
    These answers are stored under your account, protected by the same row-level security as the rest of your data (Section 4), and are deleted with your account (Section 6).

Information collected automatically

  • Product state — a few records of how you have used features, kept so the app behaves correctly: your Sam message count (see "Conversations with Sam"), whether you have finished the in-app tour, and which items you have reviewed, dismissed or already seen. The app contains no analytics or tracking software, and this is not used to build advertising profiles.
  • Error and diagnostic reports — if the application crashes or encounters an error, a report is sent to our error monitoring provider, Sentry. It includes the error message, a stack trace, the app version, the device model and OS version, and the IP address the request came from. A report from the app also carries a short trail of what happened just before the error (breadcrumbs), including the addresses of the app's recent requests to our servers and recent app log messages. Those request addresses contain your account identifier, and some reports attach your account identifier directly, so these reports are not anonymous. The app also sends Sentry timing measurements for a sample of sessions (how long screens and requests take). We do not deliberately attach your financial records to any of this, and reports from our servers have amounts, email addresses, and long numbers removed before they are sent. This is diagnostic data used to fix faults. We do not use it for advertising, we do not combine it with data from other companies' apps or websites, and DeductSam contains no advertising identifier and no third-party analytics or tracking SDKs.
  • AI usage records — each time the Service sends a request to OpenAI for you, we record which feature made it, the AI model used, how much text (in tokens) or audio (in seconds) it processed, what it cost, and when, together with your account identifier. These records hold no content — no message, receipt, document, recording, or answer. They let us understand and manage what the AI features cost. When you delete your account, your account identifier is removed from them (Section 5).
  • Authentication tokens — short-lived session tokens managed by Supabase Auth. We do not store your password in plaintext at any point.

The DeductSam iOS app

This policy covers the DeductSam iOS application distributed on the Apple App Store as well as the web application at app.deductsam.com. The iOS app collects the following in addition to everything above:

  • Location — only while you are tracking a drive (Pro plan). The mileage feature uses your device's GPS to measure the distance of a drive for the IRS standard mileage deduction. The app requests "While Using the App" location permission — never "Always" — and location is collected only between the moment you tap Start drive and the moment the drive is stopped, paused, or automatically ended. Because a drive must keep measuring while your phone is locked or you are using another app, tracking continues in the background during an active drive only; iOS displays its standard indicator whenever this is happening. We store the resulting trip record so the deduction is substantiated if it is ever questioned: the distance, the start and end times, the precise GPS coordinates of where the drive started and where it ended, and the street addresses of those two points. The route in between is used on your device to measure the distance and is not sent to our servers; only a count of the points measured is saved. To turn the start and end coordinates into street addresses, the app uses Apple's geocoding service, which receives those two coordinates (Section 3). We do not track your location when no drive is running, and we do not use location for advertising or sell it to anyone. You can decline location permission entirely and still use every other part of DeductSam; you can revoke it at any time in iOS Settings.
  • Camera, photo library, and microphone — used only when you photograph or attach a receipt, or dictate a note. When you dictate, the short audio clip is sent to OpenAI to be transcribed into text and is discarded immediately after transcription — it is never written to our database or storage. Each permission is requested at the moment you use the feature and each can be declined without affecting the rest of the app.
  • Device and app identifiers — your account identifier, and the device model and OS version attached to error reports, used to operate the app and diagnose faults. DeductSam does not create or read a device or installation identifier. DeductSam does not collect the Advertising Identifier (IDFA), does not ask for tracking permission, and does not track you across other companies' apps or websites.
  • App Store purchase records — if you subscribe inside the iOS app, Apple provides us a purchase receipt and a subscription transaction identifier so we can verify your subscription and unlock paid features. See the in-app purchases entry in Section 3.
  • Notifications — notifications in the iOS app are generated locally on your device (for example, a reminder that a drive is still running, or a count of transactions awaiting review). We do not operate a push server and we do not collect a push notification device token.

Information from connected services

If you choose to connect third-party services, we collect data from those services on your behalf:

  • Plaid (bank and credit card sync — Pro plan) — with your explicit authorization, Plaid provides us read-only access to your transaction history — up to two years of past transactions when you connect, and new ones as they post. How far back the app imports depends on your plan (see the Terms). We receive the name of your bank; the name and last four digits of each connected account, and Plaid's identifiers for those accounts; and, for each transaction, its amount, date, merchant name, description, and Plaid's category. We also store the access key Plaid issues for your connection, on our servers only, so we can fetch new transactions. To categorise imported transactions that our own rules cannot place, their merchant name, description, and amount are sent to OpenAI (Section 3). We do not receive your full account number, routing number, or login credentials — Plaid handles that directly. You can revoke access at any time from Settings: disconnecting revokes the connection at Plaid and deletes the stored access key. Transactions already imported stay in your records until you delete them or your account.

On our website

  • Contact form — if you write to us through the contact form on deductsam.com, your name, email address, and message are emailed to us through Resend so we can reply. They are not saved to our database.
  • Early-access sign-up — if you sign up for early access (for example on the For CPAs page), your email address, and your name and firm size if you give them, are saved to our database along with the page you signed up from, and a welcome email is sent to you through Resend.

2. How We Use Your Information

We use the information we collect to:

  • Provide, operate, and improve the Service
  • Power Sam's AI analysis — identifying potential deductions, generating Tax Health scores, creating Year-End Packets, and responding to your questions
  • Read the receipts and tax documents you upload, using OpenAI, so their details can be filled in for you to check
  • Turn your voice dictation into text
  • Suggest categories for expenses and imported bank transactions
  • Measure and manage what the AI features cost to run
  • Send invoices to clients on your behalf when you use the email send features
  • Process payments and manage your subscription — via Stripe on the web, or via Apple if you subscribed in the iOS app
  • Send you service emails, such as team invitations and invoice notices. Receipts for your subscription come from Stripe on the web, or from Apple in the iOS app.
  • Diagnose and fix technical errors
  • Comply with applicable legal obligations

We do not use your data to train AI models for external use, sell your information to advertisers, or build advertising profiles.

3. How We Share Your Information

We share your information only as necessary to operate the Service:

Service providers

We work with the following companies to deliver the Service. Each receives only the minimum data necessary to perform their function:

  • Supabase — database and file storage. Your data is stored in Supabase-managed PostgreSQL databases and object storage, encrypted at rest.
  • OpenAI — powers Sam and the app's reading, transcription, and categorisation features. Depending on which features you use, we send OpenAI:
    • the photograph of a receipt you attach — the image itself, not text we extracted from it (a PDF receipt is sent as an image of its first page);
    • an image of each page of a tax document you ask DeductSam to read;
    • the audio recording when you dictate, to be transcribed;
    • the messages you send Sam and the recent conversation, together with the context Sam needs to answer: your business profile, your household tax facts and the note you wrote about your household, recent transactions (including their descriptions, amounts, merchants, notes and categories), summaries of your records (for example your income, expenses, contractors, assets, payroll, and mileage), figures you confirmed from documents, and the results of the checks the app has run on them;
    • when you ask Sam to look for tax opportunities, the expenses in your workspaces (merchant, description, amount, date and category) and your workspace names and descriptions;
    • the figures that go into the written summary of your Year-End Packet;
    • an expense's merchant, description, notes, and amount, when our own rules cannot pick its category;
    • an imported bank transaction's merchant or payer, description, and amount, when our own rules cannot place it;
    • dictated expense text and invoice line items, to fill in forms for you, and the description of your household you wrote, to propose household facts for you to confirm.
    We do not screen images or audio before sending them. A photo or scan contains whatever is printed on it — which can include a card number, a Social Security number, or a bank account number — and it is sent as it is. Do not photograph or upload anything you do not want read. We do not include your email address or your DeductSam account identifier in what we send. OpenAI processes this data under its own API terms and policies, which may allow it to keep what it receives for a period (for example, to monitor for abuse). That copy is held by OpenAI, not by us, and it is not deleted when you delete your DeductSam account.
  • Stripe — payment processing, in two separate roles. (1) Your subscription to DeductSam, if you subscribe on the web: Stripe collects and processes your payment information directly; DeductSam does not store full card numbers or CVV codes. (2) Invoice payments from your clients (Stripe Connect): if you connect your own Stripe account, your client pays your Stripe account directly and the money lands in your Stripe balance — it never passes through a DeductSam account, and we take no fee from it. Your identity and bank details for that account are held by Stripe under your agreement with them, not by us.
  • Plaid — bank data access. Plaid acts as the intermediary between DeductSam and your financial institution. Your banking credentials go directly to Plaid, not to us.
  • Apple (In-App Purchase / StoreKit) — if you subscribe from inside the iOS app, the transaction is processed by Apple, not by us. Apple handles your payment method entirely; we never see or store your card details. We receive a purchase receipt and a subscription identifier, which we check against Apple's signature to confirm your subscription status. Billing, renewals, refunds, and cancellation for an App Store subscription are managed by Apple in your Apple Account settings.
  • Sentry — error and performance monitoring. Sentry receives the error reports and timing measurements described in Section 1. They are not anonymous: a report can carry your account identifier, because the addresses of the app's requests contain it. We do not deliberately include your financial records in them.
  • Resend — transactional email delivery. Resend sends emails on our behalf, including invites and the invoice emails you send to clients. Resend receives recipient email addresses and message content for these emails. If you contact us through the in-app support form, the message you write (and the category you pick) is emailed to our support address through Resend, together with your account email address and account identifier, the name of the workspace you were in, your plan, and the screen you sent it from, so we can reply and understand the question; it is not stored in our database.
  • Apple (map lookups) — when you save a GPS-tracked drive in the iOS app, the app asks Apple's geocoding service to turn the drive's start and end coordinates into street addresses. Apple receives those two coordinates. DeductSam does not send Apple your account details with this request.
  • Vercel — application hosting. Your requests pass through Vercel's infrastructure to reach our servers.
  • Microsoft Clarity — website analytics on our marketing site only (deductsam.com). Clarity records session replays and builds heatmaps of the marketing pages you visit — which pages you view, where you scroll, and where you click — so we can see which explanations are working. It runs only if you accept cookies in the banner; decline and it is switched off and any Clarity cookie already set is erased. Clarity is not present in the DeductSam app. Your expenses, income, receipts, bank transactions, invoices, and household facts are never seen by Clarity, because it is not loaded on any screen that shows them.

People you invite

If you invite someone to one of your workspaces — for example your accountant or someone who works with you — they can see that workspace's records according to the role and permissions you give them. Their email address is stored so the invitation can be sent to them and matched to their account. You can change their permissions or remove them in Settings at any time.

Legal requirements

We may disclose your information if required by law, legal process, or government request — for example, in response to a court order or subpoena. We will notify you of any such request if permitted to do so.

Business transfers

If DeductSam is acquired or merges with another company, your information may be transferred as part of that transaction. We will notify you before your data is subject to a different privacy policy.

With your consent

We will share your information with additional parties only with your explicit consent.

4. How We Protect Your Data

  • Encryption at rest — all data stored in Supabase databases and file storage is encrypted using AES-256.
  • Encryption in transit — all connections to DeductSam use TLS 1.2 or higher. HSTS headers ensure browsers enforce HTTPS for all future visits.
  • Row-level security (RLS) — Supabase RLS policies enforce that every database query is scoped to your authenticated user ID. You cannot query another user's data.
  • Passwords — we never store your password in plaintext. Authentication is managed by Supabase Auth, which uses bcrypt hashing.
  • Two-factor authentication — you can enable TOTP-based two-factor authentication from Settings. Recovery codes are hashed before storage.
  • API keys — all third-party API keys (Plaid, OpenAI, Stripe) live only on our servers. They are never bundled into the frontend application code.
  • Rate limiting — the Service's API endpoints are rate-limited to protect against abuse. The endpoints that payment and bank providers call (webhooks) are not rate-limited; they are verified by signature instead.

No method of transmission over the internet is 100% secure. We take reasonable precautions, but cannot guarantee absolute security.

5. Data Retention

We retain your data for as long as your account is active. If you delete your account:

  • Your personal data is deleted from our production database immediately — the deletion runs while you wait, not on a queue.
  • Receipt and document files are deleted from storage in the same operation.
  • Backup copies may persist for up to 90 days before being overwritten.
  • If you were invited as a founding member, the email address on our founding-members list is not removed by account deletion; contact us and we will remove it.
  • AI usage records (Section 1) are not deleted: your account identifier is removed from them, and what remains — the feature, the model, the amount of text or audio processed, the cost, and the time — no longer identifies you. We keep it so our record of what the AI features cost stays complete.

While your account is active, removing a single document from your Documents list does not erase it; see "Tax documents" in Section 1.

What deletion does not reach — stated plainly

Deleting your account removes your records from our systems, including your receipts and documents in storage, and revokes any bank connection at Plaid. Some things sit outside that, and we would rather say so than let you assume otherwise:

  • Your Stripe customer record. If you subscribed through Stripe, we cancel your subscription when you delete your account (if you are charged afterwards, contact us and we will refund that charge), but Stripe keeps its own record of the transactions. Stripe is required to retain payment records under its own legal, accounting, and anti-fraud obligations, and that retention is governed by Stripe's privacy policy, not ours. Stripe also keeps the customer record it holds for your subscription (your email address, our reference to your account, and any payment method you saved with it).
  • Your own Stripe account, if you connected one to get paid on invoices. That account is yours, not DeductSam's, and deleting your DeductSam account does not delete or close it. When you delete your account, we ask Stripe to disconnect DeductSam from it, and the deletion screen tells you whether Stripe confirmed the disconnection. If it did not, remove DeductSam from your account in your Stripe Dashboard, or contact us and we will remove it on our side. Your Stripe account, its balance and its payment history stay with you at Stripe; close it with Stripe if you no longer need it.
  • What is stored on your own device. Your Sam conversation history and any onboarding answers in progress live in your browser's or the app's storage, not on our servers, so deleting your account cannot erase them. Clear them in the app or by clearing the browser's site data (or deleting the app).
  • Your Apple subscription. If you subscribed inside the DeductSam iOS app, your subscription is billed by Apple and deleting your DeductSam account does not cancel it — Apple, not DeductSam, controls App Store billing. Cancel it in your Apple Account (Settings › [your name] › Subscriptions › DeductSam › Cancel Subscription, or at apps.apple.com/account/subscriptions) before or after deleting your account, or Apple will continue to bill you. Apple keeps its own record of the transactions under its own legal and accounting obligations.
  • Error and diagnostic reports. The crash and error reports described in Section 1 are held by Sentry and are not deleted when you delete your account. They age out automatically on Sentry's retention schedule. These reports contain the error message, a stack trace, app and device version, the originating IP address, and the trail of recent requests and app messages described in Section 1, which can include your account identifier. We do not deliberately include your financial records in them.
  • What OpenAI received. Anything sent to OpenAI to provide a feature (Section 3) — receipt photos, document pages, voice recordings, and messages — may be kept by OpenAI for a period under its own policies. We cannot delete it, and deleting your DeductSam account does not delete it.

6. Your Rights

You have the right to:

  • Access your data — you can see everything you have entered in the app, download your expenses as a CSV file from Finances, and download your Year-End Packet and your receipts from Insights › Year-End. For a copy of anything else we hold about you, contact us.
  • Correct your data — you can edit any expense, business profile field, or account detail directly in the app.
  • Delete your account — you can delete your account from Settings › Profile. Deletion is permanent and cannot be undone. It cancels a web subscription immediately (it does not cancel an Apple subscription — see Section 5).
  • Revoke third-party access — you can disconnect your bank at any time from Settings › Bank sync, and disconnect a Stripe account you connected for invoices from Settings; to remove DeductSam's access completely, also remove DeductSam in your Stripe Dashboard.
  • Opt out of AI processing — you can choose not to use Sam, receipt reading, document reading, and dictation. Expense entry without those features is available on all plans. Two AI steps run on their own, and there is currently no setting to turn them off: when you save an expense our own rules cannot categorise, its merchant, description, notes, and amount are sent to OpenAI to suggest a category; and if you connect a bank, imported transactions our rules cannot place are sent to OpenAI the same way (Section 3).

If you are a resident of California, the EU, or another jurisdiction with specific privacy laws, you may have additional rights. Contact us at admin@deductsam.com to exercise any of these rights.

7. Children's Privacy

The Service is not directed at children, and children do not use it. We do not knowingly collect personal information from a child, and no child can create an account.

There is one place where an adult account holder may record information about their own children: the household tax facts described in Section 1. If you tell us you have children, we store their birth years only — never their names, and never a full date of birth — because a child's age at the end of the tax year is what decides whether certain credits apply to your return. You enter it, you can change or remove it at any time in Settings, and it is deleted with your account.

If you believe a child has provided us information directly, please contact us and we will delete it promptly.

8. Cookies and Tracking

We use a minimal set of cookies:

  • Sign-in — the app keeps your sign-in session in your browser's local storage (not a cookie) until you sign out.
  • Preferences and app state — your cookie-consent choice, billing view (monthly/annual), your Sam conversation history, onboarding answers in progress, and similar settings are kept in local storage on your device and are not sent to our servers except as described in this policy.
  • Our marketing website — deductsam.com uses Microsoft Clarity cookies only if you accept them in the cookie banner (see Section 3). The DeductSam app does not use Clarity.

We do not use advertising cookies, cross-site tracking pixels, or third-party analytics that build profiles across the web.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by email or by displaying a notice in the app at least 14 days before the change takes effect. Continued use of the Service after a change constitutes your acceptance of the updated policy.

10. Contact Us

If you have questions, concerns, or requests regarding your privacy, please contact us at:

DeductSam LLC
Email: admin@deductsam.com

We will respond to all privacy inquiries within 10 business days.