Releasing product and BT SIG/Wifi Alliance approval

[eelikesESP32]

Hello,

I am planing to release a product with an ESP32. This is my first time. I've been doing some research on Bluetooth SIG and Wifi Alliance and Id like to clarify some stuff. Maybe someone has some experience on this.

My product is a BLE server with a private service and reads sensor data. The other product is a BLE client that will collect this sensor data and this client also acts as an embedded web server. The web page will display the data and allow for configuration of my devices.

First question - if I do not use the bluettooth logo/trademark and I do not mention bluetooth in any of my documentation at all and also in any marketing brochure, do I still need approval from Bluetooth SIG, sign up as a member and pay fees? My customers wouldn't even know it's bluetooth under the hood unless they open the enclosure and see the esp chip. They could only assume it's bluetooth because the user would have to command the BLE client to scan my devices and connect. I don't plan to use smart phones by the way with regards to connecting to my ble server.

Second question- same thing as above but with wifi alliance. If I don't mention wifi anywhere and not use the wifi certified logo, do I still need to pay fees? What gives it away as wifi is my user guide will ask customers to connect to their router by entering ssid and password. But I wont mention wifi at all. Do I still need their approval?

I just want to make sure I do things the right way and not break rules and regulations.

Last question. Currently I wrote the BLE client and Wifi Server as 2 separate projects during prototype stage. I read somewhere that the esp32 work with both functionality enabled? Any sample code to help me on how to use BLE and wifi together.

Thank you very much.
Regards,
EE