Privacy Policy

1. Who is responsible

ForemanPay is run by Milan Fatić, an individual based in New York, USA. It is not a company. In this policy, "ForemanPay", "we" and "us" mean Milan Fatić.

2. Whose information this covers

Three groups of people:

• Account holders. Contractors and foremen who sign up and use the app.
• Workers named in the records. Foremen and helpers whose pay is on a statement (the weekly payroll PDF) or is typed in by an account holder. They may not use ForemanPay themselves.
• Moving customers. Each job line keeps the job name as printed on the statement. It usually includes a customer's last name and a job number.

The account holder decides to put this information into ForemanPay. We store it for them. The app does not notify the people named.

If you are a worker and want to know what a contractor keeps about you, ask that contractor first. The same applies if you want it corrected or removed. You can also write to us at support@foremanpay.me. If you are a moving customer, write to us.

3. What we collect

About your account:

• At sign-up: account type (contractor or foreman), your company name or your own name, your email and a password.
• Subscription details: your plan, its status, and two ID numbers from Stripe (one for you as a customer, one for your subscription).
• The trusted sender email addresses you list for email import (contractor accounts).
• Bug reports and suggestions you send: your message, your account email and the time. If a page fails, the app sends us a short automatic error report (the error message and the page).

From statements and from what you type in:

• Each statement: file name, week, the company name printed on it, and totals. On a contractor account, also the PDF file itself.
• Each job: date, job name as printed, foreman name, rate (percent), job type, commission and tip.
• Deductions, reimbursements and adjustments: date, name, description and amount.
• Pay rates, helper names and each helper's share of a job (a percent or a dollar amount), and jobs you mark as excluded.
• Payout records: who, how much, the method you pick (Zelle, cash, check or other), the date and any note. This is a record only. ForemanPay does not move money.
• Pay slips you make: one foreman's week (jobs, deductions, helpers, totals, payout) and its code.
• Anything you type on the Earnings page, in the Job Log and in note fields.

The app also keeps a usage log. It records actions such as signing in, importing a statement, marking a payout or exporting to Excel. It saves the account and the time with each action. We use this to count usage and find problems. It does not record workers' names or pay. Two exceptions: the week of a statement, and the totals of a statement that was not fully read. Our own log does not record your IP address or device.

4. What we do not collect

• Card numbers. You enter payment details on Stripe's pages. They never reach our servers.
• Social Security numbers, tax IDs, bank account details, phone numbers, home addresses or dates of birth. The app does not ask for them. It also does not keep the tax number (EIN), address or email printed at the top of a statement, or the email addresses printed next to reimbursements, except that a contractor account keeps the PDF file itself, with everything printed on it (section 5). Please do not type such details into note fields.
• Advertising or analytics trackers. There are none in the app, and no third-party tracking scripts.

We do not sell personal information, we do not share it for advertising, and we do not send marketing emails. The only emails we send are account emails (such as sign-up confirmation and password reset), replies to your messages, and important notices about ForemanPay, such as a price change or a change to this policy or the Terms. Stripe may also send you receipts.

5. Statement PDFs and emailed statements

When you upload a PDF, it is read inside your browser, and the rows read from it and the file name are sent to our server and saved to your account. On a contractor account the PDF file itself is saved too, so you can open it again from the Statements and Reports pages; it opens through a private link that our server makes for your account and that works for one minute. On a foreman account the file is never saved: the browser sends all the rows it read, and our server keeps only the rows under your own name. The others are dropped before anything is saved.

When a statement is emailed to your email import address (contractor accounts), the email passes through SendGrid to our server. The server checks the sender, reads the attached PDF, and saves the same rows, the file name and, on a contractor account, the PDF file. The email and its text are not stored, and neither is a PDF that is not imported. If an email is refused, our hosting provider's log may record the sender's address.

6. Cookies and browser storage

ForemanPay uses cookies only for signing in. One cookie keeps you signed in. A second, short-lived cookie is used while you confirm your email or reset your password. The app cannot work without them.

Your browser also keeps a few settings on your device: language, light or dark theme, how you arranged the menu, the last rate you typed, and the foreman you last selected on the Earnings page. Two short-lived markers are kept until you close the tab, so that a sign-in and a visit are each counted once. All of these stay on your device and are not sent to us.

There are no advertising or analytics cookies. That is why you see no cookie banner. Stripe's checkout and billing pages are Stripe's own website and use Stripe's own cookies.

Do Not Track: ForemanPay does not track you across other websites, and it lets no one else do so. So the app does nothing different when your browser sends a "Do Not Track" or similar signal.

7. How we use information

• To run ForemanPay: calculate payouts, show your reports and history, make pay slips.
• To bill your subscription.
• To answer you and fix problems.
• To keep accounts secure and prevent misuse.
• To count basic usage so we know what to improve.

