PRIVACY
Privacy Policy
Last updated October 15, 2026
Information you provide
The service processes account and authentication information, your chosen card name, profile photo, age confirmation, verified city and Home Office, biography, interests, Member Number, and card preferences. Your card name is not a login credential and may match another member’s name.
Community activity may include posts, comments, likes, follows, reports, uploaded images, notification state, and Store wishlist choices. Password authentication is handled by Supabase Auth.
Attendance and personal plans
Check-in records, elapsed time, attendance history, and calendar events are private to the account owner. They are protected by database access policies and are not published to other members or visitors.
When you choose a public check-in, members and visitors can see the public status, Office, and current activity. Exact duration and personal calendar details remain private. A private check-in is not exposed.
Visibility choices
Posts may be Public, Office only, or Followers only. Profile and current activity sharing follow the choices presented in the product. Post visibility and check-in privacy are separate settings.
Public Employee pages and card sharing
Public Employee links can be opened without an account. They show your display name, Employee Number, public profile photo, Home Office, public bio, identity interests, and join date when enabled. Public activity follows your visibility choices.
Shared card images show email as Private and omit uploaded signatures by default. Authentication email, private activity, recorded hours, calendars, and account security data are not included in public Employee pages or shared card images.
How information is used
Information is used to authenticate accounts, complete onboarding, activate verified Offices, display Member Cards, operate community and attendance features, prevent abuse, investigate reports, and maintain service security.
We process the information necessary to provide the account and features you request. Optional profile details, public sharing, and Google sign-in follow your choices; choosing not to use them does not require consent to optional usage analytics. We do not treat accepting the Terms as blanket consent to unrelated processing. Any processing that requires separate consent must be presented separately before it begins.
International processing
THE COMPANY is operated by the individual in South Korea identified below. The following providers receive information when you use the relevant features, through encrypted network connections. Authentication and content requests are transmitted when you use the service; recovery copies are transferred during scheduled backups and approved recovery operations. A provider’s registered country is not necessarily the location of every server or support team.
For overseas processing and storage necessary to provide your requested account, features, recovery, and related support, our basis is Article 28-8(1)(3)(a) of South Korea’s Personal Information Protection Act: necessary processing or storage for entering into or performing a contract, with the required transfer details disclosed in the privacy policy. This basis does not extend to a provider’s unrelated independent purposes. Refusal options and their effects are explained under Your choices and contact.
Our selected database, authentication, file storage, application server region and private recovery-file storage are in Tokyo, Japan. This location does not describe every network request or provider log. The sections below separate stored member data, connection information, conditional support access and optional services. A corporate address or a provider’s worldwide offices alone is not evidence that your information is sent there.
South Korean Personal Information Protection Act, Article 28-8
Supabase — accounts, database, and files
Recipient: Supabase Pte. Ltd. (Singapore), with Supabase, Inc. (United States) supporting operations. Contact: privacy@supabase.io. Supabase processes authentication email and credentials, provider identity records, profile and card settings, member content and relationships, private attendance and calendar records, uploaded photos and signatures, and security metadata needed for the features you use.
Account storage: our database, Auth service, Storage objects and database backups use Tokyo, Japan. Operational logs are a separate flow: Supabase documents API and authentication logs with request metadata, including IP-address fields, and states that service logs are ingested and stored in EU data centers. The reviewed documents do not name the EU country or countries used by our project. We have not inferred those countries from the database region or the visitor’s location.
Support access is conditional on a support request or security incident. Supabase identifies its US affiliate as providing support and operations when necessary; its worldwide staffing statement does not establish routine disclosure of every member record to every staff location. Storage CDN delivery can cache a requested object outside Japan. Public photos can contain personal information; brand-only images and private account records are not treated as the same flow. When you use account or community features, requests are sent to Supabase and public photos may be delivered through its Storage CDN. We will update this notice when more specific processing-location information is confirmed.
Retention: active member data follows the account and content deletion rules below. Supabase’s DPA covers retention during our service agreement, subject to earlier deletion requests through service functionality. When our agreement ends, it requires deletion of covered copies at the end of a 30-day data-return window. That window concerns our provider contract ending, not an individual member’s account deletion. Covered personal data also includes information generated in providing the service. Our current Pro plan provides seven days of database backup access; this access window does not establish final erasure of internal logs or residual copies.
Supabase processing locations and privacy contact
Supabase data processing agreement and subprocessors
Supabase current subprocessor list
Vercel — website delivery and recovery storage
Recipient: Vercel Inc. (United States). Contact: privacy@vercel.com. Vercel processes network and device information, request and security metadata, and the information needed to handle application requests and responses. Its private storage holds encrypted uploaded-file backups and limited recovery evidence. Recovery evidence includes account-linked deletion records and a separate number-only allocation record.
Our application server and private recovery-file store use Tokyo, Japan. Vercel identifies the United States as its primary processing location. For page delivery, its published TLS-termination and cache regions are in Australia, Brazil, Canada, France, Germany, Hong Kong, India, Ireland, Japan, Singapore, South Africa, South Korea, Sweden, the United Kingdom and the United States. Requests are routed according to visitor location and availability; this is the delivery-region scope, not a claim that every visit reaches every country or that account databases are replicated to each location. Network ingress and DDoS routing points are distinct from these TLS/cache regions.
Retention: our encrypted recovery copies follow the eight-day policy and safeguards below. For customer data covered by its DPA, Vercel supports deletion during our contract and deletion within a commercially reasonable time after termination, subject to legal retention obligations. The contract does not specify a fixed maximum number of days for that termination process.
Vercel’s DPA distinguishes customer content processed on our instructions from service-generated information processed by Vercel as a controller under its Privacy Notice. That distinction does not exempt our hosted member data from transfer requirements. When you use the service, Vercel handles the application requests needed to provide the requested features, as well as connection information needed to deliver and secure the site. Optional usage analytics operates only after you select Allow analytics, as described below. Provider-generated information follows its stated purpose-based deletion or anonymization rule, not an invented fixed retention period.
Vercel data processing agreement
Vercel delivery regions and network routing
Optional usage analytics — your choice
With your permission, we use Vercel Web Analytics to count visits and interactions such as starting and completing sign-up, and to understand which sources bring visitors to THE COMPANY. Select Allow analytics to enable this optional processing, or Decline to use the service without it. Privacy choices at the bottom of the site lets you change your decision. We also respect browser Do Not Track and Global Privacy Control signals.
We send sanitized page paths, event names and fixed source labels such as Product Hunt or Instagram. We remove URL query strings and fragments, exclude authentication pages and mask public Member Numbers in paths. We do not send names, email addresses, account IDs, passwords, authentication tokens, community text, private attendance or calendar details as analytics properties. Vercel also processes connection and device information as described in its linked analytics documentation.
After permission, this browser stores a source label for up to 30 days to associate a later sign-up with the initial visit. A timestamp suppresses repeated visit events for 30 minutes in the same tab; a sign-up timestamp suppresses repeat confirmations on this browser for 30 days. Your allow or decline preference remains until you change it or clear site storage. Withdrawal clears these attribution records and stops future analytics; it does not automatically erase prior aggregated reports. Counts exclude visitors who decline, block analytics, or complete sign-up on a different browser without the original attribution.
Recipient: Vercel Inc. (United States), for optional analytics processing through encrypted network requests after your choice. Its analytics handling and contact information are linked below. The provider’s visitor-identification lifetime and reporting window are not a guarantee of final deletion of every provider record. Contact our operator with a request about prior analytics processing. No Meta advertising pixel is installed by this feature, and we do not sell member data or use private activity for advertising.
Vercel Web Analytics data handling
Google — optional sign-in
Google sign-in is optional. When selected, you authenticate directly with Google LLC (United States). Google sends the basic identity information needed for sign-in to Supabase Auth in our selected Tokyo region: your Google account identifier, email, profile name, and available profile photo. We do not receive your Google password or upload your community content and private attendance records to Google as part of this sign-in. Email-and-password sign-in is available without selecting Google sign-in.
Google’s direct collection during authentication and its international identity-service processing follow its own privacy and retention policies. They are distinct from the identity information our service receives and stores through Supabase. The Workspace support-mail agreement below does not govern your personal Google account. Deleting your THE COMPANY account does not delete your Google account.
Google OpenID Connect identity information
Google Workspace — support correspondence
We use Google Workspace Business Starter for support@onecompanyoneearth.com. The Workspace contracting entity for our South Korean billing location is Google Asia Pacific Pte. Ltd. (Singapore), with Google affiliates and service subprocessors handling the service. Contact and privacy request options are linked below. This mailbox processes sender and recipient addresses, message content and attachments you send, and delivery metadata so we can receive and answer enquiries.
Information is transferred through email and encrypted service connections when you contact us or we reply. We have not configured a Japan-only mail region. Google’s published possible processing countries for Workspace core-service data centers, maintenance, support, and security review are Argentina, Australia, Belgium, Brazil, Bulgaria, Canada, Chile, Colombia, Denmark, El Salvador, Finland, France, Germany, Hong Kong, India, Ireland, Israel, Italy, Japan, Malaysia, Mexico, the Netherlands, New Zealand, the Philippines, Poland, Romania, Singapore, South Korea, Spain, Sri Lanka, Sweden, Switzerland, Taiwan, the United Kingdom, and the United States.
This is the published scope of possible processing, not a claim that each message is sent to every location. Google’s linked list identifies the entities, countries, and activity-specific limits. Its third-party technical-support providers access stored customer data only when the customer explicitly enables access in a support case.
Our mailbox follows the support retention rule below. Under Google’s Cloud Data Processing Addendum, deletion that is no longer recoverable by the customer starts a provider deletion instruction, to be completed within 180 days subject to applicable legal retention exceptions. This is separate from our mailbox cleanup period and does not promise immediate erasure of provider copies. We do not automatically forward support correspondence to the operator’s personal Gmail account.
Google Workspace contracting entity
Google Cloud Data Processing Addendum
Resend — authentication email delivery
Recipient: Plus Five Five, Inc., trading as Resend (United States). Contact: privacy@resend.com. Supabase sends authentication emails through Resend from no-reply@auth.onecompanyoneearth.com. This transfers the recipient email address, authentication message and one-time link, and delivery metadata over encrypted connections when an authentication email is requested. It does not send your password, profile photo, attendance records, or community content.
Resend stores message content and delivery logs in the United States. Its standard plans retain email and log data for 30 days, with seven-day backups; its DPA separately provides for remaining customer-data deletion within 90 days after service termination. Provider legal and security obligations can affect retained records. Resend lists its subprocessors and describes limited trust-and-safety processing. We do not use its AI editor or AI support agent with authentication messages, and open and click tracking are disabled.
THE COMPANY does not create an additional sent-mail archive of authentication messages or links in its application database or support mailbox. This does not remove Resend’s delivery copies, Supabase’s necessary authentication records, or copies retained by recipients and their mail providers. Requests concerning an earlier message can be made through our support contact; provider-assisted early deletion is subject to the applicable service and legal requirements.
Resend data location, retention and privacy practices
Retention and account deletion
Account information and content are kept to provide your account and the features you use. You can edit supported profile, card, visibility, community, attendance, and calendar information within the app, delete supported content, or request account deletion. A completed account deletion removes the active account, owned content, and uploaded files. A failed or uncertain deletion is investigated rather than described as completed.
Employee Numbers are never reused. We keep the number and retirement record permanently without your name, email, or account identifier in that ledger.
Encrypted file backups and the minimum account-linked evidence needed to prevent a deleted account from returning after a restore follow an eight-day retention policy. Deletion evidence is removed only after older restorable backups have expired and no active restore still needs it. An unresolved deletion or retention hold is reviewed by the operator, with its purpose and duration assessed separately; it is not automatically kept forever. Backup copies are restricted to recovery and are not returned to normal service without reapplying completed deletions.
Support email is scheduled for removal within 30 days after the request is resolved, unless a specific legal obligation or dispute requires a separately documented period.
Provider security logs and older backups
Providers retain security and service logs and rotate backups under their contracts and retention settings. We keep provider authentication audit logging, without an additional copy in our application database. We do not promise that deleting live account data immediately erases every provider backup or internal log. Provider dashboard access periods are not guarantees of physical destruction.
Your choices and contact
You may request access, correction, deletion, restriction of processing, or withdrawal of applicable consent through the operator contact below. Tell us the right you want to exercise and the account or content concerned. We may need proportionate verification of account ownership before acting. We will reply using that contact channel within the applicable legal period, explain any refusal or delay, and identify a specific legal basis if retention is required. Do not send your password or authentication codes. The operator shown below is also responsible for privacy requests.
To object to international processing, contact support@onecompanyoneearth.com and identify the processing you want stopped. You can decline Google sign-in and use email sign-in. Essential overseas account hosting and email delivery cannot be disabled while retaining the affected account functions; you can choose not to register or request account deletion. You can decline optional analytics or withdraw permission through Privacy choices at the bottom of the site. We will explain available measures and any legal limits before acting.
The service is for adults aged 18 and over. Session cookies and local browser storage support sign-in, account security, and your selected preferences. Blocking necessary browser storage may prevent those features from working.
Access controls and encryption protect restricted information, but no online service can guarantee absolute security. Material policy changes will be published here with an updated date.