Changelog
Back to All

3rd March - Privacy and Security

over 1 year ago by Peadar Coyle

Better user permission management

At Aflorithmic we take really seriously security for customers. So we recently rolled out a new improved user permissions management (which is managed by our customer success team) and have taken user feedback to make this even better.

We've also added enhancements in resource based control. We'll be rolling out more and more features based on this in the coming weeks. However here's a few improvements.

  • We've a 10x faster system for handling this, and reduced load on our engineering team by 10x, so they can focus on producing features for our customers! 🍮
  • We've enabled better privacy and control. For example - We are assigning private voices with an owner role of the user, which only has access to certain Operations like invite others and delete the voice.
import audiostack


audiostack.api_key = "APIKEY"


PUBLIC_VOICE = "stefan"
PRIVATE_VOICE = "private_aflr"
PREMIUM_VOICE = "dahlia"
SCRIPT_TEXT = """
Hello Viviane! Look what I have build!!!!
"""

script = audiostack.Content.Script.create(scriptText=SCRIPT_TEXT, 
                                          scriptName="privacytest")

speech = audiostack.Speech.TTS.create(
    scriptItem=script, voice=PRIVATE_VOICE, speed=1.1, public=True
)
speech.download()

The premium voice should break because you won't have access to this.

  • This allows you to have specific voices to specific users. So your PII is better protected.

🔐

  • We now have a more auditable, better security, and helping protect our customer data, which we take very seriously. 🏁

Bug fixes and enhancements

We fixed a bunch of bugs in the recent release. We can't highlight them all.

However let's celebrate some 💯

  • We've improved our voice systems - we reduced technical debt and did a whole new design - this will enhance the customer experience and also allow us to ship features faster 🚢
  • We've made improvements to billing, we've fixed some bugs (for example 2FA didn't work with some credit cards), and enhanced the transparency (it'll be clearer in your reporting). We'll be rolling out further changes in the future. 💰
  • Our script pipeline was failing silently in some edge cases - now we've fixed this and it fails safely. 👷