Privacy Policy
This policy explains what information PFOS collects, why, where it is kept and who can see it. PFOS is operated by Sirbu Systems (“we”).
PFOS is an invitation-only business application. It is used by organizations (“customer organizations”) and the people they invite. It is not directed at consumers or at children, and it is not intended for use by anyone under 18.
Information we collect
From Google, when you sign in. PFOS uses “Sign in with Google”. We receive your name, your email address, your profile picture, and Google’s identifier for your account. We request only Google’s basic profile permissions (openid, email, profile). We do not request or receive access to your Gmail, Google Drive, Google Calendar, contacts, or any other Google data, and we never see your Google password.
Account and access information. The email address an administrator invited, who invited it and when, your role and membership status in your organization, and whether you have set up two-step verification. If you set up an authenticator app, the information needed to check its codes is stored by our authentication provider.
Business records. The information you and your colleagues enter into PFOS for your organization’s work — for example products, prices, job and customer records, notes and uploaded files. This information belongs to the customer organization.
Activity and security records. PFOS keeps an audit trail of changes to records, changes to who has access, and refused requests. Entries include the account involved, the time, your IP address and your browser’s identification string. Our authentication and hosting providers also keep their own standard logs, including of sign-ins.
In your browser. PFOS stores your sign-in session and a few display preferences in your browser’s local storage so that you stay signed in. It does not use advertising or cross-site tracking cookies and does not run third-party analytics. The application loads its typefaces from Google Fonts, which means your browser makes a request to Google when the application opens. The pages on this public site load nothing from any third party.
How we use information
- To confirm who you are and that you were invited.
- To decide what you may see and do, according to the role your organization gave you.
- To provide the application to your organization.
- To keep the service secure, investigate problems and keep an accountable record of changes.
We do not sell personal information. We do not use it for advertising. We do not use information received from Google for any purpose other than signing you in, matching you to your invitation, and identifying you to your colleagues inside PFOS.
PFOS’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Artificial intelligence
PFOS does not currently use artificial-intelligence models to process personal information or your organization’s records, and does not send them to any AI provider. We do not use information received from Google, or your organization’s records, to develop or train artificial-intelligence models. If PFOS adds AI-assisted features, we will update this policy to describe what they process and which providers are involved before those features are made available.
Who can see it
Within your organization. Administrators of your organization can see who its members are, their email addresses, roles and status. Other members see records according to their roles. People in one customer organization cannot see another organization’s records.
Service providers. We use a small number of providers to run PFOS. They process information on our behalf:
- Google — sign-in (identity verification).
- Supabase — authentication, the database, and private file storage.
- Render — hosting of the application and its API.
Otherwise. We do not share personal information with other third parties, except where required by law or to protect the security of the service and its users.
Where it is kept
PFOS’s data is stored and processed in the United States (Oregon). If you use PFOS from elsewhere, your information is transferred to and processed there.
How it is protected
- Connections to PFOS and to its database are encrypted in transit.
- Access is by invitation only, and every request is checked against your current membership and role.
- Roles that can see or change sensitive information must use two-step verification.
- Each organization’s records are separated from every other organization’s at the database level.
- Uploaded files are stored privately and are reachable only through short-lived links issued to permitted users.
No system is perfectly secure, and we cannot guarantee that information will never be accessed without authorization. PFOS is in beta and has not undergone an independent security audit or certification.
How long it is kept
We have not set fixed retention periods during the beta. In practice:
- Account and membership records are kept for as long as your organization uses PFOS. When an administrator removes your access you can no longer sign in to that organization’s records, but the record that you were a member is marked as ended rather than erased. Invitations that expire or are cancelled are also kept, as a record of who was invited.
- Business records are kept for as long as the customer organization uses PFOS. Your name and email address stay attached to the records you created or changed, so that the organization’s history stays accurate.
- Audit and business-history records are append-only: the application does not edit or delete them.
- Logs and backups kept by our service providers may hold copies for a limited time after information is removed from PFOS itself.
Your choices and requests
You can ask what personal information PFOS holds about you, ask for it to be corrected, and ask for your access to be removed and your sign-in account deleted. We will delete what we can; the records described above as kept — the fact of your membership, your name on records you created, and audit entries — are not erased on request. Business records belong to the customer organization, so requests about those are best made to your organization’s administrator, who controls them. Depending on where you live, you may have additional rights under local law.
You can remove PFOS’s access to your Google account at any time from your Google Account’s security settings; you will then be unable to sign in until you grant it again.
To make a request or ask a question about this policy, contact dion@sirbusystems.com.
Changes to this policy
If this policy changes, the new version will be posted on this page with a new effective date.