Item logo image for Visage360

Visage360

ExtensionWorkflow & Planning2 users
Item media 1 (screenshot) for Visage360

Overview

Visage360 inside your clinic's system: each client's photos, comparisons and analyses on their record. Works with Feegow.

Visage360 inside your clinic's system: each client's photos, VisageTone, VisageCrop and VisageFrame, the skin analyses, before and after comparisons and 3D scans, on the client's record, without leaving the system you use every day. Works with Feegow. In Feegow, on a client's record, a "Visage360" item opens Visage360 for that client, right there. Like "Imagens", the item shows how many new photos and 3D scans the client has. Feegow keeps each photo's original in the client's record; everything Visage360 makes of it stays in Visage360 and shows here. Connect once from any Feegow page: a line at the top of Feegow's pages says when the token needs you (not connected yet, ending soon and not renewed for you, ended, a permission missing). Click it, or the button on Feegow's "API Pública" page, and the extension makes the token there through Feegow's own API, in your Feegow session: it creates the token Visage360 needs with only the permissions it needs, connects it, and switches off the old Visage360 token. After that, the extension keeps the token current by itself while you work in Feegow: in its last 30 days it makes the new one and switches the old one off, and it keeps the token's permissions at exactly the ones Visage360 uses, adding or removing them, only on the Feegow licence Visage360 is connected to and never on any other token. To do it, it may open Feegow's "API Pública" page out of sight. You can still make the token yourself, step by step. With Visage360 connected, the photos already in the client's "Imagens" in Feegow come to Visage360 too, for before and after comparisons: the extension reads the client's "Imagens" the way Feegow's own "Imagens" does and hands the links to those photos to Visage360, whose server fetches them. You need a Visage360 account with an active subscription, and sign in to it once inside Feegow. The extension reads the client's number in Feegow's address, to open that client and to count their new photos and 3D scans, Feegow's licence number on the record, which it sends with it so that Visage360 opens and counts only clients of the licence it is connected to, the links to the photos in the client's "Imagens", which it hands to Visage360, and the token. It keeps no client data and runs no analytics. Its own requests go only to Feegow, inside Feegow's page and session: reading the client's "Imagens", and Feegow's token calls, when you click and to keep the token current. Everything else reaches Visage360 through the Visage360 page it opens. Feegow is a trademark of its owner. This extension is made by Lab360, Inc., the maker of Visage360, not by Feegow.

Details

  • Version
    1.0.2
  • Updated
    November 9, 2026
  • Size
    109KiB
  • Languages
    2 languages
  • Developer
    Lab 360, Inc.
    9357 Osprey Isles Blvd Palm Beach Gardens, FL 33412-1118 US
    Website
    Email
    support@lab360.ai
    Phone
    +1 646-659-4533
  • Trader
    This developer has identified itself as a trader per the definition from the European Union and committed to only offer products or services that comply with EU laws.
  • D-U-N-S
    119471371

Privacy

Manage extensions and learn how they're being used in your organization

Visage360 has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

Visage360 handles the following:

Personally identifiable information
Health information
Authentication information
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps