Privacy Policy
Anastasis Professional Services LLC ("Anastasis," "we," "us") provides a remote workforce platform connecting companies with operators. This policy explains what personal data we collect, why, and your rights under GDPR, CCPA, and other applicable privacy laws.
1. Data Controller
Anastasis Professional Services LLC
Contact: privacy@anapro.co
For EU/UK data subjects: You may also lodge a complaint with your local supervisory authority.
2. What We Collect
2.1 Account Data
When you register, we process: name, email address, and authentication credentials. Passwords are hashed by Anastasis using a strong one-way algorithm — we store only the hash and never the plaintext password. Your signed-in state is maintained with a secure, HttpOnly session cookie.
2.2 Profile Data
Contractors: skills, assessments (a self-reported work style profile, skill and English test results, internet speed, PC specs), work history, government ID (for compliance), payout account details (handled by Stripe). Clients: company name, role specifications, team member accounts.
2.3 Work Activity Data
Timesheets, screen captures (domain-level only — never full URLs), application URLs visited, approval decisions, and audit logs. Screen captures are stored as short-lived signed URLs with 15-minute expiry.
2.4 Payment Data
Card numbers, CVV, and full bank details never touch our servers. Payments are processed by Stripe (PCI DSS Level 1). We store only payment status, charge IDs, and payout references.
2.5 Communications
Messages sent through the platform, support tickets, and booking call requests. We do not record calls without explicit consent.
2.6 Portal Diagnostics
When you are signed in to the contractor or client portal, we record how the portal itself behaves so we can find and fix faults. This covers errors and crashes, failed or slow requests, permission refusals, signs that a screen is not working (such as repeatedly clicking a control that does nothing, or retrying the same action), and a record of the screens opened and the actions taken, with the time spent on each. These records are linked to your account.
We record the address of the screen, never its contents. We do not capture anything you type — no form fields, no message text, no search terms — and no request or response bodies. Record identifiers in addresses are replaced with a placeholder before storage, so a page address is kept as/contractor/hired/timesheets/:id rather than naming a specific record. This is diagnostic data about our software, not a measure of your productivity, and it is not used to evaluate your work. Hours are verified only through the time-tracking records described in 2.3.
2.7 Google Calendar integration
Connecting Google Calendar is optional. Clients and hired contractors can do it from Settings; nothing is requested from Google unless you choose Connect.
What we access. When you connect, Google asks you to approve three permissions: openid and email, which give us the address of the Google account you connected so Settings can show which account it is, and calendar.events, which lets us add events to your calendar.
How we use it. When an interview is confirmed, we create one event on your primary Google Calendar. The event has the interview time and duration, and the meeting link. If the interview has no link yet and you are the client who scheduled it, we ask Google to attach a Google Meet link to that event. The event title is “Interview with” the candidate’s first name and last initial on a client’s calendar, and “Anastasis interview” on a contractor’s; a client’s own note for the interview, if they wrote one, goes in the description. We only add events. We do not read, list, change or delete any event on your calendar, including the ones we created, and we do not read any other calendar data. We use this information only to provide this scheduling feature. If Anastasis already sent you a calendar invite for the interview (see 2.8), we don’t add a second event.
Sharing. We do not sell Google user data, share it with other third parties, use it for advertising, or use it to train or run AI or machine learning models. The only place it is sent is to Google, to create the event.
Protection. The access and refresh tokens Google gives us are encrypted (AES-256-GCM) before they are stored in our database, are used only on our servers to talk to Google, and are never sent to the browser or to any other service. Access to the database is limited to our service.
Disconnecting and deletion. Choose Disconnect in Settings at any time. We immediately delete the stored tokens and the connected email address, and we ask Google to revoke the permission. Events already on your calendar stay there; they belong to your calendar, so delete them there if you want them gone. You can also remove Anastasis in your Google Account’s third-party access settings. If your account is closed, we do the same: the tokens and email address are deleted and the permission is revoked with Google. We keep this data only while the connection is active.
2.8 Interview calendar invites
When a client schedules an interview, we create the event on our own Google Workspace calendar (interviews@anapro.co), and Google emails the invite to the people in it: the client who scheduled it, any teammates they chose, and the candidate. Nobody needs to connect a calendar for this.
What is sent to Google. The interview time and duration, a title with the candidate’s first name and last initial and the client’s company name, the client’s note if they wrote one, the meeting link, and the email addresses of the people invited. The invite is set so guests can’t see each other’s email addresses.
Meeting rooms. Unless the client pastes their own link, we create a Google Meet room for the interview that anyone with the link can join, with automatic recording, transcripts and notes turned off.
Replies. We read the candidate’s reply to the invite (yes, no or no answer yet) so that answering it accepts or declines the interview in the portal. We read nothing else from anyone’s calendar.
Changes and retention. When an interview moves, Google sends the update; when it is cancelled or declined, we delete the event and Google tells the guests. Events for interviews that took place stay on our calendar as the record of the interview, under the retention rules in section 5.
Our use of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
3. Legal Basis for Processing (GDPR)
- Contractual necessity: Account creation, payment processing, platform functionality.
- Legitimate interest: Platform security, fraud prevention, service improvement, aggregated analytics.
- Consent: Assessment tests, screen activity capture during clocked-in sessions, marketing communications (opt-in only).
- Legal obligation: Tax records, compliance with labor laws, law enforcement requests.
4. Third-Party Data Processors
We use the following processors who may access personal data to provide services:
| Processor | Purpose | Privacy Policy |
|---|---|---|
| Stripe, Inc. | Payment processing, payouts | stripe.com/privacy |
| Cloudflare, Inc. | Hosting, CDN, serverless functions | cloudflare.com/privacypolicy |
| Google LLC | Interview calendar invites and Google Meet rooms (see 2.8); calendar events if you connect Google Calendar (see 2.7) | policies.google.com/privacy |
5. Data Retention
- Account data: Retained while account is active. Deleted 90 days after account closure, unless required by law.
- Work activity data: Screenshots are kept for 90 days, then deleted. A screenshot behind hours that are still under review or disputed is kept until those hours are settled, and deleted 90 days after that. Timesheets and URLs retained for the duration of the client engagement plus 12 months.
- Payment records: Retained 7 years for tax compliance.
- Audit logs: Retained indefinitely for security and compliance, with PII redacted from purge logs.
- Google Calendar connection: The encrypted tokens and connected email address are kept while the connection is active and deleted when you disconnect or your account is closed (see 2.7).
- Portal diagnostics: Individual event records are deleted after 30 days. A daily summary built from them is kept for longer; it groups faults across everyone affected, and includes per-person totals (screens opened, actions taken, time on the portal) but not the individual events behind them.
6. Data Storage & Transfers
Data is stored in the United States on infrastructure provided by Cloudflare and Stripe. For EU/UK users: data is transferred under Standard Contractual Clauses (SCCs). We apply encryption at rest and in transit for all personal data.
7. Your Rights
7.1 GDPR Rights (EU/UK Residents)
- Access: Request a copy of your personal data.
- Rectification: Correct inaccurate or incomplete data.
- Erasure: Request deletion ("right to be forgotten"), subject to legal retention requirements.
- Portability: Receive your data in a machine-readable format.
- Objection: Object to processing based on legitimate interest.
- Restriction: Limit processing while a dispute is resolved.
7.2 CCPA Rights (California Residents)
- Know: Request categories and specific pieces of personal data collected.
- Delete: Request deletion of personal data.
- Opt-out: We do not sell personal data. No opt-out is needed.
- Non-discrimination: Exercising your rights will not affect service quality.
7.3 How to Submit a Request
To exercise any of the above rights, email privacy@anapro.co with:
- Your full name and the email address associated with your account.
- A description of the right you wish to exercise (access, deletion, correction, or portability).
- For access requests: we will provide your data within 30 days in a portable, machine-readable format.
- For deletion requests: we will confirm completion within 30 days, subject to legal retention obligations.
You may also designate an authorized agent to submit a request on your behalf by providing written authorization signed by you. We do not charge fees for reasonable requests. We do not discriminate against users who exercise their privacy rights.
8. Children's Privacy
Our platform is not intended for users under 18. We do not knowingly collect data from children under 13 (COPPA) or 16 (GDPR). If you believe a minor has provided personal data, contact us immediately for deletion.
9. Cookies & Analytics
We use essential cookies for authentication and session management. We do not use advertising or cross-site tracking cookies. Our marketing pages use self-hosted, cookieless analytics (Umami) that we run on our own infrastructure: it records aggregated page views and clicks without cookies, without persistent identifiers, and without sharing data with any third party. No cookie consent banner is required for essential-only cookies under current ePrivacy guidance, however we disclose this use transparently.
That cookieless, aggregated analytics runs on our public marketing pages only. The signed-in portals are not covered by it; what we record there is the diagnostic data described in 2.6, which is linked to your account and kept for 30 days.
10. Security & Breach Notification
We apply encryption at rest (database) and in transit (TLS 1.3). In the event of a personal data breach, we will notify affected users and relevant authorities within 72 hours of discovery, as required by GDPR Art. 33-34.
11. Changes to This Policy
We will post updates on this page and notify active users of material changes via email. Continued use after changes constitutes acceptance unless consent is legally required.
12. Contact
Anastasis Professional Services LLC
Email: privacy@anapro.co
Response time: Within 30 days for data subject requests, 72 hours for breach notifications.