Privacy Policy

How Unlimited Coders collects, uses, stores, and protects information

Last updated:

This is the general Privacy Policy of Unlimited Coders. It covers our corporate website at unlimitedcoders.com, our business communications, software-development and consulting services, customer and partner relationships, and the websites, platforms and mobile applications that we operate under this Policy (together, the “Services”).

It also includes specific disclosures for Teamora App, its web, iOS and Android versions, and the Google, Microsoft and Apple services used for calendar integration, email, mobile notifications and application distribution. The information we handle depends on which Service or feature you use.

1. Overview and Scope

Unlimited Coders develops software and digital services for businesses and organizations. This Policy explains what personal information we handle, why we handle it, who may receive it, how it is protected and retained, and how you can exercise your privacy choices.

For our corporate website, business enquiries and administration of our own commercial relationships, Unlimited Coders determines the purposes for which the relevant information is used. When we develop, host, maintain or support a system on a customer's behalf, that customer may determine how information in that system is processed, and we act according to the applicable service agreement and instructions. A customer's own privacy notice applies to the processing that the customer controls.

Teamora App is a product of Unlimited Coders, available at teamora.unlimitedcoders.com. Where an employer or another organization provides your Teamora account, it determines its workplace policies, authorized users and employment-record requirements. Unlimited Coders operates the service for that organization and handles the information needed to administer, secure and support it.

Product-specific notices may provide additional detail. The Google-data restrictions in Section 9: Google services take precedence over general marketing, sharing, business-transfer or retention wording in this Policy for information received through Google APIs.

2. Updates to This Policy

We may update this Policy when our Services, data practices or applicable requirements change. We publish the revised text here and update the date above. We provide additional notice or obtain consent where required.

Before using Google user data for a new purpose or accessing a type of Google data that was not previously disclosed, we will update the relevant privacy disclosures, notify affected users and obtain their consent to the new access or use. A general update to this Policy does not authorize undisclosed use of connected-account information.

3. Information Collection

Website enquiries and business communications

When you contact us through a form, email, chat or another communication channel, we handle the information you provide, such as your name, email address, telephone number, organization, role, message, project requirements and correspondence. If you send an application, proposal, portfolio or other document, we handle it for the purpose for which you sent it.

Customers, suppliers, partners and client projects

In a business relationship, we may handle contact-person details, contracts, proposals, project communications, technical requirements, support requests, billing details, invoices and transaction records relevant to the service. Where a client provides access to its systems or data for development, migration, hosting or support, we process that information within the agreed scope. We do not require information unrelated to the work requested.

Accounts and digital products

For Services with accounts, we handle registration and authentication information, user preferences, organization membership, access roles and information submitted through the product. In Teamora, this can include a profile photograph, department and job information, working schedule, birthday, absence entitlements, requests, dates and durations, approvals, comments and related documents. An authorized colleague or company administrator may provide some of this information.

Some workplace documents or absence records may contain health-related or other sensitive information. Such information should be provided only where needed for the applicable process and through the appropriate authenticated feature.

Technical information

Operating and protecting the Services involves technical information such as IP addresses, browser and operating-system details, request times, pages or features used, account and company identifiers, session information, security and audit records, and diagnostic or error information. Mobile notification registration also involves a device or installation identifier and notification token. These technical identifiers are not necessarily anonymous.

Information from others and connected platforms

We may receive information from your organization, a business contact acting on your behalf, an authorized project collaborator or a service you choose to connect. The scope of a Google, Apple or Microsoft integration is described in Section 9 and in the relevant permission or subscription screen. A calendar connection does not give us your provider-account password.

4. Information Use Practices

We use information relevant to the relationship or Service to:

  • Respond to enquiries, discuss requirements, prepare proposals and communicate about our work.
  • Deliver software development, consulting, implementation, hosting, maintenance and support that a customer requests.
  • Administer contracts, customer and supplier relationships, invoicing and related business records.
  • Provide accounts, authentication, preferences, access controls and the features of our digital products.
  • Operate Teamora's workplace records, absence requests, approvals, documents, calendars and notifications.
  • Maintain reliability, diagnose problems, prevent abuse, investigate security issues and improve the relevant Service.
  • Send service communications or, where permitted, business updates and marketing communications subject to your choices.
  • Meet applicable legal obligations and establish or defend legal claims.

Where applicable law requires a legal basis, the basis depends on the activity: performing or preparing a contract, complying with a legal obligation, consent, or a legitimate business interest balanced against your rights. Sensitive workplace information is processed only where an appropriate condition and organizational authorization apply. Consent to marketing is separate from providing a requested service or connecting a calendar.

5. Disclosure of Information

People involved in the requested service

Information may be shared with the customer, authorized project participants, company administrators or other users who need it for the relevant business process. In Teamora, access is governed by company membership, roles and permissions. Information copied to an external calendar follows that calendar's sharing settings.

Service providers

We use providers for functions such as hosting and infrastructure, business email, technical support, security, communications and the integrations you choose. They may process information necessary for their task under appropriate confidentiality, security and purpose restrictions. Google, Apple and Microsoft may also act independently when you use their own accounts, operating systems, calendars or app stores.

Legal requirements and business changes

We may disclose information when required by law or when necessary to address fraud, security threats, abuse or legal claims. A business reorganization or transfer involving personal information remains subject to applicable privacy obligations. A transfer of Google user data as part of a merger, acquisition or asset sale requires your prior explicit consent under the Google-specific restrictions below.

We do not sell connected-calendar information or provide it to advertising platforms, data brokers or information resellers. Connecting a provider is not permission to disclose its data for unrelated purposes.

6. Data Protection and Confidential Client Information

We handle information for the relevant business or product purpose and limit access according to the work involved. Project agreements may define additional requirements for confidential information, customer systems, subcontractors, security and return or deletion of project data. Where we process personal information on a customer's behalf, we follow the applicable agreement and authorized instructions.

Use the agreed project or authenticated product channels for confidential documents. Avoid including passwords, authentication codes, private keys or unnecessary sensitive information in public website forms, ordinary chat messages or privacy requests. Any AI-assisted or automated feature that involves additional processing is subject to the disclosures and choices presented for that feature; Google API data is subject to the specific AI-use restriction in Section 9.

7. Who Has Access to Your Personal Data?

Access may be available to authorized Unlimited Coders personnel, contractors and service providers who need it to deliver, support or protect the relevant Service. Customer-controlled project information may also be accessible to the customer's authorized representatives. Support access does not provide an unrestricted entitlement to browse customer information.

Within Teamora, your employer or company administrator manages membership and roles. Approved colleagues may be able to see information permitted by those settings. Private absence types and private downloads require the relevant authorization. External calendar copies, emailed documents and notification previews can be visible outside Teamora according to the destination's settings.

Human access to information received through Google APIs is limited to specific access you affirmatively authorize, necessary security investigation or a legal requirement. The same Google use restrictions apply to personnel, contractors and any successor handling that information.

8. Personal Data Storage and International Transfers

Information may be stored in systems operated for Unlimited Coders, the relevant customer environment and the systems of providers needed to deliver the Service. Documents or messages sent to a customer, email recipient, connected calendar or mobile device may also be stored in that destination.

Some providers process information in countries other than your country of residence. Where applicable, we use the safeguards required for the relevant transfer and any additional restrictions agreed for a customer project. Provider-specific restrictions continue to apply wherever the data is processed. The relevant provider's privacy notice explains its own processing and controls.

9. Google, Microsoft and Apple Services and Calendar Integrations

How Teamora calendar synchronization works

Calendar integration is optional. Teamora exports approved absences that you are permitted to see. A copied event contains a title, start and end date/time, and a synchronization identifier. It may include a colleague's name and permitted absence type when your role allows you to see that colleague's absence. Where a private type is not visible to you, a neutral absence title is used. Reasons, free-text notes, comments, documents, medical attachments and attendee lists are not included in these calendar exports.

Synchronization is one-way: changing a copy in an external calendar does not change the Teamora request. While a connection remains active and authorized, the export is updated to reflect changes, cancellations and what you are permitted to see. Google and Microsoft synchronization can remove mapped copies; an Apple ICS subscriber applies feed changes according to its own refresh and calendar behaviour. If authorization or calendar access is lost, synchronization stops and existing external copies may remain. The external calendar's sharing settings apply to those copies.

Google services and Google Calendar