We do not use your information for advertising.

8. Who receives it

We use these service providers. Each gets only what it needs for its job:

• Supabase: sign-in, the database where all account and statement records are kept, and the file storage where contractor accounts' statement PDFs are kept. It also sends the account emails and keeps its own technical logs, such as sign-in times and IP addresses.
• Vercel: hosts ForemanPay and runs our server. Like any web host, it handles every request, including your IP address, and keeps technical logs.
• Stripe: payments and subscriptions. We send Stripe your email, an internal account ID and the plan you chose. You give Stripe your payment and billing details directly. Stripe handles them under its own privacy policy (stripe.com/privacy).
• SendGrid (Twilio): receives emails sent to your email import address and passes them to our server.
• ImprovMX: forwards the email you send to support@foremanpay.me to our mailbox at Google (Gmail), where we read and answer it.

Also:

• Us. Milan Fatić can see a list of accounts: company name, email, plan, status, number of statements, bug reports and recent activity. He also has database access to all records, including the stored PDF files. He uses this access to give support, fix problems and keep ForemanPay running.
• Anyone who has a pay slip code. A pay slip code or QR works like a key. Anyone who is signed in to ForemanPay and has the code can open that pay slip and import a copy into their own account. That copy stays there even if you later delete your statement. Share the code only with the person it is for.
• Authorities, when the law requires it.

If ForemanPay is ever transferred to a new owner, the information moves with it. We will tell account holders by email or in the app, and update this policy.

9. Where it is stored

The database and the stored PDF files are in the United States. Supabase, Vercel, Stripe and SendGrid are US companies. If you use ForemanPay from another country, your information is sent to and kept in the USA. Email to support@foremanpay.me passes through ImprovMX, a French company, on its way to our mailbox.

10. How long we keep it, and how to delete

We do not delete anything automatically. Your records stay until you delete them or ask us to delete them. If that ever changes, we will update this policy and email account holders before anything is removed.

This is also true after a trial ends, a payment fails or a subscription is canceled. The account becomes read-only (you can still see everything, but you cannot import statements or change your records), and nothing is removed.

What you can delete yourself in the app:

• A statement. This also removes that week's jobs, deductions, helper splits, exclusions, payout records and pay slips, and its PDF file if one was kept.
• A single payout record, helper split, Earnings entry or Job Log job.

Deleting a statement does not remove everything. Foreman names in your roster, rate settings, the week of the statement and the usage log stay.

While an account is read-only, the app does not offer any of these deletions (only the sample statement can be removed). Statements also cannot be deleted while your crew is over your plan's foreman limit. Write to us and we will delete what you ask.

There is no "delete account" button. To delete your account and all its records, or anything you cannot remove yourself, write to support@foremanpay.me from your account email. We delete it manually.

What may remain after deletion: Stripe keeps its own payment records under its own rules. We may keep invoices, payment records and our emails with you where tax, accounting or legal duties require it. Our providers delete their technical logs on their own schedules.

11. Security

What we do:

• Each account can read and change only its own records. The database itself enforces this, and a stored PDF opens only through a short-lived link that our server makes for the account the statement belongs to.
• ForemanPay uses an encrypted connection (HTTPS).
• New passwords must be at least 10 characters. Our sign-in provider handles them. It stores a protected (hashed) form, not the password itself.
• Emailed statements are accepted only from your trusted senders, and only when the email passes the usual checks against faked senders.
• Pay slip codes are random and stop working after a time. An account that enters too many wrong codes has to wait before it can try again.

No system is perfectly secure. We cannot promise that nothing will ever go wrong. Use a password you do not use anywhere else.

If we learn of a security breach that affects your information, we will tell you. We will also tell the authorities when the law requires it.

12. Your choices and rights

You can ask us to:

• tell you what information we hold about you and send you a copy;
• correct something that is wrong;
• delete your information.

Write to support@foremanpay.me. We may ask you to write from your account email so we know it is you. If you are a worker named in a contractor's records, we may need to involve that contractor, because the records are in their account.

You can already export reports and history to Excel in the app. There is no single button that exports everything. Ask us if you need more.

We handle these requests the same way for everyone, wherever you live, and we will not treat you worse for making one. If a law where you live gives you more rights than these, write to support@foremanpay.me.

13. Children

ForemanPay is a work tool for adults. It is not meant for anyone under 18, and we do not knowingly collect information from children. If you believe a child has given us information, write to us and we will delete it.

14. Changes to this policy

If we change this policy, we will post the new version on this page and change the effective date. If a change is significant, we will also tell account holders, by email or with a notice in the app.

15. Contact

Milan Fatić, New York, USA.

Email: support@foremanpay.me