Questions About Nutritional Data Sources and User Input Management

[Paolenji]

Questions About Nutritional Data Sources and User Input Management

Hi everyone, I’m researching how nutritional databases work within popular health and fitness applications, and I’d like to understand a few things better:

1. Data Sources: Where do the nutritional values in your database come from? Are they sourced from official public databases, third-party providers, or user-generated inputs?
2. User Input Management: When a user logs or creates a new food item, does that data become part of the general database accessible to other users, or is it only visible to the individual who entered it?
3. Data Ownership and Control: How is data ownership managed? Specifically, if a business (e.g., a restaurant) were to provide detailed nutritional information, would they retain any control over how that data is used or shared within the platform?

I’m interested in learning about best practices and standard policies regarding data sourcing and management, so any insights or resources would be greatly appreciated.

Thanks in advance for your help!

[Gondwana]

The SDK doesn't provide access to that database. I'll move your post to a more relevant forum section. That said, your questions are arguably broader than 'development' and could be asked in other sections too.

[Gordon-C]

Hi @Paolenji 

At Fitbit, we have a public and private database.  Some of the values come from the user's input and some are provided by Fitbit.  Each company has a different process for managing the nutritional information.   I'd suggest determining what functionality you want to provide and research how to implement solutions based on that.

[Paolenji]

Hi Gordon,

Thank you for your response, I really appreciate it!

You mentioned that Fitbit has both a public and private database, with some values coming from user input and others provided by Fitbit. I’d love to understand a bit more about how this works:

1. Who provides the nutritional data in the private database? Are these official sources, third-party providers, or data curated by Fitbit itself?
2. When a user adds a new food item, does Fitbit verify or standardize the data before making it available? Or is it strictly user-generated and used only by that individual?
3. You mentioned that "each company has a different process for managing nutritional information"—does this mean Fitbit follows a specific standard, or does it manage data differently from platforms like MyFitnessPal or Cronometer?
4. If a business wanted to provide verified nutritional data, how would that information be managed within Fitbit’s system? Would they retain any control over how their data is shared and used?

Thanks again for your time and insights!

[Gordon-C]

Hi @Paolenji 

1. The private data is something Fitbit licensed.

2. We do not verify the data the user enters manually.  The Fitbit mobile app does support scanning the food item's barcode to get the content from the label.

3. I'm not aware of a standard for logging nutritional data.

4. How do you see providing the verified nutritional data to Fitbit?  

[Paolenji]

Hi @Gordon-C,

Thanks for your response! I really appreciate the insights.

I’d like to clarify one key point about user-added food entries:

If I, as a Fitbit app user, manually enter the nutritional values of a dish or a product:

1. Is this food entry only visible to me, or can other users find and use it?
2. Does Fitbit store this entry in its database for future searches, or does it remain private to my account?

Regarding your question on providing verified nutritional data to Fitbit: at this stage, I’m exploring how different platforms manage food data before considering potential contributions. Understanding how user-generated and verified data are handled within Fitbit is key to evaluating possibilities.

Thanks again for your time and support!

Best,

Paola

[Gordon-C]

The user entered foods go into your private database and should only be visible to the user who entered it.   It would be searchable and reusable for that user.