For Google Calendar, Teamora requests calendar.events.owned (https://www.googleapis.com/auth/calendar.events.owned), which permits viewing, creating, changing and deleting events on calendars you own. The integration uses your primary calendar and Teamora's synchronized events; it does not list or import unrelated Google calendar contents. It reads Google's event-colour palette and uses the closest available colour to a permitted absence type. A concealed private type does not export its identifying colour. The Calendar connection does not request Gmail, Drive or contacts access.

Teamora stores encrypted OAuth access and refresh tokens on its backend, together with connection ownership, status, synchronization timestamps, errors and event mappings needed to maintain the connection. OAuth state and verification information protect the authorization flow. Google requests use HTTPS. Google API information is used for the user-facing feature you authorize, with access and deletion controls described in Section 15.

Limited Use: Teamora App's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, remarketing, credit or lending, give it to data brokers or information resellers, or use it to develop, improve or train general-purpose or non-personalized AI or machine-learning models. These restrictions include derived information and override general corporate marketing provisions.

Transfers of Google API information are limited to the authorized user-facing feature with your consent, necessary security purposes, legal requirements or a business transfer with your prior explicit consent. Providers processing it for us must follow the same restrictions. The human-access limits in Section 7 apply.

Google also provides Firebase Cloud Messaging for Teamora notifications and may provide business email or app distribution through Google Play. Those separate purposes do not authorize access to your Google Calendar. For Google's own processing, see Google's Privacy Policy and Firebase privacy information.

Microsoft services and Microsoft Calendar / Outlook

If you choose Microsoft Calendar / Outlook, Teamora requests delegated Calendars.ReadWrite and offline_access permissions. The first permits calendar-event operations for the signed-in user; the second allows access to be renewed for background synchronization. Teamora uses Microsoft Graph to create, update and remove its permitted absence-event copies in your calendar. It does not import unrelated Outlook calendar events into Teamora.

The Microsoft event contains the permitted title and start/end date/time described above. Teamora stores encrypted authorization tokens, connection status, synchronization times, errors and returned Microsoft event identifiers. The Google event-colour mapping described above is specific to Google; the current Microsoft export does not promise the same colours.

Microsoft connection information is used for the chosen integration and its operation and security, not sold or used for unrelated advertising. You can disconnect in Teamora and separately withdraw the app's consent through the controls for your Microsoft account or organization. Disconnecting in Teamora does not revoke Microsoft's grant or automatically delete existing Outlook copies. Microsoft or your organization's policies may affect permissions and access. See the Microsoft Privacy Statement for Microsoft's own processing.

Apple services and Apple Calendar

Apple Calendar integration uses a private ICS subscription link. Your calendar application retrieves a feed of the Teamora absences you are permitted to see. This is a subscription to a Teamora feed, rather than authorization for Teamora to read your existing iCloud calendar events or use your Apple Account password.

The feed includes the permitted title and dates, synchronization identifiers and the information needed to represent the event and its status. The server stores a hash of the private feed token. Treat the full subscription link as a credential: someone with the link may be able to retrieve the feed. Regenerating the link invalidates the previous link; disconnecting stops future access through that connection. Copies already downloaded by a calendar application may remain, and you can remove the subscription in that application.

Apple also provides iOS notification delivery through Apple Push Notification service and distributes our iOS application or beta versions through the App Store or TestFlight. These functions involve the delivery or distribution information needed for that service and do not grant Teamora general access to an Apple Account. See Apple's Privacy Policy for Apple's own processing.

Business email and optional organizational mail connections

We use email services to communicate with customers and deliver invitations, account messages, service notices and requested documents. The email provider processes the recipient address, message and any attachment needed for delivery. This can include Google or Microsoft services depending on the configured sender.

Where an authorized organization administrator separately connects a sender through OAuth, this is distinct from a personal-calendar connection. The optional Google mail connection requests https://mail.google.com/, a broad mail permission; the optional Microsoft mail connection requests SMTP.Send and offline_access. Teamora's implemented mail use is sending the organization's configured service email, not importing inbox contents. Sender credentials and OAuth tokens are stored encrypted where configured. Calendar consent alone does not authorize organizational email access. Google API information from a mail connection is subject to the same Limited Use and human-access restrictions above.

10. Cookies, Analytics and Marketing Communications

Essential website and application storage

Our websites and authenticated Services use cookies or similar storage for features such as sessions, security and preferences. Browser controls let you restrict or remove this storage, although doing so may affect sign-in or other functions.

Website analytics, advertising and social features

Where enabled on the corporate website, analytics or marketing technologies may process visit information such as browser details, pages viewed, referral information, identifiers and interactions. Social-media links or embedded third-party features may also involve processing by their providers. Applicable consent choices are presented through the website or relevant feature. The providers' own notices explain their independent processing.

We may use business contact information for relevant corporate updates or marketing where consent or another applicable legal basis permits it. You can unsubscribe through the message or contact us to object. Marketing consent is not required to request a proposal, receive contracted support, use Teamora or connect a calendar.

Connected-calendar credentials, event information and information derived from Google API data are not sent to website advertising or marketing analytics services. A consent to a calendar integration is separate from website analytics or marketing choices.

11. Teamora App, Mobile Devices and Notifications

Teamora's web, iOS and Android clients use the same workplace service and authorized company records. Information submitted through the application is used for the selected workplace feature. When you choose a profile photograph or upload a document, the selected content is transmitted to the service. Device permissions and file-selection controls apply to the feature concerned.

For mobile push notifications, Teamora uses Google Firebase Cloud Messaging on Android and iOS, with Apple Push Notification service delivering to iOS devices. We handle an installation identifier or registration token, platform and account/session association, registration status and delivery information. Providers receive the target identifier, notification title and text, and routing identifiers needed to deliver and open the notification.

A notification may include an employee's name, a permitted absence type or date, an approval decision, or a document type or reminder. It can appear on your device's lock screen according to your settings. Notification payloads do not include the contents of medical attachments, absence reasons or comments. You can manage available preferences in Teamora and notification permissions in device settings. Disabling alerts or unregistering a device does not itself erase every retained registration or audit record.

App Store, TestFlight and Google Play distribution and testing may provide us with installation, beta-feedback, crash or diagnostic information made available through those platforms, depending on the platform and your choices. Apple and Google handle their own store accounts and distribution services under their respective notices. Installing an app or joining a beta does not automatically create a Teamora workplace account or authorize a calendar connection.

12. Your Rights and Choices

Depending on the law and processing involved, you may have rights to access, correct, erase or receive a copy of personal information, restrict or object to processing, withdraw consent, or complain to a competent data-protection authority. Withdrawing consent does not change the lawfulness of earlier processing. Some records may need to be retained to meet legal obligations or protect the rights of others.

Contact us using Section 17 and identify the website, business relationship, product or connection concerned. Where a customer or employer controls the information, we may need to involve its authorized representative. We may verify your identity before providing or changing records and will respond within the period required by applicable law. Do not send passwords, verification codes, tokens or private calendar links.

13. Third-Party Links and Children

Our Services may link to external websites, social platforms or optional integrations. Those operators control their own services and publish their own privacy notices. Review the relevant settings and notices before sharing information. Their notices do not replace the commitments in this Policy for information handled by Unlimited Coders.

Our corporate and workplace Services are intended for business use and are not directed at children. If you believe a child has provided information inappropriately, contact us so we can investigate and take appropriate action. A client-operated product may have its own audience and notice, for which the client is responsible.

14. Security

We use technical and organizational measures intended to protect information against unauthorized access, loss, alteration or disclosure. Depending on the Service and information, these include authenticated access, role-based authorization, HTTPS, protected credentials and security/audit records. Teamora stores configured calendar and mail authorization tokens encrypted on the backend. This does not mean every database field, message or exported copy has the same encryption properties.

No internet service can guarantee absolute security. Keep your account and devices protected, use authorized project channels, sign out on shared devices and consider who can see shared calendars or notification previews. Contact us if you believe an account, private subscription link or other Service information has been exposed.

15. Data Retention, Disconnection and Deletion

Corporate, customer and product records

We retain information for as long as needed for the relevant enquiry, contract, service, support, security or legal purpose. Different records have different needs: correspondence and project records support the relationship, financial records may have legal retention requirements, and technical or audit records support security and accountability. Information processed on a customer's behalf is also subject to the applicable agreement and lawful instructions. Information no longer needed is deleted or anonymized as appropriate.

Teamora employment and document records may be subject to the organization's retention requirements. Leaving a company, uninstalling the app or switching off notifications does not automatically delete those business records. Retained device registrations may be disabled without their historical records being erased.

Google and Microsoft calendar connections

Disconnect a personal-calendar connection in Teamora → Profile → Personal calendars to stop synchronization and clear the active credentials and pending authorization state from that connection. Connection metadata, event mappings, errors and audit history may remain for synchronization integrity, troubleshooting, security or applicable record-keeping needs. We retain them only for those purposes for as long as necessary or as required by law.

Disconnecting in Teamora does not revoke the grant in the provider account or delete events already copied to Google or Microsoft calendars. You can separately remove Teamora's authorization in your Google Account connections or the corresponding Microsoft account or organization controls. You can delete remaining event copies in the external calendar. The Apple ICS controls and their effect on downloaded copies are explained in Section 9.

Requests to delete information

For corporate website or business records, email info@unlimitedcoders.com. For Teamora, Google, Microsoft, Apple calendar or notification integration records, email support@unlimitedcoders.com with the subject “Privacy / data deletion request” and identify the relevant account, company or connection without including credentials.

We may verify your identity, coordinate with a customer controlling the record, delete information that no longer needs to be retained and explain any lawful retention requirement. Deletion from active systems may precede removal from backups; backup copies may remain until overwritten or removed under the applicable backup-retention process. We do not promise immediate erasure of every historical copy. Information already held by a provider, email recipient, subscribed calendar or exported device must also be managed through that destination's controls.

16. Viewing and Updating Information

Keep your contact and account information accurate. Use the available profile or organization controls to update information you are authorized to change, or contact us about a correction to a corporate, business or project record. In Teamora, some workplace fields and documents are controlled by an administrator or the organization. Changes to an external calendar copy do not update the original workplace record.

Contact us if you cannot find the appropriate control or wish to access information held outside your account. We will direct the request to the relevant team or customer representative while protecting other people's information.

17. Contact

For questions, requests or complaints about this Privacy Policy, contact Unlimited Coders:

This Policy is published at unlimitedcoders.com/privacy-policy and applies to the Unlimited Coders Services described above, including Teamora App and its applicable Google, Microsoft and Apple integrations.